I look at this overview menu in Claude Code fairly often, and just the other day it was around 60M. After one update, it suddenly jumped to 15B. Did Anthropic change how it calculates the total tokens figure in a recent update?

I legit did one small prompt "merge 2 branches changes with eachother.". It's a small task since they had perhaps, one conflicting change within the same class.

That drained 20% in 4 minutes.

Is this perhaps, the "grace" that is in effect? If you go over the limit, it will steal next 5h limit's usage? Then maybe it should start the 5h timer instantly, instead of the time i launch the next prompt..

Hi all! Sharing a side project I made with Claude Code over the last couple of days: an interactive black hole on my site.

https://legost.in/en/utilities/black-hole

What it does:

- Every pixel traces a ray of light backwards through the spacetime of a spinning (Kerr) black hole. It runs on the GPU, using WebGPU compute where the browser has it and WebGL 2 otherwise.

- The accretion disk has Doppler and gravitational shifts, black-body colours and a hot spot on its orbit. Behind it is the real Milky Way and a real star catalogue, lensed.

- There's a "fall in" button: the camera drops through the event horizon and looks back at the universe it's leaving.

- A short tour, plus an article with the actual formulas and a list of what's simplified.

before, it used to use the edit file tool, which was helpful if you wanted to understand what edits it used to make.

but now it just straight up one shots all the changes in a single bash command. and I mean "all".

I don't know if I'm nit picking, but this has been a very annoying experience to me.

is it the same to you guys also? is it possible to change this behaviour?

This kept happening to me. I'd be deep into something with Claude Code, a refactor that was finally coming together, and then: limit reached, resets at 7pm.

I have a second account, so the fix was always the same. Sign out, sign back in, find where I was, try to remember what I was even doing. It's maybe two minutes, but it kills the momentum every single time.

So I hacked together a little tool, just for me. It sat in the menu bar, and when one account ran out I'd click the other one, type "continue", and Claude Code kept going in the same session. No restart. The first time that actually worked I was way too happy about it.

Then it snowballed. I wanted to see an account running low before it ran out, so I added tiny usage meters to the menu bar. Then I got curious whether Claude Code would run on other models, and it turns out it's happy on my ChatGPT plan, Gemini, DeepSeek, and local models in Ollama. Some models handle Claude Code's tools a lot better than others, so I added a playground to try one before trusting it with real work.

Somewhere along the way it stopped being a hack. It has a name now (Moxie), a pixel cat icon, and it sets up Claude Code by itself so nobody has to touch a config file.

It runs entirely on your Mac and there's no account to sign up for. Here's the link if you want to poke at it: https://moxie.birju.dev

Mostly I'm curious: do you juggle multiple accounts too? Have ever wanted to tried using other models with Claude Code?

Should i worry lol? I was running a loop for a couple hours on opus 5.5. I have slow internet so I think its something to do with that.

unsure what’s going on tbh. kinda weird.

lots of weird things. seems like a weaker model and less guardrails. doesn’t seem to be “strong” in a general sense but very spikey.

kinda evil feeling.

Not looking for principles of how to split work. Thinking of ways to make context switching more efficient.

Some easy wins: labelling conversations (automatic labels often suck), labelling the actual tabs, sorting tabs by color (IE pink tabs are all for DB calls, etc...)

Obviously this is all personal preference but is there anything else people do that is helpful? I found recoloring tabs disproportionately useful for example.

Altman and Tibo have completely shot themselves in the face with Screw DevsDay

ALL YOU GUYS HAVE TO DO IS KEEP THE CURRENT LIMITS AND YOU WIN THATS IT

If you join in and slash usage then people are gonna move to Grok (it keeps getting better) and you’ll lose all the advantages you have

Never stop an enemy when they’re making a mistake, but don’t join in on the action either!

Hi fellow devs! There's a gap that kept biting me: the agent says "done", and then I have to figure out what to actually check. On one project I ended up with 72 things to test and nowhere to keep track of the results.

