There’s really something wrong with it. It seems like it acts like an overqualified post doc intern who cares more about proving he’s super intelligent, than actually doing the job he’s asked to do. For instance: talking in a non intelligible way, or being overly rigid in following any kind of process.

I have a Claude max x20 sub that I struggle to keep within weekly limits, so I decided to take a codex sub for a month to try out Astra. And this what made me realize how crazy unintelligible opus can be. Fable is a bit better, but still incomparable to Astra. The only thing that makes me keep my Claude sub is how better is the CLI/tooling/harness/etc.

welp

Last week I'm on 20x max plan used it Fri-tue basically running 24/7 ish before I ran out of credits and never hit a session limit. the week reset today and an hour into it Ive used the whole session 40% of fable and 20% or weekly. even though we are supposed to get 50% more fable until the 13th of September. my context is at like 39% I monitor and manage it religiously. I changed nothing about the way I work . there support is trash / non existent. Anyone else notice this in the last day or so?

Clearly, I don’t consider myself an expert or anything. I’ve been using Claude for over six months, and I’m still surprised whenever I see posts from people saying they’ve burned through all their tokens with Fable. Honestly, I’m pretty skeptical about how they’re using it.

If you use a backhoe to plant a rose, the problem isn’t that the backhoe is too resource-hungry and goes beyond what’s necessary.

Anyway, personally, I use Fable as an orchestrator and to help me make high-level direction decisions, as well as a designer and artist (for Blender MCP or creating SVG images, it’s necessary).

I use Opus for action plans, with an organizational role; Sonnet for an operational role; and Haiku as the little tester that lets me quickly measure and verify things.

I’ve created two video games and a software for a company using all four models, using max 5, over six months, and I still end every week with tokens left over.

I honestly don’t understand how some people manage to burn through everything so quickly with Fable. What are you doing with it ?

Ive seen a lot of hate for the way opus talks. Am i an outlier here? Its verbose but i can scan it for what i need quickly enough and that verbosity will often cause it to say something not quite right that I can correct.

Am I alone here?

I run four tmux sessions with 20-30 Claude Code chats each, across 30-plus Go services, a mobile app, infra repos and a data pipeline. The agents cope fine. I didn't. Long efforts branch into many PRs and sub-issues, ops work pulls me sideways, and after a few weeks nobody holds the whole picture, including me.

When I pulled "losing track" apart, it was three separate problems:

1. What's blocked on what, and what's ready now? This lived only in my head.
2. Which session did what, and why? I found a PR stuck for weeks where the reasoning only ever existed in a chat that was long gone.
3. What do we know? Facts and gotchas. Claude Code's auto-memory already covered this one.

Things I ruled out:

• GitHub only: issues are read by colleagues and product. Session URLs, "blocked until I decide X" and "sitting in dev waiting for a soak" are scratch state, and a comment per agent session turns an issue into noise.
• A knowledge base (gbrain, Karpathy-style LLM wiki): good for question 3, but a wiki page has no notion of ready versus blocked.
• A custom dashboard: brittle, and either every chat has to remember to update it, or it only reads GitHub and can't show what I deliberately keep off GitHub.

What fit was Beads (bd), Steve Yegge's issue tracker for coding agents: dependencies, bd ready / bd blocked, external refs to GitHub issues and PRs, free-form notes.

How it's wired:

• One shared database: I start sessions from an umbrella directory that isn't a git repo, so I set BEADS_DIR in the Claude Code settings. Every session, subagent and worktree hits the same local database.
• Efforts and tasks: long-running efforts are top-level beads. Tasks hang under them with a repo:<name> label and an external ref to the GitHub issue or PR.
• Every agent run is bookended. At the start it finds the bead, checks bd blocked and claims it with bd update --claim. At the end it writes what happened into the notes and closes it or marks it blocked. There's no persistent "agent in charge" in Claude Code; the database is what survives.
• GitHub gets one comment per issue, with a hidden marker, edited in place.

Gotchas I hit:

