Since the random resets started happening, I’ve been constantly wondering if I have to use up my entire limit over the weekend because Tibo will reset on Monday , or if I should save up because my reset isn’t scheduled until Friday… I literally have mixed feelings (joy and fear at the same time) – it’s gambler’s syndrome → if I use everything up on intense work over the weekend and get a reset on Monday, I’ll feel happy – and if not, I’ll be sad.
These are just my personal thoughts.
Okay, now we get it in the form of a ticket (we can decide for ourselves when we want) - this is a much better solution.
I’m currently designing tools for drawing technical drawings of fences - connected to synchronized data and a configurator. - But the codex is now an everyday tool for me.
But from the very beginning, I’ve been modifying Codex settings to optimize the usage and performance associated with subagents.
My Codex setup is optimized as an autonomous senior developer and QA engineer:
Sol XHigh is the default model; I select the main model manually.
Subagents are used only for complex tasks: XHigh up to 2, Max up to 3, Ultra up to 8.
Codex selects Luna or Terra based on task complexity, reuses existing agents, and displays their model in the name.
A hard hook enforces agent limits, model selection, and prevents subagents from creating more agents.
Project memory, handoffs, and SessionStart restore context after restarts or compaction.
The Visualizer project has 828.4K usable context tokens.
Skills and plugins are automatically selected for WordPress, coding, UI/UX, testing, and visual QA.
Codex autonomously analyzes, implements, tests, and commits changes, but asks before production operations, paid actions, data deletion, or git push.
Unfortunately, sometimes (quite often) I hit the limit.
Therefore, to be able to work smoothly, I need to know how much Codex power I can utilize. With random restarts, I often felt like I was missing out on a chance (I’m not complaining - I understand how it works), and I have to say that the current distribution of resets (I decide when to use them) is simply healthy.
But I have a simple idea… next to the use icon, add a symbolic number for any unused resets (the number indicates how many resets you have left – if you don’t have any, the number isn’t displayed).
Also, when you launch Codex, when you receive a new reset, display annotations and a short comment explaining the occasion you received the reset, so you can use it at any time.
I think many people will appreciate this.
A new reset is available!
To celebrate this new milestone, we're giving you a little gift. Enjoy!
I suspect many people don’t know they have this option.
If I hadn’t followed this forum, I wouldn’t have found out about Tibo…
¯\_(ツ)_/¯
, or if I should save up because my reset isn’t scheduled until Friday… I literally have mixed feelings (joy and fear at the same time) – it’s gambler’s syndrome → if I use everything up on intense work over the weekend and get a reset on Monday, I’ll feel happy – and if not, I’ll be sad.
