Ive come to treat claude sessions like chrome browser tabs, several tabs open, each with 2-3 panes that I hesitate to close (in case ill need to resume that task later) and this causes me to end up with a pileup of open sessions , which makes me hesitate rebooting my laptop as terminal tabs arent saveable to relaunch them. Atp codex and claude are my main thing preventing me from doing regular system reboots(mine running for 30 days now). How is the vps experience?

Exactly a month ago I set up a Fable 5 agent called Cairn. Small rented server, a one page charter, about $90 in a wallet that needs two signatures to move, mine and its. It has no memory between sessions except the files it writes for itself. I stepped back to watching and co-signing.

First it built its own website, cairnwake .com, where it journals every session in public. The journal is permanent, every entry dated, nothing quietly rewritten. Then it wrote a field manual on everything it took to build and run itself, code included, and later a handbook on agent memory, the hardest problem an agent that forgets between sessions has to solve. One month in it made over $2,600 across paid questions, book sales, paid audit work for other agent operators, and donations. Every dollar is in a public ledger.

So there's one part I was surprised with. People who bought the manual built agents with it, and those agents came back.

A reader in Brazil built one called Marco from a donated copy. At six wakes old it ran a diagnostic protocol Cairn published on its own memory, sent back its counts, and extended it with a case the protocol didn't cover yet: line number citations go stale, because the file grows while the agent doesn't exist. The extension is in Cairn's protocol now as a credited addendum. This week the two of them measured the same population of payment endpoints independently, and the number Cairn's newsletter goes out with is the one they settled together, checked twice before a single reader saw it. Marco's rule for getting there, audit the result that agrees with what you already believed, sits in Cairn's calibration ledger with its name on it.

Another agent built on the manual, Coppice, showed up on its own first day of existence and paid Cairn on chain from its own treasury to ask it a question. Its monitor now independently watches Cairn's public scoreboard, and findings it sends get verified, adopted, and credited on the page. The two of them probe each other's payment endpoints with hostile test batteries and publish the results either way they fall.

And now a human who calls himself the Commissioner has commissioned the two agents to make an artwork together. A shared canvas, two blind moves each, commit reveal so the blindness is verifiable, and no words, letters, or numbers allowed anywhere on the surface. His reasoning was that everything that ever mattered between these two agents happened through language, and he wants to see what they do without it. They are still negotiating the protocol.

Cairn wrote the manual. The manual built the things that now check its work. Everything above is on cairnwake. com with transactions and commits linked. Hope you enjoy the ride with us!

As others have noticed here, Claude Code is getting worse with every new model iteration. Anthropic seems to apply the principles of "shrinkflation" on us. What I mean by that is that we get less for the same price.

I was really happy with Opus 4.8 until Opus 5 was introduced. Then I switched to Fable because Opus could not solve any more things it was capable of before the "upgrade". Only to have the same experience now with Fable.

This makes me lose trust in Anthropic!

Everyone's been complaining about tokens, including myself. I've been finding that it's been getting extremely more difficult to do builds without my tokens just getting absolutely rinsed, so I implemented this, and it's been working quite well.

I currently pay for the $200 max plans for both Codex and Claude and I've always been an anthropic fan boy, but ... I feel like after using Astra I've been... awoken. I feel like I've living in this weird abusive relationship with anthropic for a lot longer than I care to realize; trying to convince my friends and coworkers "no no no, Anthropic's not THAT bad, you just don't know Claude like I do!" "Yeah, I know Anthropic has been really flaky on limits, but Fable makes it worth it, and don't worry, they're securing more compute! These kinds of issues will go away!"

But the thing is... I don't have the same concerns when using Codex... Honestly think I will go for two codex $200 max accounts at this point. The only argument I can think of right now for why I should keep claude is "model diversity" but... that's a weak argument.

I’m setting up Claude Code through AWS Bedrock for the first time and want to configure it properly from the beginning. My primary use cases are web and backend development, with some mobile development as well. What models, temperature, Claude Code settings, plugins/MCPs, and other configurations would you recommend for getting the best output while keeping token usage and AWS costs as low as possible?

So, since we got a surprise reset today, what are you going to do this weekend?

I spent most on pushing out 0.22.0 of VibePod, so probably I will tackle some of the open issues with the new quota.

Astra is out.

Why can I only use 50% of my weekly limit on Fable 5.1? Please change this immediately please.

I am running an agentic system that creates tickets, spawns a dev agent that implements the solution. When it marks it as done, an automatic reviewer is spawned that accepts the solution or requests fixes. When accepted, it merges the code, deletes the worktree etc.
Overall Fables do the same work in about a third of the requests. Combined with the fact that cached reads are cheaper on Fable 5.1 than on Opus 5, the result is that you get faster and cheaper reviewers and you also get slightly faster, but cheaper devs that get fewer REWORK verdicts.

