mirror of
https://github.com/obra/superpowers.git
synced 2026-07-23 10:44:01 +08:00
cdcadda4be
Responds to maintainer review of this branch: the dispatch-hint lines were hardcoded Codex strings inside shared skill tooling that every harness runs. The per-role hint lines now live in a platform-owned data file, skills/using-superpowers/references/codex-dispatch.hints, and the task-brief/review-package scripts only relay the current role's line. The relay is suppressed when CLAUDECODE is set (Claude Code's dispatch templates already carry model selection) and on any harness with no hints file; unknown harnesses fail toward printing, because a silent no-op in the environment that needs the hint is the failure mode this mechanism exists to prevent. Printing at the moment of dispatch is load-bearing: skill text loaded at session start does not survive context compaction, but script output reprints every round. codex-tools.md's SDD dispatch section shrinks to the behavioral rules (fork_turns: "none" always; copy the printed hint verbatim; reviewer tier never exceeds implementer tier; no effort bumps; the <=0.144 inheritance fallback) and points at the hints file for values. Tests cover the relay path, the per-role efforts, and the new CLAUDECODE suppression case. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
65 lines
2.9 KiB
Markdown
65 lines
2.9 KiB
Markdown
## Subagent dispatch requires multi-agent support
|
|
|
|
Add to your Codex config (`~/.codex/config.toml`):
|
|
|
|
```toml
|
|
[features]
|
|
multi_agent = true
|
|
```
|
|
|
|
This enables `spawn_agent`, `wait_agent`, and `close_agent` for skills like `dispatching-parallel-agents` and `subagent-driven-development`. When using subagent-driven-development, close reviewer subagents when their review returns. Keep each implementer subagent open until its task's review passes — the fix loop resumes the implementer — then close it. If your harness cannot send another message to a spawned agent, dispatch each fix round as a fresh implementer carrying the brief, the report file, and the findings.
|
|
|
|
## SDD dispatch on Codex
|
|
|
|
Every SDD `spawn_agent` call sets `fork_turns: "none"` — the default
|
|
`"all"` forks your whole transcript into the child and refuses model
|
|
and effort overrides.
|
|
|
|
If your `spawn_agent` schema has `model` and `reasoning_effort`
|
|
parameters (Codex 0.145+), set both on every dispatch: task-brief and
|
|
review-package print a `dispatch:` hint line with the exact values —
|
|
copy it onto the call verbatim, every time, even late in a long
|
|
session. Those hints are the Model Selection mapping on Codex:
|
|
reviewer tier never exceeds implementer tier, no fix round gets an
|
|
effort bump, and rounds 4-5's "more capable model" means a fresh
|
|
implementer at the same tier — needing more is a BLOCKED escalation
|
|
to your human partner. Inherited frontier-tier subagents are a
|
|
measured cause of runs spinning out for hours. (Values live in
|
|
`codex-dispatch.hints` beside this file; they track the spawn_agent
|
|
model allowlist.)
|
|
|
|
Without those parameters (Codex 0.144 and earlier), children inherit
|
|
your model and effort with no override — role files in
|
|
`~/.codex/agents/` do not attach to spawns either. Tell your human
|
|
partner before starting a plan of more than a few tasks, and offer a
|
|
lower-effort session instead.
|
|
|
|
## Environment Detection
|
|
|
|
Skills that create worktrees or finish branches should detect their
|
|
environment with read-only git commands before proceeding:
|
|
|
|
```bash
|
|
GIT_DIR=$(cd "$(git rev-parse --git-dir)" 2>/dev/null && pwd -P)
|
|
GIT_COMMON=$(cd "$(git rev-parse --git-common-dir)" 2>/dev/null && pwd -P)
|
|
BRANCH=$(git branch --show-current)
|
|
```
|
|
|
|
- `GIT_DIR != GIT_COMMON` → already in a linked worktree (skip creation)
|
|
- `BRANCH` empty → detached HEAD (cannot branch/push/PR from sandbox)
|
|
|
|
See `using-git-worktrees` Step 0 and `finishing-a-development-branch`
|
|
Step 1 for how each skill uses these signals.
|
|
|
|
## Codex App Finishing
|
|
|
|
When the sandbox blocks branch/push operations (detached HEAD in an
|
|
externally managed worktree), the agent commits all work and informs
|
|
the user to use the App's native controls:
|
|
|
|
- **"Create branch"** — names the branch, then commit/push/PR via App UI
|
|
- **"Hand off to local"** — transfers work to the user's local checkout
|
|
|
|
The agent can still run tests, stage files, and output suggested branch
|
|
names, commit messages, and PR descriptions for the user to copy.
|