codex automations are GA and your manual repo babysitting is now a CHOICE

set the model, set the reasoning level, pick worktree or existing branch - thats not a wrapper, thats granular control over how the agent thinks and where it writes code
reusable templates mean you build the workflow once then let it run daily repo briefings, issue triage, PR comment follow-up while youre shipping the thing that actually matters
the part nobody is talking about - you can now theme the entire codex app and import or share themes with other builders, which sounds small until you remember youre staring at this thing 9 hours a day
not a chatbot skin. not a prompt playground. an actual operator environment you can tune at the reasoning layer AND the visual layer.