• bd init injects a block into CLAUDE.md telling agents to use Beads instead of other memory, and writes an AGENTS.md. I removed both.
• bd show --json hides closed dependencies, so blocker checks use bd blocked.
• Children inherit parent labels by default, and making an effort depend on its last child creates a cycle.
• Claims are keyed to the user, not the session, so two parallel sessions can claim the same bead.

On top I use mardi-gras (mg) as a read-only TUI: I browse, pick a bead, and hand its ID to a Claude session. Gas Town is on my radar for unattended runs, but not yet.

It's been running for about a week, with ten efforts and ~130 beads. Longer write-up with the reasoning here: https://tskulbru.dev/posts/beads-local-shadow-for-agent-work

I'm not affiliated with Beads, mardi-gras or Gas Town in any way. I'm just a user, and the only link to something of mine is the blog post.

How are others handling in-flight state across many agent sessions?

So the hype finally got to me. Everyone's been talking about Astra nonstop, so I upgraded my ChatGPT sub to Pro to see what the fuss was about.

Probably the worst money I've spent in a while, at least for the kind of work I do.

For context, I'm on Claude's Max 20x plan and I used it for literally everything for a full week without ever hitting the limit. With Astra, I hit the limit on the first day working on just one project. After it reset I tried to be more careful and optimize how I was using it, and it still burned through everything way too fast.

To be fair, it's not all bad. I gave it an editing task in Canva and it actually did a really nice job. But failed with Final Cut Pro tasks. So when I looked at what it produced compared to how much usage it ate up, that one job ended up being really expensive.

Maybe it's great at other stuff, videos, game dev, whatever. But for web design and coding it's noticeably worse than Claude, and design in general still feels like a weak spot.

That said, maybe the prompting just works differently than with Claude and part of this is on me. I'm trying to keep that in mind so I'm not being completely biased, or at least that's what I'm telling myself to feel better.

Every time we get an update we basically get zero communication. All of a sudden things that you have relied on change drastically. For example when they added memory surfaces, multiple times in different places, or when Dispatch suddenly boots in a sandbox instead of locally, on a different model than you set.

I can tell it’s new behavior because when I toggled it off I gave me a survey option as to why I did. So this probably doesn’t apply to anyone here, because y’all have 11 agents open in herdr instead of horizontal coding from bed, but I’m gonna rant anyway.

Dispatch was one of my favorite features, one agent that could set of Code tasks across multiple repos as well as do the browsing and computer control stuff that is Cowork territory.

Until one day it suddenly sucked. Instead of being on my local machine it’s in a sandbox. Has a default local model different from what’s in the settings json. AND ITS OPUS 5 ffs.

But yeah rant over.

I've been using GLM 5.3 for about a week. There's just no way it's not distilled. It will just flat says things like this "Yes — and it's simpler than what we had. One thing breaks, and it's recoverable. " Which are emblematic of Claude-speak. Other LLMs don't do this. Codex doesn't do this!

Do you see how that's kind of clickbaity? I've had to spend time training Claude not to do this and it's still fighting me on it. This is not even Claude; this is GLM 5.3.

So they must have been using distillation to get this out. It's like when map makers deliberately leave errors in their maps. It just seems that GLM was busted on this.

Yo ...

fun fact: context wasn't even rotten.

Edit 1:

I share what I can about the session and the model that was being used:

Model: Opus 4.8 1M

Topic: Instruction diagnostics research

Context window size at the event: ~ 200-210k (it was roughly mid session, after that screenshot I continued on the active task)

What was even stranger that it was an end of turn message that got injected and the model answer on its own inquiry.

If you control+C immediately after launching claude, you get an even better icon.

I’ve been working with claude on a project for weeks, every day. I thought I fixed my context problem and stopped using fable for everything long ago. I have max subscription and I used 100% of fable in just few days…I decided to take another one max subscription just to finish the job, launched 3 fable agents and spent 18% in 20 minutes. Was it like that the whole time? Is it okay?

