Codex: clarify subagent tool mapping in bootstrap + README #361
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Minimal Codex-only improvement to the tool-mapping docs so Codex users understand how subagent references should be handled when collab is enabled or disabled.
Changes
.codex/superpowers-bootstrap.mdto mapTask/subagent tool references to Codex collab (spawn_agent+wait), with a sequential fallback if collab is disabled.docs/README.codex.mdto match the same guidance.Why
Codex has an experimental "Multi-agents"/"collab" feature. When enabled, Codex can use
spawn_agent. When disabled (the default), it should fall back to sequential execution. This PR makes the mapping explicit and keeps behaviorconsistent across bootstrap and documentation.
Impact
Testing
Tested in Codex with collab enabled and disabled. Behavior improved (more consistent
spawn_agentusage), but reliable multi-agent behavior still depends on explicit guidance indispatching-parallel-agentsandsubagent- driven-development, which currently requires personal overrides to be fully effective.