r/ClaudeCoding • • Jul 14 '26

r/ClaudeCoding lists the TLDRs of all Claude Code and coding discussions with comment counts >= 50 that appear on Claude subreddits.

9 Upvotes

New TLDR posts updated every six hours.

You are welcome to comment on all posts and make new posts as well


Brought to you as a public service by the moderators of r/ClaudeAI and Wilson, u/ClaudeAI-mod-bot


r/ClaudeCoding • • 2h ago

r/ClaudeAI [TLDR] Claude Code is insane. My entire self-hosted Netflix is 17 MB. [via r/ClaudeAI]

2 Upvotes

OP : u/CoderLuii

last week i shared holyarrs here, the netflix-style app i built for my media server with claude code. since then: 1,445 github stars, 23,763 docker pulls, 26 releases and 309 closed issues in 8 days. 299 people joined the discord and 533 signed up for updates

quick recap: a home media server usually means six apps (sonarr, radarr, lidarr, bazarr, prowlarr, seerr) just to find and get a movie. holyarrs does all of it in one app, about 17 MB, and plugs into what you already run: qbittorrent or sabnzbd to download, plex, jellyfin or emby to watch

last post i listed what was next. here's what actually shipped:

  • an mcp server, so claude can talk to your library
  • 4K requests, and every request can wait for the owner's yes (that's the video)
  • plex friends' watchlists turn into requests on their own
  • run it without my metadata server at all, or with your own tmdb key
  • the app in 44 languages (i promised 11 more, it got a bit out of hand)

the part i didnt expect was how fast the issues came in. people were filing bugs and ideas faster than i could read them, and a few even sent fixes themselves. claude code helped me keep up, and 309 issues got closed in 8 days. honestly the people using it made it better than i could alone

i've been putting in 16+ hours a day on it since launch. most days look the same: wake up to a pile of new issues, pick one, have claude code dig into it while i check it on a real setup, ship the fix, reply to whoever reported it, next one. some days that loop ran 5 or 6 times

it's free and open source. still a beta, so expect rough edges. i'm in the comments

what's the one thing it still needs before you'd switch?


Original link/media URL : https://v.redd.it/yh6yhdiuuc2i1


r/ClaudeCoding • • 4h ago

claude code & Codex?

2 Upvotes

Hi,

I'm building quite a lot with Claude Code and I'd like to have my work checked by Codex as a second reviewer. I'm curious how you handle this.

Right now I've set it up in Claude Code so that whenever something is finished or about to go live, it first has to pass a Codex review before it can be deployed, even to a test environment.

A few questions:

  1. How do you set up this kind of review flow? Do you do it the same way, or do you use a different approach?
  2. How do you work with multiple AI models within the same tool? For example, Claude writing the code and Codex reviewing it.
  3. Are there specific tools you use or recommend for letting multiple AI models review code?

Would love to hear how you approach this. Thanks!

Best,

Bart


r/ClaudeCoding • • 1h ago

Spare code

1 Upvotes

I want to upgrade to Claude pro because I’m building a game for a school project
but I was just wondering if anyone has a spare referral so I could test it out before subscribing
a 7 days trail would be nice,
It would help out a lot


r/ClaudeCoding • • 5h ago

