“Something weird is going on w/ my rate limits”. “I burned thru my whole sub in an hour.”

Seeing so many new users is cool, but seeing people go through what I call the Anthropic initiation, which is using your whole subscription and a few hours or less is almost like a write a passage. Everybody has done it.

Don’t know where to start? Don‘t wanna read? I got you. The first thing you need to do is set up your CLAUDE.md global hierarchy the right way, then your first project. All you have to do is ask Claude code to read the anthropic website, dev docs, and Changelog, and setup the CLAUDE.md’s optimally. That’s it.

Next, docker desktop. They made it very simple where there’s what’s called an MCP tool kit. Get Context7, Playwright, (most will want YouTube transcriber), if you’re building anything serious, Arxiv or paper_search, & depending on your OS, desktop commander. There’s gonna be more, ask Claude code.

Last, Fable is NOT FOR EVERYTHING. To be honest, it’s not for most things. If you’re building a simple one page website, and you’ve never done it before, your time should be spent planning in the browser, dropping things into a project folder so you can spec out your MVP (look it up). this will give instructions once you make your plan that can be easily followed by opus, sonnet, and for all of your documentation and things like that, use Haiku. Fable is basically “break glass in case of emergency”…or “I dont have bills”. If you don’t have bills, then enjoy. for the rest, build about 80% of your project. When you hit the wall… like he forgot to set up auth or payment and do you have to sort out a mess your unprepared for as a noob, that is a fable adjacent issue. You don’t even need to use it. You can simply tell Claude code to use fable as an ad advisor to opus/sonnet. But if Zen breathing and yoga app isn’t working right because it keeps resolving to localhost and you can’t figure out why… Fabel ain’t gonna help you. Learning how to ask questions will, and especially providing plenty of context and straight up telling the model to help fill in knowledge gaps and think of things you haven’t considered.

If you read this, congratulations. You’re on your way. If you read this and rolled your eyes, again congrats. At least you have a semblance of knowing what you’re doing.

The difference usually comes down to strategy.

Instead of targeting businesses that do not have a website, target businesses that already have one but clearly need a better version. The market is larger, the sales process is easier, and the value proposition is much stronger because those businesses already understand why a website matters.

The next part is outreach. A regular outreach tool is not enough if all it does is send the same message to thousands of people. You need something that can analyze websites at scale and turn real issues into personalized emails.

I use Swokei for that. It helps find businesses with existing websites, analyzes each site, and turns problems with design, SEO, speed, layout, and mobile optimization into personalized outreach emails. That means you can contact a large number of businesses without sending generic messages or spending hours manually researching every website.

When someone replies interested, I always offer a free mockup. I use Claude, Lovable, or Base44 to build it quickly. It becomes much easier to sell when the client can already see what a better version of their website could look like.

Web meetings should also be a major part of the process. I would never just send the website through email and hope the client likes it. I present it live on Google Meet, Zoom, or Microsoft Teams, explain the value, show what has been improved, answer their questions, and try to close the deal during the meeting.

The less back and forth there is after the meeting, the better. Present the website, show the value, close the client, and move on to the next project.

That is the type of process that can help an agency scale much faster.

Especially with Fable, it constantly gives me answers like:

"It is because the third activator gate suppressed the desired behaviour".

And when I ask "what do you mean by the third activator gate?" it responds with:

"Oh, it is just the phrase I came up with to describe the if condition you have at line 96".

I don’t know how accurate this is, but I suspect it comes up with these words during reasoning to better guide itself. Then that glossary leaks into the output tokens we see, and Claude treats those words as if they’re part of a ubiquitous language that I already know.

My company has 6 GitHub repositories which all have a CLAUDE.md file and several skills/commands. Most of the CLAUDE.md text is identical across all repos, and the skills/commands are all the same. In other words, we're just copy-pasting the same instructions into the different repositories.

Clearly this is not maintainable, so I'm looking for a solution where we could store these files in just one place, and have each repo load them from there. I've investigated options like building a Claude Code plugin or using a new repo for these files, which can then be referenced by each project, but there are disadvantages to these options.

What I want is a solution where I can update the shared CLAUDE.md or skills/commands, and each project gets these changes automatically, without requiring each dev to manually pull or install the latest version.

Does anyone have any suggestions?