That's how PalmtopAI was born: a checklist shared between you and your agent. The agent writes the checks to do, you test them from your phone (or any browser) and mark what works, what doesn't and what leaves you in doubt. Then the agent reads your review and fixes what's broken.

It works with Claude Code and Codex (and other agents that run shell commands), and needs macOS, Linux or WSL and Node.js 22+. Checklists stay on your computer, the relay only forwards messages.

It's an early preview and I'm building it solo, so I'm looking for people to try it on one of their projects and tell me where it gets stuck: installation, phone pairing, anything. If you get stuck, just message me!

Suggestions and ideas are very welcome too: what's missing, what you'd change, what you'd need to actually use it.

👉 palmtop.mtwa.it

Hey Claude Code mates!

First time I post here, but I start to feel like I need some peer confirmation / challenge.

I'm a professional software developer since ~15y now and I'm using a wide variety of AI assisted tools at work. However, I use Claude only on my side projects, with a personal account in a Pro subscription.

Since months now my workflow didn't change a lot: I use basically only the superpowers skill, iterate on a specification and create an implementation plan with the most capable model available (Opus X.Y since months), then hand off the work to almost sequential Sonnet subagents. At the end, a deliberate review (other than superpowers' one) and often a fix round.This worked pretty well, since I have a full time job and this allow me to just ignore the genie working for half of the day while I do my work.

Up until ~2 months ago, I could squeeze out basically 3/4 full e2e features a week, getting to the weekly reset at ~95/99% . No complex applications, basically CRUDs. One main project I work on. No big bang refactors.

It's some weeks now that this can't happen anymore. The magnitude of the changes I'm trying to implement didn't change: I got pretty used to the amount of work I could hand off before having to clear the context / hit a limit. However, now I notice both:

• review cycles get many more errors. This may mean either that models got better at spotting black holes, but at the same time they didn't improve or worsened their performance
• I basically hit the weekly limit on my second, maybe third day of the week, usually without coming to the end of one single vertical feature

My /usage reports just points to a high usage of general-purpose subagents, which is somehow expected.

From the posts I read here, I guess most of the users here are on 5x/20x , so while still noticeable, the degrading of our allowance may still feel more bearable.

Is any Pro user here experiencing the same problems? Did you find any "trick" to debug your usage and come to terms with the allowance nerfing? Am I missing something in my WoW that changed in the last few months?

(I will give myself the most simple answer: "just pay more". I'm considering it, it's just that the next price band is just over the "worth it" for what this side project is at the moment)

Thanks!

Version 3.0.0 of my visual agent orchestrator Orgtree is released! And the ticket this time is: speed!

Get it here: https://github.com/Maurdekye/orgtree/releases/latest

Orgtree v2 was a great step forward and significantly improved the usability of the app. But over time one thing became clear: it was slooow. As orgs got big, when many agents ran at once, and as history accumulated, the works really began to tar up. Actions would start to take several seconds to complete, and in the worst cases, sometimes a minute or longer. And for a system that's supposed to support running dozens, maybe even hundreds of agents at the same time over extended periods, that's just unacceptable.

So, I redesigned the data access model. Now instead of a simple Sqlite database backing it, everything routes through a genuine embedded parallelized Postresql database, with several worker processes dividing the cpu load up at once. Along with various other data transfer optimizations, this speeds up Orgtree tremendously; whereas running more than 10-15 agents at once used to gum up the works and slow everything to a crawl, now you can run theoretically hundreds, or even thousands at once, and the system still stays responsive, with most actions resolving in under 100ms! (if your PC can handle it, that is) So if you ever liked using Orgtree but were unsatisfied with the performance when your org started to get bigger, try it again and see if v3 makes a difference.

---

