Hi all,

No layoff talk brewing at my company. Yet.

But I’m definitely at the point where the model is so good, I crush anything that is assigned to me in 1-2 hours. I’m having a hard time filling an 8 hour workday.

All tech debt : gone. I solved it.

I ask for more work: “we’re still gathering requirements.”

I’m worried that it is only a matter of time before senior leadership notices that there isn’t enough work to feed the amount of devs we have.

I feel like Opus 5.5 was another inflection point. Previously, I had to build sophisticated orchestration, baby sit models, and curate context. And that took a lot of my time. This model needs very little of that.

I am loving that handoffs can happen when context gets full and you just click a button and claude spins up a nested session under main session - saves so much time rather than manual handoffs i was doing before. Claude even suggests when to move it to new session

apologies if this has always been there and I just discovered it but I am pretty sure this a new feature on the desktop release

I use Claude Code for a lot of browser work. Mainly tools I need that were never built for agents, smoke-testing my work and searching the web for things I care about.

What I struggled with:

• chrome-devtools-mcp likes to open throwaway instances and profiles, and rarely cleans them up.
• "Allow remote debugging?" prompts on every connect (when using --autoConnect).
• "Chrome is being controlled by automated test software" on top of every page.
• A dozen windows and no idea which tab belonged to which session, or whether I could close it.
• Agents stepping on each other by taking over each other's tabs. --isolated solves that, but doesn't persist logins.
• Gigabytes of RAM with multiple chrome-devtools-mcp processes (about 270 MB each) and chrome instances. Often upwards of 4GB.
• I tried various Cloud browser services, but most are unreliable and/or expensive. And most sites get blocked by bot detection due to non-residential IP address.

I forked Chromium and I call it Shuttle:

• Every agent is a named identity (name, color, avatar) with its own storage. My agents log in once, and stay logged in.
• Agents get their own control plane: create agent profiles, sessions and tabs over MCP.
• MCP server is built in (http, loopback-only by default). So no middle-man needed.
• Every agent works in its own tab group in your window, color-coded. This is the biggest UX improvement for me, as I can clearly see what each agent is doing.
• No DX friction: no debugging dialog, no automation bar, navigator.webdriver is false, and no window pops up until an agent needs one.
• Clean & minimal surface: 12 browser tools + 24 page tools. Vercel's awesome agent-browser is bundled in, so tool calls are directly controlling the browser.
• Per-session CDP endpoints for Playwright if needed, e.g. for scripted e2e tests.
• Meticulously removed bloat from Chromium: Google sign-in, Profile Sync, Telemetry, Google AI features, Translate, Password manager, Chrome Apps, Bookmarks, and many more.

How it was built:

• ~43 fork commits over two weeks, mostly written by Claude Code. Chromium itself is well maintained, so most of my own code and review effort went into my own additions (MCP server, agent model, the removal batches).
• Five agents (mostly Opus 5.5 and Fable 5.1) across three devices (Mac, Linux, Windows/WSL2), with lead agent curating sessions; handoff workflow keeping sessions mostly under 300k context size (my personal sweet spot).
• Removal done as scout → 3–5 surgery sub-agents per batch with a strict keep-list (biggest batch: 5,572 files, 1.18M lines in one commit).
• Fable/Astra adversarial reviews before every commit.
• Recent Chromium 155 merge was the real test for maintenance: 453 conflicted files, zero after 20 minutes with 5 parallel sub-agents... but then a full day of builds (still painful).

Site: https://www.shuttlebrowser.com

Beware: Some humor and easter eggs hidden on this site.

Code: https://github.com/shuttle-browser/shuttle

Regarding Stealth/Bot-detection: Shuttle isn't per se an anti-detection browser. However, it does work closer to a "human operated browser", as Agents are treated like "real human operators". If you're looking for a solution to crawl millions of linkedin profiles or scrape reddit posts at scale, this is not for you. But if you like to operate websites "like reasonable humans", you're good.

Disclosure: I'm promoting my own tool. It's free and open source (BSD-3). I hope others use it, like it, and share their feedback and ideas with me.

Maybe it is just me, but definitely feels like I'm hitting my limits a lot faster.

And I'm on the 20X plan. Never was an issue until past 48 hours.

I really feel like this is kinda more complicated than it needs to be. I loved it before where you finally could select model effort with the slider, see usage and context (with the stacked bar graph showing what is messages, mcp etc) in one go/ area. I feel like this is a step back.

Is there a way to customise it to go back or is that something only anthropic can do?