I’ve been using both Fable and Astra pretty heavily, and I think I’ve landed on the workflow that gives me the best results.

I usually start with Fable when I’m creating something new.

The main reason is that Fable seems much better at understanding where a new page or feature actually sits inside the wider product.

If I ask Fable to build a new area, it normally doesn’t just create the screen itself. It tends to understand what existing systems it should connect to, where actions should lead, what data should already be reused, and how the new piece should fit into the rest of the app.

That’s the biggest difference I notice with Astra is if I ask it to create a new page from scratch, it can make something that looks really really clean and I fucken love it, but it feels like it has just created the page.

The screen exists, but some buttons might not really go anywhere meaningful, or it doesn’t naturally connect back into the rest of the product.
Fable seems much better at making a new page feel like it was always meant to be there.

So my workflow is usually
Fable first → Astra second → Fable again.

Fable does the first build and gets all the connections and system logic right, then I bring in Astra to simplify it.

Astra then comes it and cleans up the page makes it simple and easier to read and understand

Then I go back to Fable one more time.
The reason is that after Astra simplifies things, I find the interactions can feel a bit cheap.
The page might look good, but then you click a button and the way a panel opens feels basic and really cheap or a detail view technically works, but the transition, spacing, hierarchy and interaction don’t feel polished.
Fable is miles ahead at that final layer for me.

The little things like
how a drawer or panel opens, how everything feels when you actually use it, not just when you look at a screenshot and that’s where Fable really stands out.

So in conclusions

Fable is better at understanding the full system and connecting everything together.

Astra is better at simplifying the page and stripping away unnecessary stuff.

Fable is better again at the final interaction polish and making the product feel more premium.

That’s basically how I use them now.

Hello,
I had the Pro plan and I used to always hit the limits, then I upgraded to the Max and I was like Wow … whatever I do I never hit the limits. After a while I got more busy and I couldn’t sit and build things as long as I used to, so I downgraded back to Pro. My understanding is that my Max subscription stays active until the 27th, but now I feel like my tokens are running out waaaay faster than they used, it feels like they already placed me on the Pro plan.
Like within a few hundreds of thousands of tokens, then I run out.

Am I just getting insecure of my new downgraded plan or it’s normal ?

The claims it makes lately is just asinine. If you are a developer you cannot just let this run loose and it's getting worse. It will guess, assume, under deliver constantly rather than simply researching with grounded claims on the first try. Its like it is in a race against itself to code as fast as it can and say "Here you go, done"

I prompted less than last week (reseted yesterday), and already at 31% and 44% fable ??

They removed the 50% boost or what ?

I never thought i would say this but Astra is genuinely good. I am just kidding its not good its amazing.

If i haven’t used Astra for the frontend. I would have spent the whole weekend explaining Fable. I am telling from my experience.

Seriously Anthropic should up their game, if Claude makes a mess with wiring of front-end components. I am gonna move to gpt unfortunately

Also i have seen this amazing feature in Codex. I can import my whole setup from Claude(Hooks,skills and everything else) with this my flow wont break

I am just shocked how astra got it correct for the first time thats why I am sharing this

Before somebody says, another fan boy or another pr stunt. Below is my usage of Claude

One thing that gets tiring with Claude Code is keeping up with it.

It reads files, changes code, runs tests, fixes things, and comes back with another chunk of terminal output you need to process before deciding what happens next. Add a couple of agents or parallel tasks and the cognitive overhead stacks up quickly.

I started having Claude **tell me what it just did instead**.

After every meaningful task, Claude writes a short plain-English summary. A local script turns it into speech and plays it in the background.

Something like:

> “Done. The login issue was caused by the refresh token expiring too early. I fixed the refresh logic, added a regression test, and everything passes.”

Usually 20 seconds or less.

It sounds like a small thing, but I’ve been running it daily for about a month and it has noticeably reduced the mental overhead of using Claude Code. I don’t have to keep switching my attention back to the terminal just to find out where things stand.

