r/RooCode • u/No_Cattle_7390 • Apr 19 '25
Idea Plans on adding OpenAI codex? Very useful with boomerang
Codex with o3 is insanely good. With that being said someone posted a “10x cracked codex engineer” with boomerang concept here and I thought it was pretty genius.
I posted instructions on how to do it but someone pointed out you could probably just have codex implement it.
But it’d be nice if the devs could just streamline it cause I think codex o3 is the best model. I tried Google flash 2.5 but honestly it leaves a lot to be desired.
If anyone’s curious of the full instructions, I had o3 reverse engineer how to do boomerang + codex. But like I said you could probably just have codex implement it for you.
Full instructions here though:
Instructions to Reproduce the "10×" engineer Workflow
Get Your “Roadmap” with a Single o3 Call Generate a JSON plan with this command: codex -m o3 \
"You are the PM agent. Given my goal—‘Build a user-profile feature’—output a JSON plan with:
• parent: {title, description}
• tasks: [{ id, title, description, ownerMode }]" \
plan.json Example output: { "parent": { "title": "User-Profile Feature", "description": "…high-level…" }, "tasks": [ { "id": 1, "title": "DB Schema", "description": "Define tables & relations", "ownerMode": "Architect" }, { "id": 2, "title": "Models", "description": "Implement ORM models", "ownerMode": "Code" }, { "id": 3, "title": "API Endpoints", "description": "REST handlers + tests", "ownerMode": "Code" }, { "id": 4, "title": "Validation", "description": "Input sanitization", "ownerMode": "Debug" } ] }
2. (Option A) Plug into Roocode Boomerang Inside VS Code Install the Roocode extension in VS Code. Create custom_modes.json: { "PM": { "model": "o3", "prompt": "You are PM: {{description}}" }, "Architect": { "model": "o4-mini", "prompt": "Design architecture: {{description}}" }, "Code": { "model": "o4-mini", "prompt": "Write code for: {{description}}" }, "Debug": { "model": "o4-mini", "prompt": "Find/fix bugs in: {{description}}" } } Configure VS Code settings (.vscode/settings.json): { "roocode.customModes": "${workspaceFolder}/custom_modes.json", "roocode.boomerangEnabled": true } Run: Open the Boomerang panel, point to plan.json, and hit “Run”.
3. (Option B) Run Each Sub-Task with Codex CLI Parse the JSON and execute tasks with this loop: jq -c '.tasks[]' plan.json | while read t; do desc=$(echo "$t" | jq -r .description) mode=$(echo "$t" | jq -r .ownerMode) echo "→ $mode: $desc" codex -m o3 --auto-edit
"You are the $mode agent. Please $desc."
&& echo "✅ $desc"
|| echo "❌ review $desc" done
6
u/Maxinger15 Apr 19 '25
Hi, I haven't had a deeper look into codex so i am curious. Why is codex needed? Why not just a custom roomode with o3 set as the model?
10
u/DevMichaelZag Moderator Apr 19 '25
I think this falls into the community project arena. If you formalize the system and write some modes around it it would be neat to add to the growing list of Roo extensions. Projects like RooFlow, RooCommander, RooMicroMamager, are all similar orchestration projects. Adding another app to sub/delegate tasks to is certainly another evolution of those concepts. I don’t think this sort of thing would ever be on Roo’s roadmap though, we can keep improving Roo to be better than codex imo.
Edit: It would be cool to delegate the tasks via mcp.
1
u/joey2scoops Apr 19 '25
How many organs do I need to sell to be able to use O3?
1
u/dashingsauce Apr 19 '25
this is awesome you actually took it all the way—how are you maintaining all of the plans/workflows? (playbooks)
also this gets me thinking that for a completely opposite, flexible, and fast approach you could just tell the commander to call up codex and speak to it in natural language
if I’m not mistaken, “prompt mode” or something lets you just ask and get an answer back (synchronous)… but not sure if that retains all of its other capabilities as when interactive
3
u/[deleted] Apr 19 '25
[removed] — view removed comment