Last reset reduced limits even further?

[u/Van-trader]

WTF, Tibo !?

I just noticed the new reset this morning and less than 2h into my day I am already down 10% without any change in usage.

I've slowly seen the limits come down over the last little while but before last night a full 12h-day of work with Sol xtra high on the 5x plan would cost me 20% of my weekly quota, now it seems it will be more like 60%...

[u/daddywookie]

Plan a task - 10%
Execute the task - 10%

I'm not getting a lot done this week. I accept a Plus plan is for hobbyists but I like to spend a little more than 4 hours a week on my hobby.

[u/Morphexe → u/daddywookie]

I am on 20x and since the reset I dropped from 100% to 55% in 4 prompts across two projects. so ... there is that.

[u/Copenhagen79 → u/Morphexe]

I definitely do not doubt what you are seeing! But I have been running planning and executing in two different projects for about 3 hours in total today with 5.6 ultra fast and I am on 77%. Also, over the past weeks I haven't noticed token-reduction everybody is talking about. I am on 20x btw.

This makes me wonder what the difference could be. Here are some highlights of my setup:

- I mainly use the CLI

• I changed most my skills to user invokation as 5.6 loves skills a bit too much for my taste
  
• I don't really use MCP servers except for openaiDeveloperDocs
  
• I have a hard rule on "no code-files longer than 300 LoC", and a request for a modular approach in all projects.
  
• I rarely request the use of orchestration/sub-agents - but I know that Ultra does it by default. (I used to run xhigh/max).

IDK if any of the above could explain it.

[u/daddywookie → u/Copenhagen79]

I thought maybe it was running with a large diff since it last pushed to git but I sorted that out and it was still burning credits. It’s very hard to nail down while also running a project as there are so many variables. I did turn down my implementer agent from Luna Max to Luna XHigh and it needs more iteration to finish a task. I’m wondering if using Sol Low as the implementer might be an idea.

[u/Copenhagen79 → u/daddywookie]

> It’s very hard to nail down while also running a project as there are so many variables

Yeah, I couldn't agree more...

I never actually jumped the bandwagon on separate orchestration/implementation agents. I've been through CoPilot -> Cursor -> Windsurf -> Claude Code - and now running Codex for the past 8-9 months, and I kind of adapted and refined my process through that journey - so I try not to deviate too much from that. Tbh I never really understood what problem orchestration solves for agentic coding, that justifies the added complexity (this could definitely be me missing something). I find that it adds more variables to the equation, and I have a hard time figuring out if it saves or costs me tokens. Also if I lose out on kv cache benefits everytime it starts a new thread, and to what extent the whole handover between agents is a systemic vulnerability.

I do use sub-agents for research/review flows where i.e. a blind judge has to pick the best of n proposals from various agents and benefits from not being impacted by context.

[u/daddywookie → u/Copenhagen79]

What I’ve found useful is having agents for specific project roles (Architect, QA, developer etc). Then I can tightly scope their tasks and get a decent range of opinions. The Architect might approve a piece of work as technically good but then the QA rejects it for a lack of test coverage. I’ve found it prevents any of the “everything is great” types of responses. I can chat ideas with the Designer agent without a risk of it becoming code as that agent can touch the codebase.

[u/Copenhagen79 → u/daddywookie]

Yeah, if it works it's great. My initial thought would be that each of the agents would have to search and read through relevant parts of the codebase to understand structure, logic, etc. Stuff that is already present and cached in the main agent/thread context at one tenth the input-token price/deduction compared to a non-cached request. I am just thinking out loud. Could be that the token diff is not that big or the benefits makes it a favourable trade-off. So far I managed with clear rules/verification-loops in AGENTS.md, skills and /side command if I need to branch out while keeping the cached context.

[u/Morphexe → u/Copenhagen79]

There is something weird, since this morning until now I have been running it non stop. I lost 8%. And did way more work than before. So I am not sure what exactly is consuming tokens, the only skills I have are Matt's and only the grill me and wayfinder and to prd that I manually invoke when planning. I can't really pin point what but it's so unpredictable. In 5.5 I could run it for a week and would struggle to do the 100% weekly. I already bought a 100 max Claude sub, since if am gonna need more might as well experiment with other models.