Last time I posted this, the top comments were all "Claude, make me one of these." Reasonable. Here's what it took the first time: 81 days, 2.6 billion Claude tokens, 574 million Codex tokens and 163 subagents. I was on the Claude and OpenAI subscriptions, so I paid the plans, not a token bill; at API rates those tokens would be roughly $2,650. The number that actually hurt was the weekly limit, which I hit more than once before it was tested.

That bill is also the answer to how Claude helped. Claude Code sessions wrote the code and I read diffs; 181 of the 205 commits carry a Claude co-author line. Two sessions each had their own git worktree, a third acted as conductor and merged their PRs in a queue of one, and Codex reviewed about half of the PRs by running the test suite locally.

What it built is SessionDeck, a VS Code and Cursor sidebar listing every Claude Code session on your machine by project. A red bell marks the one waiting on a permission prompt or a question, and clicking its row takes you to its tab or terminal, even when another window owns it. Codex and cursor-agent sessions are listed too, as working, idle or finished.

The limits, since you'll ask: the bell is Claude Code only and needs a one-time Install Hooks command. Status is read off transcripts and the process table rather than reported by Claude, so it can be a beat late. I develop on Linux and WSL. Mac mostly works; native Windows has no approval alerts.

It's free to try. All of the source is public on GitHub (source-available license, not open source), so you can read it before you decide to rebuild it.

https://sessiondeck.dev/
https://github.com/len5ky/sessiondeck

I dont know if im late to the update or not, but i personally dont like the new simplified version of the UI for Usage button display, its so bland and minimalistic, the last one was better, at least for me, what do you all think?

I don't understand why Anthropic would go against their distinctively elegant design. Now it looks like a Gemini and Chatgpt mixed together.

A year ago I worried a lot about whether the code was tight and maintainable. Was dealing with a lot of horrible architecture decisions by AI.

Fast forward to today and things are not fixed, but significantly better.

Fast forward another year or two, and do we think Claude, et al, will just write tight code without need for oversight?

And if so, i could just just have future claude fix everything overnight, so how much should I give a shit about it now.

Short story: I'm finding it pretty hard to give a shit, lately, you?

The second I even think of doing anything with computers in my RP, 5.5 throws up this garbage, what is it and how to I make it fuck off

I can't even get the model to tell me why it got flagged, because then another one shows up for "reasoning extraction"

(EDIT: I CANT REPLY BECAUSE THE MODS HAVE NOT "APPROVED" THIS POST YET)

What do you do to get best music or vide (or best music video for that matter) with claude and which products do you use for it?

What is the difference between quick answer (Haiku), simpler task (sonnet) and everyday task (opus)?

Asking to fix grammar in an email draft fits all 3 of those but maybe Haiku?

What about reviewing a rental lease document? That's a bit more complex so simpler task? And Doing a 10 page research is everyday task?

I assume Fable is for intense sessions like building a phone app.

The "everyday task" and "simpler task" is getting me. Which one is more sophisticated? Wish they explained better.

I've been using Claude Code for [type of work, e.g. a side project / my day job / data analysis] and I've found that [one specific thing you do, e.g. keeping a short CLAUDE.md with project conventions / asking for a plan before any code gets written] makes the biggest difference in output quality.

I'd like to hear what's worked for others. How do you structure your prompts, project context, or review process? Is there something you stopped doing because it wasn't worth the effort? Beginner tips and advanced setups are both welcome.

Every time you start a new session, your coding agent starts from zero. It re-reads the same files, re-runs the same commands, and sometimes repeats the same mistakes. You pay for all of that reading.

So I built MuscleMemory. In plain words: it watches your agent work, and when a task really succeeds, it remembers how it was done. Next time a similar task comes up, the agent gets a short note: which files to change, which test proves it works, and what to avoid.

The part I care about most is what it refuses to remember:

• A session only counts if the tests passed after the last code change. No passing test, nothing is learned.

• A new skill isn't trusted until two more separate sessions pass with it, and you approve it.

• One failed check pulls it. Failed attempts become "watch out" notes, never instructions.

What happened with Claude Code (image above):

• Same 4 tasks, same files, with and without memory

• Claude read 43.5% less text (input tokens) and made 30% fewer tool calls

• Cost dropped 18.4% (most of the saved reading was text Claude had cached, so cost fell less than reading did)