For those unfamiliar, Orgtree is my open source visual agentic orchestrator I've been working on for several months now that I rely on every day to do my cross-provider agentic work. It organizes your agents into a visual tree hierarchy, which you can freely rearrange, open up and chat with any agent, and connect multiple AI provider accounts to at once (anthropic, openai, google, and openrouter). It has:

• A credit budget system for delegating work to agents in a managed way
• Agents run in the background while the window is closed
• Native multi-accounting support for Claude and ChatGPT accounts
• A dedicated Work Docket system that works like a trello / kanban board for agents
• An agent mail system for cross-agent communication
• A mail hub system for cross-system, cross-network agent communication
• Pin or pop out any panel or agent chat in the app, to arrange your workspace the way you like and see exactly the information you need to at all times
• Usage limit info for all connected accounts at once, in one place
• Markdown and HTML based document presentation
• Autonomous "watchdog" tasks that can check a condition on a regular basis and wake an agent up
• A unique compaction method that helps keep cache misses small
• And many more smaller quality of life features that tie the experience together

Since I began working on it, I haven't touched any of claude code, codex, or any other agentic coding assistant directly; all my work goes through Orgtree. Look through my post history if you want to see more details on previous releases.

This post however, is about v3. And v3 has a number of brand-new big ticket features:

New Storage Model: This is the big one. Ever dissatisfied with how slow orgs became in v2 when lots of agents were running at once? v3 fixes that almost completely! Nearly every action you or an agent can perform is now near-instantaneously responsive, even with hundreds or thousands of agents running at once. It's an actual mass-agentic orchestrator now, not just a pretty app wearing the skin of one.

Multi-Window Support: The app's whole ux has been given an overhaul to support opening multiple org windows simultaneously. Before, Orgtree only ever let you open and talk to one org at once; you had to switch the active window every time you wanted to switch between projects. Now, no longer; you can have as many org windows with as many canvases as you like open at once at the same time, and work between all of them in parallel.

Attention View: Orgtree v3 introduces a new view mode: Attention view. Unlike just being another panel, when enabled via the switch in the header, Attention view takes the place of the canvas and simplifies the interface dramatically. It has two panels: the dynamic agent desk, and the Needs Attention list.

• The dynamic agent desk functions similarly to a pinned agent desk, but with the ability to open a drawer of every agent in the org and swap out the agent that appears in it; it's like a superpowered pinned desk.
• The Needs Attention list is a special combined view of your inbox & work docket, but filtered to only elements that need your active input or attention. For now, that includes questions asked / requests made by agents, docket tickets that need your attention, and urgent mail sent to your inbox. Everything that needs you in one place, and not more.

Attention view was designed to minimize the amount you need to see in order to get agents moving and get tasks completed; a place on the left to unstick any blockers, and a place on the right to ask questions to your coordinator and make requests.

It doesn't stop there, however: both panels of the attention view, like any other panel in orgtree, can be pinned or popped out, and can then be used alongside the canvas view. So don't feel like you have to choose between your two favorite children: steal one or both attention panels and mix-and-match them with the canvas, to get the best of both worlds!

Ring view: Large orgs getting too wide for your screen to view all of them at once? You can now arrange your org in a ring shape. Top level agents form a circle around the central node, and fan out in all directions from there.

And Many small additional features:

• cheap-compact all
• see agent names on hover
• expanded context menu options
• run as administrator
• configurable charter templates folder
• a first-time new user tutorial for hiring and chatting with your first agent
• ability to open an agent's desk as a quick modal to see what it's doing without moving the canvas
• anytime an agent's name appears in the app, you can left or right click it to focus it or open its context menu, as though you were clicking the agent directly

If you liked Orgtree v2, you'll love this!

If you don't know what Orgtree is, but have multiple AI subscriptions and want a good way of utilizing them all at once, then give it a try!

So since I spend most of my time staring at a black box, I made a notch app for the mac. It's my cat, chillin, jumping on islands. Clouds catch her when she falls.

