Did you know Codex threads can now manage other Codex threads? You can use this to make a chief of staff merge-bot with a pretty simple prompt.
Tired: I use a thread to implement some change, put up the PR, babysit CI for hours, and the agent often fails over to me to route from there. Many threads would die or distract when the actual PR work was already done approved and I just need to go the last mile through CI.
Wired: Create a new thread in Codex with a tight loop that tells it to babysit all the other threads. Keeps them moving forward. Only real problems are surfaced to me, but most eventually get merged on their own.
Try this prompt, and adjust to your flow:
I need help managing a bunch of threads in my Codex app. Any time I have a thread whose name starts with 🚢, I need to get that PR merged. Most of them are approved already and just need to make it through CI. If there's PR feedback, it needs to be addressed. If there's CI failures, it needs to be addressed. If those failures don't relate to the PR, it's often easiest to just rebase and resubmit rather than trying to figure out what the real problem is. Hell, if a PR is older than a day, it's usually good to rebase anyway just to keep it fresh. If there are manual CI steps or anything else that needs human approval, I need to know that so I can address it myself. YOUR job is to manage all the other threads and surface what I need to know back to me here. I want you to set up an automation to run every 10 minutes to check in on all the 🚢 threads and make sure they're still moving forward. If they're not, prompt them to do so or tell me what the issue is.