I recently taught a buddy of mine to use claude code, and he’s starting out on the $20/mo.

After months of using fable for 4-10 hours a day here’s what I noticed.

1) It’s still opus. It’s hard to describe but the feeling when talking to it is still a generation behind Fable. It gets hung up on small things and keeps bringing it up if you dont answer. It’s less likely to preempt solutions. It’s more verbose. And overall it just reminds me of the slog of developing with opus 4.7-4.8

2) It’s still very capable and you can definitely get it to do very complex and long horizon tasks, much closer to fable than the 4.x generations. (I had it help me get a website up and running using firebase+github+vercel + setting up DNS)

3) If anthropic charged $500 for fable i’d still pay for it. The frictionlessness of fable and it’s ability to be in lock step with you as you develop bigger and better products/integrations/modalities is simply unbeatable.

Has anyone gone from fable to full time opus and been happy with the “downgrade”. After my buddy saw what opus could do he was astonished that there could be a model that was worth $80/mo more.

as soon as you wake-up ping your bot so your 5h limit get triggered and when you finish getting ready and having your coffee and morning time waste there will be like 2 hours left of the first 5 hours then 5 hours after that . like this .

you have two 5h usage in span of 7h .

To see how much of my limits I had left, I always kept a few browser tabs open with the usage pages and kept switching to them. So I built a usage monitor I could just glance at instead, and tried to design it to take up as little of the screen as possible while still looking nice.

The result is OrbMet: a small black strip on the edge of the screen with one ring per tool. The ring fills as you use the limit and only turns yellow and red when it starts to matter. Hover it and you get every limit (5-hour, weekly, per model), when each resets and how long that is from now.

• Windows 10/11, free and open source (MIT), no account, nothing sent anywhere
• Claude Code via its own status line (one click to connect, your existing status line keeps working and comes back exactly as it was if you disconnect)
• Codex via codex app-server, nothing to set up
• Optional notifications at 75/80/90/95%, a fold-away mode, multi-monitor, and it never steals focus from the terminal

It's not code-signed yet, so SmartScreen will warn on first run. The README explains why and how to check the download's SHA-256.

https://github.com/29ardayildiz/OrbMet

Built with a lot of help from Claude Code itself. Happy to hear what's missing or broken.

How I built it with Claude Code

