@pvncher What’s missing is a proper file handoff protocol and a way to pass approvals between tasks (e.g., via auto-review).
Instead, it keeps interrupting me and forcing me to manually confirm things in a separate Codex task.
@leodev I think you’re overthinking this, dude. Removing resets wouldn’t magically prevent us from losing access. So why get rid of them? At least with resets, we can get more work done when everything is running normally.
@thsottiaux Maybe this is why some users are skeptical of these on-paper usage increases. Even if the overall quota goes up, the 5-hour limits could still prevent people from actually using it all.
Think about that.
@thsottiaux What if the 5-hour cap is so tight that hitting your weekly limit becomes practically impossible?
At that point, is the weekly allowance a real limit, or just a theoretical number?
@rockatanescu A ticket-based workflow seems like a reasonable way to help agents break down large development goals into smaller, verifiable steps. If decomposition and intermediate validation reduce costly rework, why shouldn’t agents work this way?
@ConnorTalksAI There’s a bit of a problem here. The new version got noticeably slower after release, and now that the speed has been restored, we’re being told it’s an “improvement”? Does that really count?
If TPS is what you’re trying to improve, shouldn’t Codex show the actual TPS for each task? Without that metric, how are we supposed to verify the improvement?
Also, the numbers don’t add up: if the previous result was ~20 TPS, a 50% improvement gets you to ~30 TPS, not 50.
Show us the TPS counter, then we can talk about the improvement.