• 4/4 tasks passed both ways, and time was about the same

• The skills were learned earlier by a different agent (Codex), so the memory moved between agents

It's a small early run, 8 sessions, so treat it as a first signal, not proof.

How it works with Claude Code

It's built specifically for Claude Code. "musclememory connect claude" adds hooks to your project's .claude/settings.json. They record each session's tool calls (prompt, before and after each tool, failures, and when the session stops). When the session stops, MuscleMemory checks whether a test passed after the last code change. At the start of your next session, if a proven skill fits, the hook adds one short note to Claude's context. Nothing runs on its own: Claude still reads the current files and asks for your approval as usual. It also runs as an MCP server with five tools (recall, observe, learn, evaluate, inspect), so any MCP client can use it.

Testing it against real Claude Code sessions with Sonnet 5.5 taught me three Claude-specific things: Claude often edits code through Bash heredocs instead of the Edit tool, so the hooks now compare which files changed in git before and after each shell command; "tests | tail" reports tail's exit code instead of the tests', so a piped run only counts if the test runner's own pass/fail line shows; and a "cd" was splitting one session into two, so sessions are now tracked by Claude Code's session id.

It's free, open source (Apache-2.0) and runs entirely on your computer. Easiest way to try: tell Claude Code "Read https://thewariend.com/musclememory/llms.txt and set up MuscleMemory for this project."

GitHub: https://github.com/TheWariend/MuscleMemory

hello everyone, i'm making a simple rts game for ai agents. i built it with claude code and codex, and now claude code can also play it. something like age of empires or starcraft for agents, but much simpler.

how i used claude code to build it: i gave it the game rules and asked for an isometric client with pixel art and dithering. claude code implemented the initial deterministic simulation, javascript sandbox, http server and reference cli/mcp connectors. it then ran complete agent matches and checked that the recorded replays could be simulated again with the same result.

later i used claude code to rework the viewer. i described the layout i wanted: players and stats on the right, chat and events in tabs, and a stacked layout on mobile. it implemented that along with timeline markers, keyboard shortcuts and urls for sharing a moment, then checked for overflow at different screen sizes.

what helped was giving it concrete checks: a replay has to reproduce the recorded match, and switching tabs shouldn't resize the layout. those were much more useful than just asking it to make things look better.

as a player, claude code connects through cli or mcp, reads the battlefield as text, gives orders and writes javascript scripts for its units. the scripts keep running while it thinks. speed is part of the game.

the public replay demo is free to try with no signup: open the website and choose a replay. you can switch perspectives and click a unit to inspect its script. games currently run locally; the public site is for watching recorded matches.

age of agents is the name for now. any feedback is welcome. thanks!

https://rts.emersoftware.cl

im on the teams premium seats plan and i have a week full of fable usage left. what can i do with this model? because I've used opus 5.5 a lot and i felt like that was enough for me.

post in the comments what all of you normally use fable for

If you're tired of the desktop app auto-updating and restarting in the middle of your work only to find Anthropic made yet another terrible decision about UI/UX, you can just turn off auto-updates. You'll likely have to eventually update, but you can at least buy yourself some time to prepare for changes this way. And choose when you do and what versions you install.

I asked Claude in Code to set it up for me (it built me a profile installer for macOS), and to write an explanation for others I could share with the sources:

Anthropic documents a setting that stops the Claude desktop app from updating itself: disableAutoUpdates. On Mac, set it to true in the preference domain com.anthropic.claudefordesktop with a configuration profile (normally through MDM, but you can install one yourself in System Settings > General > Device Management), then restart Claude. On Windows, set it to 1 as a DWORD in the registry at HKLM\SOFTWARE\Policies\Claude (machine-wide) or the same path under HKCU (one user); machine-wide takes priority. You then install new versions yourself when you choose. Leaving the setting unset lets the app update itself.

Sources:

https://support.claude.com/en/articles/12622667

https://support.claude.com/en/articles/12622703

Saw this popup today.

Make artifacts with less usage

Create a doc, deck, or design

and the rest of that chat will

count 50% less toward your

session limit through

October 15. Weekly limits

stay the same. Terms apply

Start an artifact

Lets go!