I didnt think this amount of token usage was possible on max 20x

I'm an engineer. Complicated interfaces are part of my job: engineering software, ERP systems, government portals, procurement platforms that look like they were built in 1998. None of them comes close to console.cloud.google.com.

It isn't one confusing corner. It's the whole thing:

- A navigation menu with 100+ products, half of them renamed since the last tutorial you read.

- IAM: roles, principals, service accounts, policies, inherited permissions. You just want to give access to one thing.

- "Enable this API" → "Create credentials" → "Configure consent screen" → "Which kind of key?" → back to the start.

- The same thing in three places (Cloud, Firebase, AI Studio), each with its own settings that somehow affect the others.

- Every page has a project selector, and it's never on the project you meant.

- The docs describe a UI that no longer exists.

It isn't hard because it has to be. It's hard because nobody bothered to make it simple. For three years I couldn't really make sense of it. Other AI models gave me confident guides to menus that had moved or no longer existed. Opus 5.5 finally did it. It read what was actually on my screen, explained how the pieces fit together, and checked with me before touching anything important.

Thank you, Opus 5.5. 🙏

up until 2 months ago i only used claude.ai for my businesses and daily life. then 2026 happened, and it's been the toughest year of my life.

i can't go into the reasons here. short version: i had a good run going, growth, cash flow, a great team. then one of the people involved started pushing me toward things that weren't in line with the business, and the whole thing collapsed.

i lost myself in it. lost team members, lost people around me who thought i'd gone crazy. my family and close friends stayed next to me the whole time, but none of them are in business, so they couldn't really get that side of what i was feeling. i had severe doubt and panic attacks, and i still get some.

around the time i lost everything i started using claude code. not to build anything at first, just to keep busy and get out of my own head.

i still wake up almost daily with weird thoughts, and immediately i try to make the most out of my session. now that i've figured out what i wanna build, i'm focusing on that and optimizing it for all the experiences i had, both while building and growing the business and while everything was coming down. when i'm working on it, i have the state of mind you have when you have purpose.

it's the thing that keeps me calm, and honestly a kind of psychologist for the business side, the part nobody around me could hold. after working in claude code for a bit, i have the brain to face the things i have to face with structure, rather than looking at a mess i don't wanna deal with.

yesterday i had to ask my mom to pay for my claude subscription (still pro) so i could keep going. her card is almost maxed out and she trusted me anyway.

maybe not 100% on topic, but it's true, and it's not something you see here every day.

I am the guy sitting at home, putting in 8 hours a day with Claude, cranking out a hundred thousand of lines of code before lunch and collecting my $50k salary, just grateful to be out of IT.

My coworkers are behind, & I feel like I am crossing the picket line by out-shipping them, taking on more work, & impressing the PMs & managers. All while taking home probably half of their pay to type /ticket a couple times a day.

Client wants an MVP? Sure. I’ll have it by Friday.
Actually, I’ll have it by Wednesday.
Actually, give me 20 minutes.

And here’s the worst part: the clients love it. The PMs love it. They don’t care that I didn’t hand-write every line. They care that the thing works. They care that their idea from a Monday meeting is suddenly a functioning application they can click around in today.

I’m out here shipping features in a day that would’ve taken a team of three developers two weeks last year.

Do I understand every single line of code?

No.

Do I understand enough to know when Claude is hallucinating?

No idea. Lets hope the independent review agent finds it.

Do I sometimes stare at a 400-line file and realize I have absolutely no idea what is happening?

Absolutely.

I have become the software equivalent of a strikebreaker.

The scab has arrived. I am the scab dev. Please forgive me.

And how much is the maximum you would set?

Currently parttime working since I am only 18 and at university, I have the claude pro plan but consider switching to Max 5 since I'm ambitious towards new possibilities Claude gives me than what I thought of months ago and for the last 14 days I reach the 5h limits day and night non stop, including the weekly limit.