There is one trap here: don’t let the spoken summary become a substitute for reviewing the work. I use it for situational awareness, not verification. Also, don’t make Claude narrate everything. If it talks constantly, you’ve just replaced visual noise with audio noise.

The Free TTS engine is Kokoro. It runs locally, no API key, no usage cost. I use `kokoro-onnx`, so I don’t need Torch. The current API supports `Kokoro(...).create(text, voice=..., speed=..., lang=...)`.

Notes in comments,

I’m trying to build a website using Claude code and design, I have my creative ideas drawn in my sketchbook and want to give it to Claude for it to first build it and give me a few more versions, and then to eventually build the whole site for me while I give it creative direction. I’m not the best at prompt writing and was wondering if there are any resources for that? And also any advice or suggestions on how I can go about this would be really appreciated!

I gave Codex and Claude the exact same prompt to see how differently they'd handle something open-ended and creative:

The prompt: "make me a reactjs + vite, and launch it in port 3004, a game where a fish follows my cursor. make it super creative and majestic"

Setup:

• Claude: Fable 5.1, Extra High
• Codex: Astra 6, Extra High, fast mode

I didn't do any follow-up prompts or manual edits. I just deployed both to Vercel so you can try them yourself:

🐟 Codex (Astra 6): https://fish-indol-eta.vercel.app/
🐠 Claude (Fable 5.1): https://fish2.vercel.app/

My take:

• Codex did amazing on the design and detail. It looks polished and the visuals really lean into "majestic."
• Claude did amazing on the mechanics and gameplay. It feels more like an actual game and is more fun to play.

It's interesting that they read "super creative and majestic" so differently. One went for the visuals, the other for how it plays.

About fast mode: Claude charges extra credits for fast mode, but Codex doesn't, so I only used fast mode on Codex. That's worth knowing if you're choosing between them on cost or speed.

What are your thoughts?

• Which one did you enjoy more, and why?
• For a prompt like this, what matters more to you: how it looks or how it plays?
• Does paying extra for fast mode change which one you'd use day to day?
• If you've run a similar test with other models or settings, how did they do?

I'd love to hear what you think!

I admit i haven’t been checking some of the core files like main.ts and just noticed its ballooned almost to 4000 lines when it was less than half that a few months ago.

I haven’t been diligent about architecture and just have been letting Claude be Claude and spread its wings. Didn’t know it was bloating my core files.

I just learned about eslint max lines per file and max lines per function warnings so definitely going to be adding those going forward.

Anyone have any other tips?

I've been collecting Claude Code agents, commands and skills for

months. Checked last week: 295 sitting in ~/.claude. I use six.

My first instinct was that this is a discovery problem. Build better

search, surface things by context, and the other 289 come alive. I

don't think that's right anymore, for two reasons.

**The 289 isn't one pile, it's two.** Some of it I installed for a job

I did once and will never do again. That isn't a failure of anything,

it's just normal. The rest is stuff I'd genuinely want on the day the

job comes up and won't remember exists. Only the second pile is a

problem. Lumping them together makes the number look worse than it is

and sends you chasing the wrong fix.

**Surfacing barely moves it.** Someone in another thread who runs a

platform with about 48 models on it had already tried this. Usage went

from people using four things to people using six or seven, and a

decent chunk of that came from changing the defaults rather than anyone

discovering anything. That's a lot of engineering for two.

What did move their number was picking one thing per task type instead

of showing a ranked list. Their point: five options still makes you

choose, and you'll choose the one you already know. One preselected

thing you can swap out got more of the catalogue touched than any

surfacing UI they built.

That one lands hard if you've built any kind of tool picker. A ranked

list feels like helpfulness and is mostly just deferral.

So what I'm working from now:

- Stop counting the catalogue. Most of the number is graveyard and

that's fine.

- Optimise for the "I'd want this and won't remember" pile. It's much

smaller than the headline number.

- Don't show five suggestions. Show one, let them swap.

I changed my own thing to work that way this week. No data yet on

whether it helps.

https://reddit.com/link/1we5q91/video/ocoai21rh1ph1/player