I maintain trigger-tree, an open source Claude Code plugin that logs which project docs the agent actually opens (all local no tokens). I built it after finding out most of my carefully written docs sometimes seemed to be ignored by AI...

Today I added a CI gate which checks whether your docs are reachable at all listed in their folder index, linked from somewhere, folders have an entry point, et cetera.. Plain Python over the file tree, no AI, same result on every machine, so you can fail a PR on it. Findings export as SARIF, so they land as annotations on the PR diff.

You can find it on the GitHub Actions marketplace (search "trigger-tree") or pip install trigger-tree and also add the plugin from Claude or Codex..

Issues and PRs welcome (https://github.com/Hedde/trigger_tree)

I was cleaning my inbox and found this job recommendation, are these kinds of roles real??

I build with Claude Code all day, and one small thing cleaned up my whole routine: I turned my usage windows into fixed shifts.

Your 5 hour window starts the second you send your first message, so if you fire off a random question at an odd hour, it resets at an equally odd hour and your day drifts with it.

I used to fix this by hand. Open an incognito window in the Claude app and type "hey" to haiku, to kick off the window.
Now a /reminder does it for me at 08:00, 13:00, 18:00 and 23:00, running on Haiku. Those are exactly 5 hours apart, so they become three clean shifts. The first one wraps up right around lunch, and by the time I'm back the next window is already lined up.

Hey everyone! Anyone have a Claude referral code available they could send me as a dm? I would be very grateful!I would like to test its functionality and if it is going to be useful for my project and if it's actually worth it.

Hey everyone!

I'm looking for 2–4 teammates for an upcoming web hackathon in Birtamode on August 5.

I'm hoping to find people who have experience building websites (HTML, CSS, JavaScript, React, Node.js, or similar) and have worked on a few projects before. If you're creative, enjoy solving problems, and can communicate your ideas well during presentations, that's a huge plus.

I'm looking for teammates who are serious about preparing before the event and want to build something we're genuinely proud of.

If you're interested, send me a DM..

To be eligible to participate you must be +2 running or +2 completed no bachelor's!

I’m trying to understand whether I’m missing something about how scheduled tasks are supposed to work.

At work we have Claude Enterprise, and I primarily use Claude Code on Windows. I’ve built a handful of scheduled tasks (mostly for my corporate functions workflow), but they only seem to run when my laptop is awake and Claude Code is running.

For example, one of my tasks runs twice a day. It checks for emails and Slack messages that I haven’t responded to yet and drafts replies using my Voice-Principles.md and Voice-Examples.md files. It works well, but only if my computer is on.

My manager mentioned that an engineering VP recommended building these kinds of agents/workflows in a GitHub repo instead, and that their tasks continue running even when their laptop is closed, they’re traveling, or asleep.

Is that actually how it works?

Does putting your Claude Code project in GitHub somehow make scheduled tasks run remotely, or is there another piece of infrastructure involved (GitHub Actions, a server, Codespaces, etc.) that I’m missing?

I’m a non-engineer, so I’m trying to understand the architecture rather than looking for step-by-step implementation details. I’d appreciate any explanation of how people are running truly “always-on” Claude Code workflows.

First ever time after weeks of Fable usage that I got the infamous Opus switch. The crazy part is that I only ran a gcloud inspect command that IT asked me to run, and it ran away thinking about it for an hour before deciding I had violated the safeguards.

Left to right: the flag an hour after I (hadn't) said anything, Fable asking me to run a command, and me running the command--which prompted the entire sequence

Bought 20x subscription at 90% usage on claude 5x subscription. But the usage is still at 90% shoun't it go down like to 30%. Asked for help on the chatbot said sorry might be a technical issue and ended the conversation.

Is there anything I can do?

Just wanted to share how my $100 usage credit it going on my Pro Plan. I've ready countless posts of their $100 being gone in a single prompt with Fable and Opus.

Yesterday I worked through 7 bug fixes using Opus 4.8 and have only used $74 of my $100 credit. I've used it without any novel style chats continuing on and on and start a new session with each bug. I think that's pretty decent even though I'd never pay piece mail like this on my own dime.

My sub is up in 4 days so had to use it now or lose it if I don't re-up. But if your smart it can go much further. You don't need Fable for absolutely everything.

hi redditers,

i'm actually creating a solution to simplify collaborative work with ai agents,

the idea is having a canvas like figma when you can spawn claude code and other providers like codex etc, have ios and android simuators, web instances, all linked together, and acess with your coworkers to this same workspace wich can be turned online or offline and solve the problem or having your laptop always on to make you claude run.

Like you can program in how much time it will shutdown, etc

I want you guys please to give me brutal feedbacks and any ways of improving :

Claude Code logs every session to `~/.claude/projects/` as JSONL with exact token
usage per request. I built a free open-source profiler that reads them locally and shows where your tokens actually go.

Findings from my own 60 sessions ($4,935 API-equivalent):

- Re-reads: a 5,649-line progress doc read 118x. Fix: head/archive split, 150-line "current state" head, history below a marker. The tool computes the math per file.
- Failed commands: 455 failed tool calls ≈ $201 of retry re-billing. It regex-classifies your actual error messages and generates the CLAUDE.md lines that prevent each class (mine were mostly PowerShell vs Unix syntax).
- MCP bloat: a server configured but never called in any session, schema injected into every request for nothing.
- The big one: cache efficiency: 95% of my context came from cache at 0.1x price. That's a ~$15.6k difference on one project. If your cache hit rate is bad, nothing else matters.

It gives each project a Context Score (0-100) and every recommendation cites your own numbers, no generic "write better prompts" advice.

Fully local, zero dependencies, no telemetry, MIT. `npx u/asmitbohra/tokenscope`

GitHub: https://github.com/AviVAvi/TokenScope

(If you hit weekly limits on Pro/Max, this is basically "where did my limit go")

I've been using the superpowers skills for writing the specs, plan and executing it via subagent-driven-development. However, the execution time takes about 1 hour. Life seems Life seems much simpler with plan mode + just execute the plan.

Questions:

1. Is anyone else hitting this wall with superpowers?
2. Are you customizing the skills to make it more lightweight?

using claude code on the same project for the past 6 months . doing exactly same kind of dev : javascript / python / ruby . Until 2 weeks ago using my Pro 20usd subscription it was manageable. Then it slowly started 2 weeks ago feeling like my usage was skyrocketing very quickly . Then we got the double limit , 100usd credit etc … but today I m really convinced that with the same subscription we had 2 weeks ago we do not have the same amount of work done .

I feel the 5 hour quota limit is a trap. I mean we also design the loops and workflow to utilize the cache window which is cheaper.

However, once you hit the limit in between the task, your next resume of the task will be a cache miss and you will immediately hit usage very easily.

Of course you should design carefully and split your tasks with proper handoff, still Anthropic should have considered these specific cases of cache misses differently?

I'd love to hear about the last time an AI agent caused a merge conflict, overwrote someone's work, or introduced a similar bug on your team. What happened? How did you catch and fix it? What would have helped prevent or resolve it? I am researching this pattern to understand how it plays out in real teams. No pitch, no product. Just genuinely curious. Reply here or DM me if that is easier.

Three days into rewriting SQLite in Rust with Claude and I'm further along than I expected.

Got the tokenizer, most of the parser, and a working B-tree that handles inserts and range scans. Pager is next and then it's mostly plumbing. Fable thinks the C source is honestly not that complicated once you get past the naming conventions, it's just written in a style nobody has used since 2003. A lot of it collapses down to about a third of the line count when you have real iterators and Result types.

I know about the test suite. Fable constantly brings up the test suite. I'm going to have Opus generate a property-based suite with proptest, which is going to be more valuable than 90 million lines of TCL that were written to catch bugs in a language that lets you index past the end of an array. Most of those tests exist because C exists. Delete the C and you delete the reason for many of the tests.

Currently at only 47 unsafe blocks, all in the mmap layer, and Fable already made a plan for those.

The part I keep coming back to is that this is the single most deployed piece of software in human history and it is written in a language where a missing bounds check is a remote code execution. Every phone, every browser, every plane. We just decided that was fine. No more.

Looking for two or three people to help with the query planner. Not asking anyone to write it, just to review what I have put together so far. I will send invites to the private github repository once NDAs have been signed.

NGL, I often forget to delete old plans. This time, it really bit me in the ass. I've got a huge refactoring job to do now because claude is incapable of sticking to the plan and spec detailed referenced in the prompt. Instead, it searched for similar discussions to make judgement calls in older specs. And unfortunately, they aligned with the system around a month ago - significant drift that has now caused a complete reversal of some work.

My fault. Don't trust your agents - no matter how clear cut your prompt is.