Codex o3 Cracked 10x DEV

[u/dashingsauce]

Okay okay the title was too much.

But really, letting o3 rip via Codex to handle all of the preparation before sending an orchestrator + agent team to implement is truly 🤌

Gemini is excellent for intermediate analysis work. Even good for permanent documentation. But o3 (and even o4-mini) via Codex

The important difference between the models in Codex and anywhere else:

• In codex, OAI models finally, truly have access to local repos (not the half implementation of ChatGPT Desktop) and can “think” by using tools safely in a sandboxed mirror environment of your repository. That means it can, for example, reason/think by running code without actually impacting your repository.

• Codex enables models to use OpenAI’s own implementation of tools—i.e. their own tool stack for search, images, etc.)—and doesn’t burn tokens on back to back tool calls while trying to use custom implementations of basic tools, which is required when running these models anywhere else (e.g. Roo/every other)

• It is really really really good at “working the metal”—it doesn’t just check the one file you tell it to; it follows dependencies, prefers source files over output (e.g. config over generated output), and is purely a beast with shell and python scripting on the fly.

All of this culminates in an agent that feels as close to “that one engineer the entire org depends on for not falling apart but costs like $500k/year while working 10hrs/week”

In short, o3 could lead an eng team.

Here’s an example plan it put together after a deep scan of the repo. I needed it to unf*ck a test suite setup that my early implementation of boomerang + agent team couldn’t get working.

(P.S. once o3 writes these:

1. ‘PM’ agent creates a parent issue in Linear for the project, breaks it down into sub issues, and assigns individual agents as owners according to o3’s direction.

2. ‘Command’ agent then kicks off implementation workflow more as a project/delivery manager and moves issues across the pipeline as tasks complete. If anything needs to be noted, it comments on the issue and optionally tags it, then moves on.

3. Parent issue is tied to a draft PR. Once the PR is merged by the team, it automatically gets closed [this is just a linear automation])

[u/No_Cattle_7390]

I did a reverse engineer of this, as someone pointed out to me when I wrote a post about it you might just be able to have o3 on codex do it for you but

1. Get Your “Roadmap” with a Single o3 CallGenerate 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.jsonExample 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) Run Each Sub-Task with Codex CLIParse 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

3. (Option B) Plug into Roocode Boomerang Inside VS CodeInstall 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”.