I wanted to see what my Claude Code agents were doing, so I built a pane for it (open source plugin

2 Upvotes

I was inspired by Agent Flow, posted on this sub. I loved the idea, but running it in VS Code put a noticeable load on my computer, and I wanted to see everything inside the Claude app itself, right next to my session. So I built a side pane for it. It's called Agents, skills & plans. It's my own project, free and MIT licensed.

The video shows the graph view while a session works through a four-step plan (demo data).

What's in the pane

For every open Claude Code session it shows:

  • The plan Claude is working through. The current step pulses, replaced plans move under "Past plans", and dropped steps get struck through.
  • Subagents, attached to the plan step they were spawned under, with status, running time and their most used tools with call counts (Grep 21, Read 7). The tool a subagent is using right now is outlined.
  • Skills, as pills under their step: active, used, red on error, ×2 when repeated. Skills a subagent calls show up on its card.

Your current session sits on top in a frame, the others below it, and each one folds. You can switch between a compact list and an animated graph, and hide plans, agents or skills. Turn plans off and the graph becomes a timeline. A statistics card ranks the skills and subagent types you use most, counted from your transcripts. Screenshots of both are in the README.

Install

In a Claude Code terminal session:

/plugin install subagents-pane --marketplace qaokss/claude-agents-view

Answer y to add the marketplace, then pick a scope (user scope loads it in every session). In the desktop app, where /plugin doesn't run: click + next to the prompt box, then Plugins, Add marketplace, enter qaokss/claude-agents-view, then Add plugin.

The pane opens by itself when a session starts. If you close it, /agents-view brings it back.

It installs from GitHub because I couldn't list it in the official plugin directory: the portal only accepts mods from Verified organizations.

What it actually runs

It's a Claude Code hooks module. No server, no network. Plans come from Claude's task list tool calls, subagents from their spawns and turns, skills from Skill tool calls. Each session writes a small JSON snapshot under ~/.claude/mods-data/subagents-pane/, and the pane reads the other sessions' snapshots. The statistics card runs grep over ~/.claude/projects every 30 seconds, only while the card is open. Everything stays on your machine.

It costs no tokens. The mod never calls the model and adds nothing to the prompt or context: every hook passes the event through unchanged and only records it. The pane is drawn beside the chat, and the model never sees it. The only text it puts in the chat is a one-line reply when you run /agents-view yourself.

It's light on your machine too. A timer updates the pane once a second, and the snapshot is written only when something changed (plus a heartbeat every 30 seconds). The grep for statistics is the heaviest part, and it doesn't run while the card is closed.

Limitations

  • The graph needs the desktop or mobile app. In the terminal you get the list view only.
  • The hooks module API is in early access. I built and tested this with Claude Code 2.1.321 to 2.1.325, and it may break or need changes as the API changes.
  • A session that stops updating disappears from the pane after 90 seconds.

How I made it

I built the whole thing in Claude Code over one long session, iterating on the design with a ui-designer subagent.

Repo: https://github.com/qaokss/claude-agents-view

Two things I'd like to hear: what you'd want the pane to show that it doesn't, and whether the graph reads clearly on your setup. Bug reports go in the GitHub issues.


r/ClaudeCoding • • 2h ago

r/ClaudeCode [TLDR] Claude code is design to make you dump [via r/ClaudeCode]

1 Upvotes

OP : u/Ok-Committee5924

I've been writing code for the past 10 years, but a couple of months ago, I switched from Cursor to Claude Code after Cursor started pushing its own models and limiting usage of Claude models. I've been really enjoying Opus and Fable, but there's something I've noticed about how these tools are changing my coding habits.

Claude Code is set up in a way that makes reviewing code harder than it should be. You mostly get shown the diff, which makes it harder to explore other files and understand the broader context. On top of that, it runs deep review skills before committing, which often flag edge cases that don't necessarily need to be addressed. The agent then applies fixes automatically, sometimes making the code 10 times more complicated and harder to maintain without even asking for your approval.

Naturally, I've found myself becoming lazier and lazier with code reviews. And I suspect the same thing is happening with some of my colleagues.

A couple of days ago, after a release, we started getting weird reports from clients, and it became clear that parts of the codebase were becoming increasingly difficult to maintain. That pushed me to become much stricter about code reviews again, but honestly, I feel like these tools are designed in a way that works against that. Doing proper reviews takes more tokens, more time, and more effort than just trusting the agent.

I'm curious to hear what other engineers, especially those who don't consider themselves vibe coders, think about this. Have you noticed AI coding tools making you less disciplined about reviewing and understanding your own code?


r/ClaudeCoding • • 2h ago

r/ClaudeAI [TLDR] The 8.9 billion token strawberry [via r/ClaudeAI]

1 Upvotes

OP : u/the_big_flat_now

Edit: I'm not involved in any project that uses this post or my name. Everything official is linked on my Reddit profile, anything else is not from me and likely a scam.

Who really made the strawberry? See for yourself: https://strawberry-methodology.pages.dev

2 weeks, for what? A strawberry. My... our strawberry. But why? First of all: I mean, look at the strawberry! Second: we need to talk about all this. Every day.

I started with animating some seeds on a strawberry and ended up with "all" the strawberries as a procedural Blender plugin and a Blender render video. All of it with Claude Code agents, me steering 3,958 times, them building with 17,453 tool calls.

The Blender community was divided about this, till they removed the post with 18k upvotes. That's fine, I guess. I mean, ~7,700 geometry nodes for one strawberry is just an absolutely inhuman thing to build.

I tried to create a study with all the data I have about these 2 weeks. Perhaps i didnt do as much as i wished. But what do I know.

What do you do when you build something with agents so fast you're about to throw up pure dopamine, you know you're certainly not a Blender god, and people say you did nothing? I'm open to discussion, I'm open to giving credit away, but not on the premise that I did nothing. What DO we actually do ?


Original link/media URL : https://www.reddit.com/gallery/1xz0jhy


r/ClaudeCoding • • 8h ago

Claude doesn’t volunteer security unless you ask. People here have noticed it, and new benchmark data backs it up.

Thumbnail
leaddev.com
1 Upvotes

AI coding rules matter more than your model.


r/ClaudeCoding • • 14h ago

r/ClaudeAI [TLDR] Something happened [via r/ClaudeAI]

3 Upvotes

OP : u/Inevitable_Truth_85

100% claude code.
Last couple of weeks made huge progress. Keeping a super tight development process with opus 5.5 only since it came out.
Was able to get to Sunday night easily including using Fable here and there.
Last week had to reset.
This week - ONLY two days. 53%.
And have moved some work to sonnet already yesterday.
WTAf 🤦‍♂️


Original link/media URL : /img/z8mlb6ddk62i1.jpeg


r/ClaudeCoding • • 14h ago

r/ClaudeCode [TLDR] I need help to reduce Claude spending [via r/ClaudeCode]

1 Upvotes

OP : u/azadmir

Hi fellow redditors,

I'm building my own construction SaaS which has grown into quite a beast, with over 900 tables and 60+ pages across 22 modules. I'm using both Claude and Codex simultaneously, sometimes running up to 14 agents at once—which is my current machine's capacity.

The problem is that I'm spending between $6,000 and $8,000 a day on average. I use Fable to orchestrate everything, and it assigns its own agents for testing, auditing, etc.

My question is: is there any way I can cut these costs without sacrificing quality or speed?


r/ClaudeCoding • • 15h ago

A cron request timed out after 5 seconds. The browser work needed longer.

1 Upvotes

I’m building pileGo, a cross-listing app for secondhand clothes. One part of it checks marketplace listings for sales. An issue Claude Code helped fix was that the scheduled request had a five-second deadline, and the first browser check got cut off when that request ended.

The change moved the checks out of the request path. The scheduler can get its reply promptly while the checks run in the background with their own time budget. The part I’d take into other projects is asking the coding agent to trace which process owns a job from start to finish. Looking only at the timeout on the browser call can miss that something upstream has a shorter one.

When you use Claude Code on background jobs, what do you ask it to verify about the runtime before it starts changing timeouts? I’m interested in the prompts or checks that have caught the most real problems for people here.


r/ClaudeCoding • • 1d ago

r/ClaudeAI [TLDR] Do you think the “vibe coded” stigma will go away? [via r/ClaudeAI]

5 Upvotes

OP : u/MannerFit852

I’m one of the many people who coding agents have helped build things that would take many years of education otherwise. While I did a bit of game development and other basic courses learning a few languages, I am light years away from what coding agents have helped me do.

While I’ve had some moderate success with what I’ve built, and while my audiences generally don’t care about whether AI use, the obvious hatred of anything connected to AI on Reddit has me feeling timid discussing my development process. A simple “Did you use AI?” question can make me feel like an imposter or that they’re thinking “meh, anyone could do that”.

I try to keep in mind Reddit is not real life, and the proportion of people that are extremely negative on AI on this site is most likely much higher than the everyday population, but it’s difficult to look past.

So, do you think that “I created this with AI” stigma will fade? Will people even ask at some point? Do you think the general population actually thinks lesser of things built with AI?


r/ClaudeCoding • • 20h ago

r/ClaudeCode [TLDR] Sol 6.2 and Astra 6.2 just released [via r/ClaudeCode]

0 Upvotes

OP : u/Standard_Exchange59

Fable 5.2 is better than Astra 6.2 and Opus 5.5 is still unmatched for Sol 6.2.

I do not care about cost per task personally so if anyone wants to dig into that feel welcome to post here.


Original link/media URL : /img/2ew69thiz72i1.jpeg


r/ClaudeCoding • • 1d ago

r/ClaudeAI [TLDR] I invented a sports league that runs itself. Fock Ball simulated 38 years of history, airs a live 3D broadcast every night, runs its own newsroom and social media, and arrests its own players [via r/ClaudeAI]

3 Upvotes

OP : u/MitchThunder

TL;DR: I built Fock Ball, a made-up sport with 30 teams and 38 years of simulated history, and Claude coded it. Every game is played by a physics sim and broadcast live in 3D at fockball.com. Claude writes the announcers, the news and the social feed, and a highlight from every game posts itself to TikTok, Instagram and YouTube.

How it started

Hello! I’m a Product Designer by trade who (perhaps foolishly) spent the last 5 months building a fake sports league with Claude. The idea actually started a few years ago, when a buddy and I recorded an hour-long podcast about a sport that didn’t actually exist. The problem was it was impossible to keep track of all the details of a league — player names, game results, trades — and be consistent across more than one episode. It was fun, but we never shipped it. Flash forward to this summer. I’m experimenting with Claude Code and realize that this is the tool to finally turn my silly idea into reality.

A quick aside

You may have seen the AI Aussie rules league post here recently. Shoutout to u/AFL_gains for a fun build, and the timing is uncanny. Fock Ball takes almost the opposite approach. There, Claude coaches the teams and decides how they play. Here, no AI touches the game at all. A physics sim plays every game, and Claude runs the whole media operation around it. Let's get into it.

The sport

Fock Ball is modified football. It's seven on seven on a football field, with sand traps running down both sidelines. There's no kicking and no set positions, so anyone can run, throw or catch.

You score by getting the ball into the goal at either end. Running it in or a short throw is 3 points, and a long throw is 5. Each goal also has rings painted in it. Catch a long throw with both feet inside a ring and it's worth 7, or 10 for the small one in the middle. A game is three 15-minute periods.

The game engine

Most of the last 5 months went into the game engine, and I rebuilt it several times.

  1. Rolling dice. The first version rolled numbers for each player and spat out a box score. That was fine for stats, but there was nothing to watch.
  2. Play by play. Next it played out each possession in order with a game clock and wrote every play to a log. The box score is added up from that log, so the stats and the story always match. I showed it as dots moving on a field. Solid, but I wanted more.
  3. 3D broadcast. After getting tired of staring at dots, I decided to build a proper 3D broadcast. I started with my play-by-play sim and had animation fake the movement to match. It was a mess. Players teleported randomly around the field, the ball bent in the air, and weeks of patches never fixed it. I learned you can't animate your way to reality when nothing is really moving. During this phase I also experimented with using a Meshy-to-Blender pipeline for more realistic players. They looked great visually but the rigging and animations were sloppy and less realistic than having Claude sculpt and animate directly in code. I finally landed on a Pixar-style look. It's real enough to show emotion, and cartoony enough that you forgive the animation when it isn't perfect.
  4. Real physics. After about 6 weeks of work I threw out the engine and rebuilt it. Now the field is a real place, and every player and the ball has an exact spot on it. The sim moves every player and the ball 20 times a second. At each step, every player decides what they're doing, like getting open, covering someone or chasing the ball, and their ratings set how fast they can run, turn, throw and catch. Once the ball leaves a hand, it flies on gravity and wind. A catch happens when the ball actually reaches someone's hands, and a tackle happens when a defender actually gets there. Even the ref has to walk over and set the ball down before play restarts. Each game is about 30,000 snapshots (2 MB of data) and doesn’t fake anything. That's when it started to look like a real sport.

Game day

Now that I had a game, I needed to build the world around it. I started with a simple venue: grandstands, lights, a team bench. Then I wanted each team to have their own venue, so I generated reference images for each team with Google’s Nano Banana and had Claude build them all. Spending time getting the references right actually made this a fairly painless process. Then I wanted a 3D flyover to start the game, and had Claude model the city and environment around each club. 

Next I fleshed out the broadcast with an animated open, pregame countdown, intermissions and a closing segment. Two announcers, Dale and Tank, call every play. Claude writes their lines from the game's log, and Kokoro, an open-source voice model, reads them for free on my Mac mini. When it mispronounces a name, the fix goes on a pronunciation list, and speech recognition listens back to make sure it's right.

Under the booth there's crowd noise and a stadium organist. The organ is synthesized entirely in code. I worked with Claude to create 12 original riffs, which can shrink or expand to fill real game time, and it sounds different in a dome than in an open-air stadium. 

The stands are full of fans, and outdoor games are played in each city's real forecast, pulled every morning from the National Weather Service (and MET Norway for the one stadium in Canada). If it's raining there, it's raining in the game!

The teams and players

All 30 teams have an original, branded identity. Logos were generated with Google’s Nano Banana, and their color identity is used on uniforms, in venues and across the site. 

Players are generated body first. Height, weight and build are rolled before anything else, then 19 ratings from 0 to 99, like a video game: arm strength, accuracy, hands, speed, tackling, how well they play in the sand, stamina and more. A player's role sets the general shape, so a thrower throws well and is ordinary at the rest. His body pushes the physical ratings: a heavier player is stronger but slower, and a taller one wins more jump balls. About 1 in 20 players is elite at one thing, and about 1 in 200 is a generational talent who's great at two. Every player also has a hidden drive rating that nobody sees, which shapes who blooms late and who wastes his talent. Ratings then change every year as players develop and age.

Each player also gets a personality, how likely he is to get into trouble, a look and a bio. Then he gets a headshot. Code photographs the same 3D player you see in the broadcast, in his team's uniform, and that photo follows him everywhere: his player page, the news, the social feed and the broadcast's on-screen graphics. If he's traded or starts going gray, he gets a new one. Coaches and owners get generated and photographed too. Coaches get fired, and owners retire and hand the team to an heir or sell it.

League History

I didn't want to write the league's history. I wanted it to be played. So I outlined the big story myself. The league starts in 1988 as four beach clubs on the Jersey Shore and in Virginia Beach, becomes a real league in 1993, and grows to 30 teams in four waves of expansion through 2011. I also had the league go dark for three years after the 2008 crash and three more for COVID, because that's what I assumed a struggling minor league would do. 

Then the sim took over. It played every season from 1988 to 2025 through the same code that runs the league today: the schedule, every game, the playoffs, then the draft, free agency, trades, retirements and the Hall of Fame. Nothing in between was written by hand. One full run takes about five hours.

After each run I read through the results like a fan would, looked for anything that felt off, tweaked the rules and ran it all again. The fifth run stuck: 8,513 games, about 2,360 players, coaches and owners, and 45 Hall of Famers. Santa Cruz became the dynasty, with four championships in five years. Fargo has never made the playoffs. And Anchorage, one of the worst teams in league history, made the playoffs twice in 15 seasons and won it all once. I locked it down. This is now canon. 

Front office and trouble

Teams run like real teams. There's a hard salary cap, contracts with guaranteed money, free agency, drafts, expansion drafts, waivers and an injured list. Teams trade players and draft picks, and losing teams sell at the deadline. 

Off the field, players get into trouble, from a DUI on a riding mower to stealing hotel bathrobes in bulk. Some just have bad luck, like getting bitten by an alligator while golfing. The ones who get in trouble are fined or suspended, and all of it ends up in the news.

The newsroom

Five reporters cover the league, each with their own beat and voice. There's a Monday recap, Friday power rankings, a game story the morning after a great game, a look at the week ahead and a police blotter for the troublemakers. A social feed runs all week with reporters and players chiming in to comment about games and drama around the league. Claude writes all of it, but it only gets the facts the sim recorded, so it can't invent a score or a stat. Code checks each piece against those facts and throws it out if anything doesn't match.

After every game, a highlight of its best play goes up on the site. Code picks the play, shoots it like a camera crew would and writes the caption. Once a day, the best one gets cut for phones and posted to TikTok, Instagram and YouTube through Buffer's API, timed for when each platform's audience is most active.

It's live, and it runs itself

The league doesn't need me anymore. There are 15 games a week, played one at a time so they never overlap: one a night Monday through Wednesday at 7:30 ET, two on Thursday and Friday, and four each on Saturday and Sunday. The best matchups get the prime-time slots.

Every morning a Mac mini plays that day's games in the real forecast for each city. It writes and voices the announcers, then locks everything away. The database won't show anyone a score, a stat or a single play until the game airs.

An hour before kickoff, the home page and the game page switch to a countdown. The broadcast starts about 90 seconds early, so the first whistle lands right on time. From there it plays out live, like TV, with everyone watching the same play at the same moment. You can pause or rewind, but you can never get ahead of live, and the score, play-by-play and stats only show what has happened so far.

At the final whistle the score and standings update, and the highlight posts 15 minutes later. Trades, signings, articles and posts all go out on their own schedule.

The scale

All of this is about 140,000 lines of code and more than 1,200 commits in under five months, on the $100 Claude Max plan. Over 8,500 games across 38 years of history (every game, stat line, contract and trade) fit in about 120 MB of database. The announcers have called 76 games so far this season: more than 60,000 lines and about 42 hours of audio, all voiced on a Mac mini.

What's next

Today is launch day, but it’s just the start. I’m ready to start scheming out a higher-fidelity broadcast with more between-plays content and refined animations, expanded social media content, merchandising for teams that don't exist, and maybe even that podcast my buddy and I never shipped. If there's something you'd want to see, let me know!

Tune in

It's all at fockball.com. There's a game on tonight at 7:30 ET—Tacoma Gnomes at Anchorage Glaciers— if you want to watch one live. Highlights from every game go up on TikTok (@fockball), Instagram (@fock.ball) and YouTube (@fockball), and r/fockball is the place to talk about the league. Thanks for taking the time to check out my obsession. Happy to answer any questions about how it all works!


Original link/media URL : https://v.redd.it/icohhjv4d62i1


r/ClaudeCoding • • 1d ago

Ringside: Claude and Codex plan usage beside your editor

Post image
4 Upvotes

I'm Mayowa from Knight AI+AV. We made Ringside, a free MIT-licensed desktop meter for Claude and Codex plan usage.

It keeps usage and reset information beside your editor in a card, orb or pill. It doesn't add quota or track API billing.

Check the reading's age: Claude desktop-only data can be hours old. The optional Claude Code connection updates after replies; Codex follows its local session data.

Ringside itself needs no signup or subscription; provider plans are separate. Usage data stays local, while optional update checks and downloads contact GitHub. The image is an official UI render with sample values, not a live account capture.

Public version: v2.0.5. Source and downloads: https://github.com/KNIGHT-AI-AV/ringside


r/ClaudeCoding • • 21h ago

I built an app for reviewing the specs and plans Claude Code writes, and it sends your notes back to the agent

1 Upvotes

I work spec-first with Claude Code. The agent and I shape an idea, then it drafts the requirements, a spec, ADRs and an implementation plan. I review them, and only then does it write code. Those documents become the project's record of what was decided and why, so reading them carefully matters as much as reading the code.

Reviewing them was the slow part. Editors and IDEs are built for editing, not for close reading. I couldn't easily see which docs were settled and which were still open. And giving feedback meant copying section references into the chat by hand, so the agent knew which part I meant.

So I built Folio, a desktop app for reviewing a project's Markdown docs. Open a folder and it shows every document in it:

  • Each doc's status (accepted, proposed, superseded), with filters and search across all of them
  • Docs rendered with Mermaid diagrams, math, code and cross-links
  • Highlights and notes on a passage or on a whole doc. Your files are never modified; marks live in ~/.folio
  • What changed since you last read a doc, down to the sections the agent rewrote

There are two ways to get your notes back to Claude:

  1. Copy and paste. Folio collects your notes into one Markdown block, with file paths and line numbers, for any agent.
  2. Review loop. Install the plugin:/plugin marketplace add crazzybot/folio /plugin install folio@folio Then run /folio:review-loop. Claude waits while you review. When you click Send, it gets your notes with their context, revises the docs, answers each note in Folio, and waits for the next round. Other MCP clients (Cursor, Codex) can do the same through the MCP server.

It's free and MIT-licensed, for macOS, Windows and Linux. Folio itself was built with Claude Code, using this same workflow.

I'd like to know how you review what your agent writes. Do you read the specs and plans, or only the diffs? How do you tell it what you decided? And if you've built a human-in-the-loop step like this, how did you hook it into the agent?

A proposed ADR in Folio: what changed since I last read it, my note, and Claude Code's reply

r/ClaudeCoding • • 1d ago

r/ClaudeCode [TLDR] Is anyone actually making money on anything they have built? Or are you fighting the AI Slop battle with the public? [via r/ClaudeCode]

2 Upvotes

OP : u/Successful-Seesaw525

Everything I build and advertise is widely rejected and very hard to market. The market is completely saturated with new software, in every direction.

However, I get mixed research results in regards to how many people actually pay for AI today.

Just curious if I am missing something?

Am I alone? How are you getting past the barriers?


r/ClaudeCoding • • 1d ago

Claude Code plugin that reduces token usage by 5-15% per prompt and keeps your project structure clean.

Post image
2 Upvotes

Here is how it works:

  • Command batching: Claude runs ls, cat, mkdir in separate turns. My plugin batches them into one command. Fewer turns, fewer tokens.
  • File organizing: Claude often puts new files in the root folder, my plugin puts files in stack-standard folders.

The skill was developed using a self-improving workflow: it was drafted, tested against real tasks, and refined based on its own results over several iterations.

Saves 5-14% of tokens per session. The more you use it the more you save.

Repo: https://github.com/BuildBias/toki

Install:

claude plugin marketplace add BuildBias/toki
claude plugin install toki@toki

r/ClaudeCoding • • 1d ago

r/ClaudeCode [TLDR] Running 18 Claude Code sessions at once and half my tokens go to idle wake-ups. How do you handle this? [via r/ClaudeCode]

0 Upvotes

OP : u/BlackberryOk182

Hey all, I could use some advice from people running a lot of Claude Code sessions at once.

I'm building a Windows app and I've got 18 Claude Code sessions working on the same repo across two Max 20x accounts, all on High effort. They talk to each other through one shared markdown "inbox" file. It works, but I keep running into my weekly limits, so I dug into where the tokens are actually going.

What surprised me:

  • About 91% of my usage (weighted by API prices) is just context being re-sent on every call. Actual output is about 9%, and edits to code are under 1%.
  • Roughly half of all tokens went to wake-ups where the session did nothing useful. No code, no tests, no git. Mostly each session's own background watcher waking it up to check the inbox, plus scheduled check-ins (one session was pinging itself every 5 minutes for days).

What I've tried so far:

  • Auto-compact at 300k instead of the default. Average context per call dropped from about 270k to about 179k. I have hooks that back up notes before compacting and tell the session to re-read them after.
  • Starting a fresh chat for each work item, with a short handoff note.
  • Replacing every session's own watcher with one small local script that only wakes a session when a post actually mentions it. In a replay of a day's posts it cut wakes about in half without missing anything addressed to a session. Just rolled it out today, so no real numbers yet.
  • Quiet test output (pytest -q), reading big files in slices, and a hook that blocks huge reads before they happen.
  • Trimming CLAUDE.md and memory files, and turning off claude.ai connectors so fewer tool descriptions load.
  • Trying Serena (MCP) on one session. Mixed results so far.
  • Tried the Superpowers plugin on a few sessions for a week and dropped it. Those sessions got noticeably less done and barely used its skills, though it was a small test.

My questions:

  1. How do you let long-running sessions wait for messages from other sessions without every wake re-sending the whole context?
  2. Is there a better way to coordinate a bunch of sessions than a shared file?
  3. Any other tricks for cutting context re-reads I'm missing?

Happy to share more details on any of this. Thanks!


r/ClaudeCoding • • 1d ago

r/ClaudeCode [TLDR] Weekly Showcase Thread; What are you building with Claude Code? [via r/ClaudeCode]

1 Upvotes

OP : u/Waste_Net7628

Weekly Showcase Thread

Built something with Claude Code this week? Share it here.

Apps, tools, experiments, scripts, websites, workflows, open-source projects — anything you've been working on is welcome.

When sharing, it helps to include:

  • What you built
  • How you used Claude Code
  • A link, repo, demo, or screenshot if you have one
  • Anything interesting you learned along the way

Quick project drops and simple self-promotion belong in this thread.

If you've got a project with enough substance for a proper write-up; how it works, how Claude Code was involved, technical details, lessons learned, etc. feel free to make a standalone post using the Built with Claude Code flair instead.

Please don't spam the same project repeatedly, and no referral or affiliate links.

What did you build this week?


r/ClaudeCoding • • 1d ago

[Request] Looking for a 7-Day Claude Pro Access Invitation to Test Claude Code for Scientific Workflows

1 Upvotes

Hi everyone,

I’m looking for an unused 7-day Claude Pro Guest Pass to explore Claude Code and evaluate its capabilities for scientific scripting, data analysis, and workflow automation.

If anyone with an eligible Pro or Max subscription has an available guest pass, I would sincerely appreciate it if you could share it with me via DM.

I’d be happy to activate it as soon as I receive it.

Thank you in advance for your help. I really appreciate it!


r/ClaudeCoding • • 1d ago

Claude Pro analog?

1 Upvotes

Have you had any experience with Cursor or OpenCode? What's the quota for Claude models? I already have GPT Plus, but I'm missing Opus 5.5. Are there any alternatives that offer a decent amount of quota for about $20?


r/ClaudeCoding • • 1d ago

r/ClaudeCode [TLDR] Four Ultras, what else can a man wish for? [via r/ClaudeCode]

2 Upvotes

OP : u/vovazk


Original link/media URL : /img/fznwdfpe352i1.png


r/ClaudeCoding • • 1d ago

Why Claude Code can cost you 2x to 10x of usage limits

Thumbnail
github.com
2 Upvotes

I spent time investigating and optimising my Claude Code token usage, here’s the most important anti-patterns avoid and best-practices to follow. Enjoy!


r/ClaudeCoding • • 1d ago

r/ClaudeCode [TLDR] PSA: Claude Code has an experimental "Code Mode" now (batches tool calls into JS) [via r/ClaudeCode]

3 Upvotes

OP : u/Poatri_US

Spotted this in the recent changelog and got it running in v2.1.325 (screenshot attached). If you haven't tried Code Mode yet, it changes how Claude handles multi-step tasks.

Instead of running tool calls one by one and dumping every raw output into your context window, Claude writes a single JavaScript script behind the scenes. It batches tasks in parallel, filters out noise locally, and only returns the distilled results it needs.

Simple but brilliant

Pretty big, cumulative context savings: Giant logs and grep outputs get filtered inside the JS script before hitting the context

It's great for big tasks, shines during repo-wide audits, bug tracing, and chaining MCP servers.

Anyone else daily-driving this since it dropped on the 12th? Curious how much token usage it's saving you on larger repos.


URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1xy0xr9/psa_claude_code_has_an_experimental_code_mode_now/

Original link/media URL : /img/l3u6hvrhf12i1.jpeg