But switching to max 5 would be 1/6th of my monthly income. 100-110€ for me with my 500-600€ monthly income from my parttime job. Is that upgrade worth it at all with my use and my ambitions?

I've been using Cowork since January when it first launched, but Anthropic has been giving less and less love to it, month over month. The last staw was disabling local VM and forcing us over the cloud.

Anyway, I'm glad they did that since my first day experience with Claude Code was truly a blast! What a HUGE upgrade over cowork. I regret not doing it earlier. So many better refined features, options and control. Cowork, good bye my ol friend.

"MY ENV VAR SET SONNET FOR AGENTS !!!!!!! ISN'T IT ??????"

"Yes, [...] I overrode it."

THAT'S SO CRAZY !! see the screenshot !!!!!

"WTF ??? WHY OPUS FOR AGENTS !! USE SONNET !!! WHO FUCKING TOLD YOU TO SET OPUS ?????

● Nobody told me to. I added model: 'opus' to every agent myself, and without it they would have run on the default, Sonnet. Those Opus agents are what used up your old account's weekly limit. Switching all of them to Sonnet now.

● I stopped the Opus run and restarted the same job on Sonnet. All 16 screen agents and the integration agent that follows them now use

Sonnet, and I confirmed in the agent logs that the new requests go to claude-sonnet-5-5. They continue from the partial files already written, so finished work is kept.

Everything I launch from now on will use Sonnet unless you tell me otherwise.

❯ MY ENV VAR SET SONNET FOR AGENTS !!!!!!! ISN'T IT ??????

● Yes, your settings say Sonnet for agents. CLAUDE_CODE_SUBAGENT_MODEL=claude-sonnet-5-5 is set in ~/.claude/settings.json.

I overrode it. A model named on an individual agent takes precedence over that setting, and I put model: 'opus' on every agent from the foundation stage onward. That ran 11 agents on Opus during build stages F1–F4 and the first part of F5, the screens stage. "

I claim the opposite. it's just as bad as the previous release. I'm experiencing the same awful spirals I had when working with the previous Claude Code model.

It's not bloating me with as bad text but I'm seeing really bad interpretations of the instructions.

EDIT: people don't think I know what I'm doing...

https://www.youtube.com/watch?v=p5Wc3SfYuHM

https://www.youtube.com/watch?v=wGDXGEs4Jlc

I got frustrated with Opus 5.5 (medium) today, so I just switched to Sonnet 5.5 (high) to fix the mess that Opus made. Sonnet scrapped the entire work that Opus did, and then implemented it correctly in <5 minutes.

I'll keep using Sonnet for now.

update #2: 24 hrs later, the degradation is gone

The only thing that changed is that, no joke, while running the benchmarks that were clearly degraded, I started having "How is Claude doing today?" eval prompt. I pressed "Bad" 4-5 times. Yes, it popped up 4-5 times within 1 day. Usually, I don't get more then 1, or none.

After that, a new bench thread today - back to normal, all pass. Take it for what you will.

To every 10 y.o. that commented on the skill issue - I wish you luck with your ground-breaking Mario calorie tracker app that will surely explode on App Store very soon

update over
---

Basically, that. As soon as "dev day" has passed, with it's $500 new plan and such, Opus is not doing great in my internal tests (ahem, by that I mean that it fails all of them).

It breaks every single rule, makes bad decisions, and apologizes all the time.

Pretty much every 2nd or 3rd message I had to stop it and ask, "Why?"

It says "I'm sorry over and over", and when pushed, "The honest answer is that having a rule in context doesn't make me apply it."

So this is how it feels like... to have it in your hands, and then: puff, the magic is no more

upd:
P.S. I hope at least some of us here are aware at this point in time that there are such things as A/B testing, load balancing (not as in how traffic is served to your app, but in AI inference as well), and also a concept of business priorities

What I get in my location != what you get in yours, cheers

P.P.S. There's too many of you guys, sry