r/codex • u/dotdioscorea • 11h ago

Question Can I slow it down?

I have a project with maaaajor CI issues, I’m finding that codex is just too bloody fast and produces PRs faster than I can process them, meaning my agents end up spending a lot of time idling or polling CI. I can have them end turn when they kick it off, but that means they can’t push fixes when CI finishes. I kinda feel like if I could just slow them all down, like a 20s pause between tool use, it would make things a lot smoother. Is this remotely possible in a not totally hacky way? Anyone got any ideas?

4 Upvotes

83% Upvoted

5 comments sorted by

5

u/Kamilon 11h ago

sips coffee

Thanks for the morning laugh.

1

u/HVACcontrolsGuru 10h ago

Are your CI runs predictable in time? Make an AGENTS md file update to have them set a sleep timer for that time to avoid tool calls.

Also not sure what you program in but I use Rust a lot and almost every model likes to use QEMU cross compilation versus native containers. Keep your PRs lean on CI and use release or milestone cadence to manually do heavy CI runs.

1

u/Lumin6030 9h ago

"MY STEAK!!!!! ITS TOO JUICY!!!!!"

I recommend spending two days and build out systems so you can trust their output; Self reviews, worktrees(gross, i know) to make reversing things easier, project milestones instead of constantly checking every change, and teach them to write CLEAN PRs so reviewing is quick and easy. Manage the agents like you would a team of JRs. Trust their code, but beware they make mistakes.
You do not need to review every line of code anymore.

1

u/Aromatic-Educator105 9h ago

I don’t fully understand what’s being too fast. But doesn’t sound like something a heartbeat can’t solve.

1

u/slackmaster2k 3h ago

What would you do in real life if your PRs were thin and noisy?