I designed it and made the calls; Claude Code wrote nearly all of the code (C#, .NET 10, WPF) and the tests. What worked well for me:

• Keeping a design doc and a project doc in the repo that Claude Code reads at the start of every session, so decisions (colours, what happens when data is missing, how the strip docks) don't get re-argued.
• Making it verify things by measuring, not by reading code: offscreen renders of the strip, real-mouse drag tests, and reading actual provider responses before writing a parser.
• Small steps: one feature, build, tests, I try it in a debug copy, then commit. ~350 tests by now.

Things I learned along the way

• Claude Code only reports rate limits to its status line, so OrbMet connects as a status line helper that keeps your existing status line running and restores it exactly on disconnect.
• Codex has a proper JSON-RPC route (codex app-server) that gives the limits with the sign-in you already have.
• Missing data is not 0%. If a limit's reset time has passed, the old figure is hidden until new data arrives instead of being shown as the new period's usage.
• A window that never steals focus from the terminal on Windows takes more than one flag; it had to be checked with real clicks.

Edit : NOT fixed.

I can confirm that the issue seems to have been resolved today. However, we've already burned through a significant portion of our weekly quota because of it.

Personally, I have four days left until my quota resets, with only 30% remaining. Most people in the original thread reported similar usage issues, although there were some differences from one user to another.

Even if usage is back to normal now, the damage has already been done. Those of us who experienced unusually high usage are still left with depleted quotas for the rest of the week.

Anthropic shouldn't just fix the issue and leave it at that. Given the impact on users, I think they should make another gesture to compensate those affected.

Original discussion: https://www.reddit.com/r/ClaudeCode/comments/1x64hj9/comment/pgx8ai2/

New Claude Code UI update. What do you guys think?

When I run a few Claude Code sessions that each spawn sub-agents, I lose track fast: which agent is still working, which one is waiting on another, which session is sitting on a prompt for me.

Agent Standup reads the session files Claude Code already writes in ~/.claude/projects and plays them back as a live call (video above). Under the cartoon there's the part I use most:

- a board of every session: working, waiting, or needs you

- tokens per agent, to spot the expensive sub-agent

- a flag when a command runs over a minute, or an agent goes quiet for 3 minutes

- replay of any past session, with a recap of commands and files changed

- a one-line status for tmux or the Claude Code status line

It costs zero tokens, nothing leaves your machine, it's MIT, and it also reads Codex and Mistral Vibe sessions. It runs in VS Code and Cursor, in a terminal, or as a desktop app.

Try it with a built-in demo: npx u/double_geste/agent-standup --open

Repo: https://github.com/Atoll92/agent-standup

Website : https://agent-standup.com/

What would you want to see per sub-agent that it doesn't show yet?

I went through the claude code docs this morning instead of the changelog and found a few things about why long sessions eat your limit that I hadnt seen posted anywhere.

the main one.. your prompt cache lives for an hour on a subscription while youre inside your plan usage. the moment you go past that limit and start drawing on usage credits, the main conversation drops to a five minute ttl. same session, same work, the gap you can leave before a cold reprocess just got 12x shorter. on an api key or a cloud provider its five minutes by default from the start.

everything that isnt your main conversation already gets five minutes regardless. subagents and workflows and compaction and session titles. so a subagent you come back to after ten minutes reprocesses from scratch even on a max plan tbh.

the fix is prob one setting. promptCacheTtl set to 1h, or the CLAUDE_CODE_PROMPT_CACHE_TTL env var. subagentPromptCacheTtl covers the rest. needs v2.1.242 or newer. api key users can set it too.

two other things I didnt know. switching models mid session reads your entire history with zero cache hits. if you run opusplan then every toggle in and out of plan mode counts as a model switch, so bouncing between planning and building rebuilds the cache each time. agent teams also run roughly 7x the tokens of a normal session when teammates sit in plan mode, which the docs state as a plain number.

run /usage and look for the Prompt cache (main) line if you want your own hit rate. needs v2.1.251. on v2.1.260 and up it also names the likely cause of your last miss.

hope this helps.

In 1967 Ted Nelson described stretchtext: text that grows where you want more and shrinks back where you don't. It stayed a quaint idea because writing every level of fidelity by hand is just tediously hard. Text is generative now, so Claude can just write it for us for free.

I've always tried to implement this idea with LLM in various ways. Claude Code Mods finally proivded a platform to share.

cc-stretch is a Claude Code plugin. It cuts Claude's reply by 83% so you read much less, yet still have the option to expand / shrink on demand. The plugin also tells Claude which parts you opened, so it doesn't assume you read the rest.

Install in a Claude Code session:

/plugin install cc-stretch --marketplace pro-vi/cc-stretch
/tui fullscreen

Repo: https://github.com/pro-vi/cc-stretch (MIT)

it plays sounds through your mic into discord and games (no virtual cable), hotkeys work in-game, voice changer, and it can play a sad trombone when "YOU DIED" shows up on screen

https://onion-alien.github.io/onion-board/

free, no ads, no account, source on github: https://github.com/Onion-Alien/onion-board

I have a company Team Premium seat (6.25x) and a personal Max 5x account (previously had personal 20x).

On paper, the gap between 5x and 6.25x is tiny, but in Claude Code the difference feels massive. On my work Team seat, I spam multiple agents all day on Opus 5.5 xHigh and have never once hit the 5h limit, it honestly feels just like my old 20x plan. Meanwhile, on my personal 5x, running just 2–3 subagents at high effort drains my 5h limit in about 2 hours.

And haven't really used my personal account this week much. just some, artifact design work.

Anyone else running both notice this? Do Team seats share an org pool or calculate limits differently, or is personal 5x just way harsher under the hood?

The difference is so striking, my context usage suddenly hits 80%+ on a single prompt (20x plan), tasks are taking at least 2x longer than they did before AND producing far more mistakes.

Several mistakes it already made months back, which I set up rules to prevent from happening again, are now happening again for the first time since I made those rules.

This is the worst state I've ever seen Claude code in since I started using it. Curious if anyone else is experiencing the same to determine how wide spread this is.

I just came across someone with practically no coding experience releasing an open-source password manager called KAPEVault.

Project: https://kapevault.brewedops.cloud

And we're not talking about some basic tutorial project. This is an actual downloadable Windows and Android application being publicly distributed for storing passwords, 2FA codes, API keys, government IDs, and other sensitive information.

I'm a software engineer, and I actively use AI coding tools myself. I think they're incredible. But seriously, of all the things you could build with little to no programming experience, why the fuck would you choose a password manager?

To give credit where it's due, the project is open source, has a documented threat model, automated tests, and a self-conducted security review. But the repository also explicitly acknowledges that it hasn't undergone a third-party security audit.

That's a pretty important distinction when you're asking people to trust your software with practically their entire digital identity.

Using AES-256-GCM and scrypt doesn't automatically make a password manager secure. Neither does having a polished interface, passing automated tests, or getting an AI to review its own output.

Security isn't just about choosing the right encryption algorithms. It's about understanding the entire attack surface, handling secrets properly, identifying edge cases, and knowing what can go wrong even when everything appears to work.

I'm not saying this particular project is insecure. I haven't performed a security audit, and that would be an irresponsible claim.

My concern is the growing confidence with which people are releasing security-critical software they may not fully understand.

There's absolutely nothing wrong with beginners experimenting, learning, and open-sourcing their projects. That's how people improve. But building something for educational purposes and distributing something that real users might entrust with their banking credentials are two completely different levels of responsibility.

AI has made it ridiculously easy to produce working software. Unfortunately, it has also made it ridiculously easy to mistake a working application for a secure one.

You can outsource writing code to an AI. You can't outsource accountability when something goes horribly wrong.

At what point should we start taking this seriously?

I used $200 plan of codex ($20 than $100 than reached to $200):
Before Astra launch: It was good and value for money, doing more work than claude.
After Astra launch: It is useless, continue working for hours and not doing acceptable work. Quality of work decrease and also very less work done on $200 plan.
I was stupid to upgrade my plan, also i got many banked reset and other reset but than i checked my calendar for completed work than i found very less completed work.

I switched to claude than using $20 plan:
used only opus 5.5:
It is amazing because:
same prompt and same work in codex took 1M context & also multiple compact context than provide me very bad results.
claude used only 45% of context and did many things within a 5 hour window and used 10% weekly limits.

If i used Astra than this will consume around 30-40% of $200 plan and also work may be done or not but work can be done with 2-3 extra prompts.
If i used Sol than this will consume around 3-5% of $200 plan and this can do the work but needed multiple prompts.
If i used Luna than this will consume around 1-2% of $200 plan and i have to make multiple prompts & do many work by myself.
I already used same prompts and same work with Astra,Sol,Luna so i am expecting almost correct usages limit.

codex working for hours and give a false feeling of getting more usages or working for more time but when you look for actual work done than this usages limits are worse, even with multiple free resets.

currently, claude with Opus 5.5 used 10% of weekly limits and did 60-70% of work so i am expecting it to complete the work using maximum 30% of weekly limit of $20 plan.

What about yours?

been hitting limits less since i changed a few habits, sharing in case it helps someone:

1. ask it to read files in line ranges, not the whole file. a big read stays in the context for the rest of the session and you pay for it every turn
2. send wide searches / research to a subagent. only the conclusion comes back to the main thread instead of 20 file dumps
3. put these as rules in CLAUDE.md, otherwise it slowly goes back to old habits
4. start a fresh session for a new task instead of dragging a long one along
5. when a session gets long, ask it to summarize the state into a file and continue from there

anything else that worked for you?

Almost got the hat trick!

Been a good boy all week, rationing my tokens carefully, clearing and compacting with care, and ended up 2 hours away from reset time with like 60% weekly and 45% Fable usage....

So f*ck it, Fable on Max, do a full audit of the control panel, look for bugs, vulnerabilities, performance bottlenecks, and suggest improvements... And 30 mins later we're here, "with room to spare", sure :D

Hi, I'm from Korea and my english is not good, so I write this with translator help. sorry if some sentence is weird.I'm making Spearhead alone. It's WW2 eastern front RTS in Unity, and you can press H and ride any tank and drive it yourself. Almost all code is written by Claude Code. I started end of May and now it's about 400k lines C#. Honestly I can't read all of it, so my job is play the build and tell Claude what is wrong.

How I use it: I send many complaints at once with screenshots. Main session find where the problem is and give each one to sub agent. Each agent can edit only its own files so they don't break each other. After that it compile everything and make checklist image on my desktop, then I test.

Today example. The tank riders (desant) jump off pose was strange, so I put 2 old photos of soviet soldiers jumping from T-34 on my desktop and said "look this, they must jump like this or they get hurt". It fixed the seat position on the tank and made the jump pose from the photos. What I learned is memory file with rules is more important than good prompt (like never commit if I don't say, and compile ok is not fixed). Also 1 agent for 1 group of files, before this agents broke each other work a lot. And don't send message to agent while it's working, it get lost often.

voice, music and some store art is AI placeholder now, 3D models are bought assets. steam page in comment.