During core US business hours, I have to actively keep a session going or I risk a massive jump in usage while the entire thread rebuilds. During weekend or off-hours, I never see the crazy jumps in usage - even if I let threads sit stale.

It’s further frustrating that I have committed to certain project deadlines knowing that I’d be able to complete it in X amount of time with agent tooling. That agentic tooling is no longer viable and I’m scrambling to readjust expectations and how much I can commit to.

As of now, I’m consistently hitting my 5 hour limit in less than 1 hour during N/A business hours. I’m getting to the point where I basically can’t use CC for work unless I work very early or late in the day.

Here’s what I’ve done to mostly fix my usage issues:

* Turn on max thinking on every session. It save tokens overall because I’m not correcting it of having it waste energy on dead paths.

* keep active sessions active. It seems like caches are expiring after ~5 minutes (especially during peak usage). When the caches expire it sees like all tokens need to be rebuilt this gets especially bad as token usage goes up.

* compact after 200k tokens as soon as I reasonably can. I have no data but my usage absolutely sky rockets as I get into longer sessions. This is the most frustrating thing because Anthropic forced the 1M model on everyone.

Mythos seems much, much more creative and self directed, but I’m not yet convinced the core capabilities are significantly higher than what’s possible today.

The full price of finding the vulnerabilities was also something like $20k. That’s a price point that brings a skilled professional in to accomplish the same task.

The magnitude is so small that anonymity is essential broken.

There are ~50k psychiatrists in the US. Roughly, 1 in 10k people in the US is named Scott. Mathematically, that means knowing "Scott is a psychiatrist" brings you down to ~5 people. Even if we assume there's some outlier clustering of people named Scott who are psychiatrists, we're still talking about some small number.

Surely adding in the middle name essentially makes him uniquely identifiable without an other corroborating information.

It's not necessarily back to where it was, but it's not desk-flipping bad.

I’m honestly not convinced this is changing the landscape significantly. It’s simple a bit better at self directing.

Today, Opus went in circles trying to get a toggle button to work.

Don’t get me wrong, this model is better - but I’m not convinced it’s going to be this massive step function everyone is claiming.

* ME: "Have sonnet background agent do X"

* Opus: "Agent failed, I'll do it myself"

* Me: "No, have a background agent do it"

* Opus: Proceeds to do it in the foreground

* Flips keyboard

This has completely broken my workflows. I'm stuck waiting for Opus to monitor a basic task and destroy my context.

1. Me not wanting that for context management reasons

2. It burning tokens on an expensive model.

Literally a conversation that I just had:

* ME: "Have sonnet background agent do X"

* Opus: "Agent failed, I'll do it myself"

* Me: "No, have a background agent do it"

* Opus: Proceeds to do it in the foreground

* Flips keyboard

This has completely broken my workflows. I'm stuck waiting for Opus to monitor a basic task and destroy my context.

I keep coming back to it because I can run it as a manager for the smaller tasks.

Even after deleting everything from the first feature and going back to the checkpoint just before initial development, I can no longer get it to accomplish anything meaningful without my direct guidance.

I've basically stopped using it because I have to be so hands on now.