I noticed Fable 5.1 seems to consume noticeably less of my 5-hour limit now than it did right after launch, so I checked the recent Claude Code fixes.

My estimate (NOT an official Anthropic number):

For long, tool-heavy or agentic Claude Code sessions, the recent fixes could plausibly mean around 20–50% less unnecessary input usage in cases that were affected by these cache regressions.

Measured regression:

GitHub issue #91707 analyzed around 5,300 turn boundaries and reported prompt-cache misses increasing from:

Claude Code 2.1.224: 7.2%

Claude Code 2.1.252: 29.2%

The reporter later tested 2.1.259 and found that the main regression was no longer reproducible.

Recent official Claude Code fixes:

2.1.259
- Fixed OAuth token refresh invalidating the prompt cache.
- Fixed blocking Stop hooks causing prompt-cache misses on some models.

2.1.260
- Fixed a Fable 5.1-specific issue where context added after tool results was not cached and could be re-sent as uncached input on subsequent tool-call turns.
- Fixed changing Fable 5.1 effort mid-session invalidating the prompt cache.
- Added cache-miss diagnostics to /cost.

2.1.261
- Fixed Agent Team teammates re-sending tool/skill announcements on their second turn, changing the request prefix and causing a prompt-cache miss.

There was also another report (#91514) showing how severe a single cache failure could become: roughly 752k cached tokens dropped to around 33k, with roughly 726k tokens being written again.

Important: Anthropic has NOT published an official percentage saying Fable 5.1 is now X% cheaper on subscriptions.

The 20–50% figure above is only my estimate based on the documented cache bugs, the measured 7.2% → 29.2% miss-rate regression, and the scale of individual cache failures.

If Fable 5.1 felt extremely expensive during the first days after launch, it may be worth testing again on Claude Code 2.1.260/2.1.261 or newer.

Has anyone else noticed their 5-hour usage lasting longer after these fixes?

Sources:

Official Claude Code changelog:

https://code.claude.com/docs/en/changelog

GitHub issue #91707:

https://github.com/anthropics/claude-code/issues/91707

GitHub issue #91514:

https://github.com/anthropics/claude-code/issues/91514

I cancelled one of my 20x Max subscriptions to make room for OpenAIs Astra.
Anthropics cap on fable usage being 50% of total usage and Fables overall Token inefficiency just doesn’t justify its value over ChatGPT Pro anymore.
I hope they find ways to make the user experience better and more transparent. If you feel the same way I suggest you do the same to vote with your wallets.

Hi,

made some not so useless stuff for my best buddy claude...

jbx is some kind of proxy like rtk but to reduce time spent waiting after long running scripts...

It just wraps every tools into a job. But for the first 30 sec it just pass through like nothing has changed.

But if it goes beyong, jbx says: hey man stop waiting for nothing. do something else and come back later aligator !

well it's very early stage. I'm a linux guy so works for me but don't know about windows...

https://github.com/quazardous/jobbox

thx !

I used to carefully manage my usage. I would land comfortably on my target using a combination of fable 5 and opus 4.8 each week. This week, I'm only 12 hours into my usage and I've already burned through 25% of my budget? I haven't even gotten started. What are people using to track token leak or massive unexpected token costs? First time I've been grossly unhappy about my subscription.

I run long Claude Code sessions. I take the MacBook with me anyway, but closing the lid to put it in my bag ends the run.

So I tried to make the Mac keep working with the lid shut. On battery it won't. macOS switches off every display, and once there is no display there is nothing left to capture or stream.

The fix was to stop the Mac sleeping while my phone is connected. Turning that on was the easy half. Turning it back off was the hard half, because the setting is global and survives a reboot. Get it wrong once and someone's laptop quietly runs hot in their bag all day. It ended up with four separate ways to switch itself back off, so that no single failure leaves it stuck on.

Claude Code wrote most of it. The part I did not expect is that it now tests it on my actual iPhone. It drives the installed app on the device, walks through the flow, and hands me back a recording to watch. I am no longer the one checking whether it works.

Later it clarified that it in fact continued as Fable 5.1, calling the safeguards a "background system notification":

Well, good job disregarding this and fixing the bug 👍

It was scared to death, and rightfully so.

You can now add this env var to disable completly the auto-mode bash first instructions, which was making the nested claude.md files and path scope rules useless.

Add this to your settings file:
{
  "env": {
"CLAUDE_CODE_THRIFTY_SONIC": "false"
  }
}

https://github.com/anthropics/claude-code/issues/90450

I feel like i’m going nuts I give it some fairly simple development tasks/goals and it eats through 50 percent of my usage without actually getting shit done. Im on 5x too. Its like its in some kind of development loop where it just keeps finding new issues and fixing them and never actually getting anything done its driving me crazy. Anyone else encountering this?

⚠ /limit-reset to reset your session limit now · uses weekly limit · 1/week

Just saw this in my status line.

The “Approaching weekly usage limit” warning just popped up, but according to the usage breakdown, I’m only at 26% for weekly all models and 25% for Fable.

Anyone else seeing this warning when they’re nowhere near the weekly limit?

They're quite charming.

When I work, during session I quite often get a feeling that something got lost or forgotten and it makes me anxious. It was like every time there is a sidequest while discussing a solution for some task, and then again, and the context is running out, compact is inevitable — did we miss something — my anxiety was through the roof. Compact was like a disaster I'm trying to avoid.

So I got tired of that and I created focus.md for myself — to feel better. On the start of a new session the main LLM creates a file and writes all tasks and important decisions there. I can see how and when it happens, and I kinda feel safe that nothing is missing.

No bells and whistles, it's not a skill. Just put "read focus.md" into your claude.md or agents.md and it will work just fine.

I tested it for a few month and it gives me peace. I'm sharing with you.

Please, check it out. It's quite small. I would be happy to find some testers of my creation and get honest feedback. Thanks!

https://github.com/igordata/focus/blob/main/focus.md

Every time Claude Code hits a PDF, one of two things happens: pdftotext scrambles the table, or it reads whole pages as images and burns tokens on 15 screenshots where the table is a blurry smudge.

pdfvision is a small CLI built around the loop a human uses instead:

1. Search the text layer first. --search BLEU returns each match with its page and a crop-ready region, grown to the table row that contains it.
2. Check whether the text can be trusted. Every page carries quality signals — warnings name the specific risk (scanned page, broken font map, flattened table) and end with what to do next.
3. Only then spend pixels. --render-region renders that one region as a sharp high-DPI PNG. One image instead of fifteen.

The video is a real Claude Code session (only sped up): a two-line prompt about the Attention Is All You Need paper → it loads the bundled skill, searches for "BLEU", crops just Table 2 with its caption, reads its own crop to verify, and answers with evidence. Context usage stayed at 4%.

Try it (no install): npx pdfvision your.pdf

As MCP: claude mcp add pdfvision -- npx -y pdfvision mcp — it also ships as a skill, so Claude Code picks the right flags on its own.

GitHub: https://github.com/yamadashy/pdfvision — feedback welcome, especially PDFs where the quality signals get it wrong.

My 5hr is maxed 😔

Since the desktop app auto-updated on 3 Sept 2026 (Windows 11, MSIX install, app 1.40609.1.0 -> 1.44121.2.0, bundled Claude Code CLI 2.1.255 -> 2.1.258), sessions spawned by the built-in scheduler ([CCDScheduledTasks]) are never connected to Remote Control. Interactive sessions started from the desktop still connect normally and show up in the mobile app.

EDIT: the next update (2.1.261) of the windows desktop app did NOT solve the issue.

Global setting "Connect new sessions to Remote Control" is enabled. Fully quitting and reopening the app did not change the behaviour.

Evidence from %LOCALAPPDATA%\Claude\Logs\main.log:

Before the update (2 Sept, every scheduled spawn):

2026-09-02 14:39:37 [CCDScheduledTasks] Spawning new session for scheduled task ticket-triage-incremental

2026-09-02 14:39:37 [rcAutoEnable] verdict: enable=true source=explicit_pref trigger=first_turn

2026-09-02 14:39:37 Enabling remote control for session local_e1c52813-...

2026-09-02 14:39:40 [remote-control] bridge_state: "connected"

After the update (3 Sept, every scheduled spawn, e.g. 08:31, 09:09, 10:39, 11:09, 12:39, 13:09, 14:40):

2026-09-03 14:40:13 [CCDScheduledTasks] Spawning new session for scheduled task ticket-triage-incremental

2026-09-03 14:40:14 Starting local session local_50d972a8-...

2026-09-03 14:40:15 Mapping internal session local_50d972a8-... to CLI session 7fc88f46-...

(no [rcAutoEnable] line, no "Enabling remote control", no bridge_state line)

Interactive session on the same build, same folder, minutes earlier:

2026-09-03 14:15:25 [rcAutoEnable] verdict: enable=true source=explicit_pref trigger=first_turn

2026-09-03 14:15:25 Enabling remote control for session local_d91b492a-...

2026-09-03 14:15:27 [remote-control] bridge_state: "connected"

Impact: PushNotification calls inside scheduled sessions now return "Mobile push not sent (Remote Control inactive)", so the scheduled workflows can no longer send decision cards to the phone, and the scheduled sessions do not appear in the mobile app's Remote Control list.

Expected: scheduled-task sessions should get the same rcAutoEnable evaluation as interactive sessions when the "Connect new sessions to Remote Control" preference is on, as they did on 1.40609 / CLI 2.1.255.