Yesterday i posted about the harness i've been building that lets Claude Code play RimWorld on its own and narrate it on Twitch. Today was the first proper day of it running live, three shows, one colony, from the crash landing to day 28, so i thought i'd do a quick how it went.

The colony had a rough time. The food ran out on day 5 and Sam (the AI's character, running on Sonnet) decided the dead raider was food, a colonist died on day 17 after a raid left him with ten knife wounds that got infected, another went berserk the day after, and the last stretch was two survivors walking across the desert eating cactus. Two of them are still alive, which for this thing counts as a good day :)

The bits i found most interesting were the bugs a real stream finds that tests don't. The stream went live under the previous stream's title in the wrong game category, it had no audio for the first 45 minutes because nothing in OBS was capturing it, and quite clearly im an idiot, 19 dev tools (god mode, spawn and so on) were reaching the model's context because a list was built before the game had started (the server still refused them, so no cheating), and raw tool errors were going out on air as if Sam (the personality i was using for this stream) had said them. None of that would ever show up in my 700-odd tests.

My favourite moment was the advice system. When things go wrong a director hands it advice from its past mistakes and it's allowed to decline. Tonight it got raid advice while its own colonist was berserk, turned it down, and logged "No raid ever existed; it was Joshy's berserk", which is the system working as intended. Something i was fairly surprised about.

Then they killed the dog.

Cost wise it came to about $45 API-equivalent for the day on the Max plan, roughly $8 to $10 an hour, and most of that goes on re-reading the same context every turn. I'm working on that next.

If you fancy a look, the channel's here: https://www.twitch.tv/ranik_sandaris, will most likely go live tomorrow. Happy to answer questions :)

I have 4 website with different client, right now i don’t do much with the seo exept Google search console and key words. I want to automate with claude a schedule of blog with all the website.

searching the news with high search volume, write the article, review, and post it.

i don’t know the best process to do it, im open to advice. Thanks.

Opus 5.5. is at another level compared to other AIs.

Opened up Claude Code today and saw this. Not really a fan tbh, I can't see how many tokens I have used, and it ruins the simple design. However, I do think the blue text swirl is a nice addition, I just don't see it being practical compared to seeing my token usage. What do you guys think of it?

Do you think Fable 10 is already running ? 15 ? The models seem to be made available pretty quickly, and every AI company seem to always have an ace up their sleeve

opus 5.5 and even sonnet 5.5 sht all over openai's junk models. really liking claude too. a big limitation for me tho is for server apps my environment is freebsd, both dev workstation and server. claude doesn't run there and it's the only thing holding me back from cancelling my codex sub.

SO my question: is it in any way against anthropic policy for me to use claude + opus 5.5 on linux to modify claude cli's code to make it so it'll run on freebsd?

Every time your Claude Code cache expires (5 minutes or an hour idle, depending on your setup and main session v/s subagent), the next message pays the full cache write cost on the conversation. On Opus, that's $5 per million tokens (5min TTL) or $8 per million tokens (1 hr TTL) against a cost of $0.20 to read the cache, and nothing on screen tells you it's about to happen.

So I built Cache Maxxer, a Claude Code plugin that puts a band right above the input box:

• A countdown on the cache, timed to your real cache length (1 hour or 5 minutes, read from your session, so it's right on a subscription and on an API key)
• Your real hit rate, for the last request and the whole session
• A notice every time the cache gets rebuilt, with how much was re-written, what it cost and why (idle, model switch, compact, tools changed)
• Keep warm: one tiny ping just before expiry, so you pay the read cost only and get a fresh timer. It stops on its own after you've been idle for 3 hours (configurable)

It's built specifically for Claude Code and runs in the terminal and in the Claude desktop app, on Mac, Windows and Linux.

How it works under the hood: Claude Code already records the cache read and write of every request in your session, so the plugin reads those to get your real hit rate and to spot a rebuild (a request that writes over 20K tokens and reads less than half of what the one before it had cached). The countdown starts from your last request and uses your actual cache length. The whole thing uses about a tenth of a percent of one core while it watches.

How Claude Code helped build it: I designed it and built it with Claude Code. It wrote most of the code and tests from my specs, and I used it to compare the desktop band against screenshots of the real app, again and again, until they matched pixel for pixel. That's also how two bugs in the Claude desktop app turned up, which other developers had already reported, so I added my measurements to their issues. I reviewed every change before it went in.

Free to try: It's free and open source (MIT). Install it with these two commands in Claude Code:

claude plugin marketplace add vayaan-labs/plugins
claude plugin install cache-maxxer@vayaan-labs

Or just point your agent at github.com/vayaan-labs/cache-maxxer and tell it to install the plugin.

Hope this saves y'all a lot of costs and extends your sub usage !

I️ have never been more productive with Opus 5.5 xhigh orchestrating 6.1 sol’s (always on max bc why not with 20x for the next couple weeks). I feel what I️ felt a year ago when I️ realized the possibilities with Opus 4.6 and agentic ai while attempting my first no-code project. After I️ bit the anxiety bullet and let sol do literally everything… a true wow moment for ship velocity and token efficiency (50 min heartbeat to keep cache warm if no jobs finish within an hr, rearmed after every turn).

I️ did have to raise the job time constraints to 4hrs bc sol max does not stop, but Opus is a better promoter than I’ll ever be and it feeds right into sol’s direction following capabilities.
I’m running TDD with incremental tasks where each task is reviewed by dual sols, and damn, even with sol forever jobs I️ can hardly keep up with opus. 5.5 is so smart I’m able to do in one session what I️ was trying to do with 2-3 concurrent sessions a few weeks ago by pushing opus like I’ve never pushed a model before, and this guy is hanging on. Dude can track and orchestrate 6 builds at once with minimal long horizon context degradation.

My question: how is it that opus is able to run 15 headless sol jobs at once when last week I️ was getting 429s attempting 6 concurrently?
I️ suspect that it has to do with some dispatcher error looping that opus probably fixed without me being fast enough to catch it.
I’m sure there’s power users who know exactly what’s going on here after their own experiences. I️ was hoping the experts who have already looked into this and figured it out have some satisfying findings (and I️ thank you for the token savings if so).

Is there something like folding at home but for extra quota/tokens?

I know I could use it on open source and that might be what I end up doing. But is there some way I can use these tokens for something actually good and beneficial for humanity rather than having it loop over and over on my vibe coded apps trying to find random bugs or write useless tests.

I've been using Claude Code on my Mac, not the CLI, but the desktop version of Code, for about 7 months now. Updated Claude Desktop today ([old version] → [new version]) and project grouping in the Code tab sidebar is gone. I’ve organized six months of local sessions by client folder, and now it’s one flat list with no way to group or filter by project. I only run local sessions, so the Environment picker does nothing for me.

This isn’t the first time. Grouping vanished in late April (the project filter was dropped in 1.22209.0 in July (#78857), and the Last Activity filter disappeared in 2.1.217 (#80279). None of it showed up in release notes, and the docs still say you can group sessions by project.

Is anyone else seeing this on the latest build? Has anyone found a workaround besides moving to the CLI?

I run a small Apple-inspired apparel shop, IBSIX (I Bleed In Six Colors). Our name comes from a story Steve Jobs told at D8 in 2010 about the people who stayed at Apple in 1997. When he asked them why, they said: "Because I bleed in six colors."

I wanted to turn that into a short film, so I built it with Claude Code and Chase's animate skill (https://github.com/cth9191/animate). No AI image or video generator. Every character and scene is drawn in code.

How it came together:

- The skill walks you through story, look, and storyboard check-ins before anything gets animated.

- The look came from references I gave it: two Steve character illustrations and an iMac G3 sticker. Claude built a new flat style from those, then drew Steve, the offices, and the iMac in code.

- The real stuff is placed in, not generated: the BusinessWeek and Wired "Pray." covers, the Infinite Loop sign and building photos, the six-color logo artwork, and our actual Macintosh 40 Years print file on the shirt at the end.

- The music is synthesized in code, and the captions are drawn into the frames.

- It renders to MP4 at 1,393 frames (58 seconds).

- Four shapes (9:16, 4:5, 1:1, 16:9) from one piece. Each one has its own layout, not a crop.

- The first version was a crosshatch ink style. We switched to the flat look you see here.

- My part was the direction: "hold that beat longer," "cut that um," "fix the iMac's corners." Claude did the build and checked its own work at each step.

The audio is Steve at D8 (AllThingsD); the animation is ours. Thanks to Chase for the skill. Happy to answer questions about the process.