Goal
Make opencode work end-to-end as a builder harness in this fork, so it can host Grok. This is the
prerequisite for #2 (per-spawn --model): a harness without a working launch and a measured
render-gate profile produces a builder you can spawn but can never message.
Fork-only. We are not sending this upstream.
Two defects, both must be fixed
1. Launch is broken — the prompt is passed as a project path
A builder with shell.builder: "opencode" launches, immediately exits 0, and shows
"Agent exited at your request. Press Enter to relaunch, or close this terminal." It never runs.
Cause: packages/codev/src/agent-farm/commands/spawn-worktree.ts:875 passes the initial prompt as a
positional argument — the claude/codex convention:
opencode "$(cat '/…/.builders/task-XXXX/.builder-prompt.txt')"
OPENCODE_HARNESS.buildScriptRoleInjection returns an empty fragment (opencode injects its role
file-based, via the opencode.json it writes: { "instructions": [".builder-role.md"] }), so the
prompt falls through to codev's generic positional form.
But opencode's positional slot is a project path, not a prompt:
opencode [project] start opencode tui [default]
opencode run [message..] run opencode with a message
Positionals:
project path to start opencode in [string]
Options:
--prompt
Fix: emit --prompt (or opencode run) for this harness instead of the positional form. Verify
against the installed opencode version rather than assuming the flag name — check opencode --help
first and record the version you tested.
2. No render-gate profile
packages/codev/src/agent-farm/servers/gate-profiles.ts resolves opencode to null, so every
afx send to an opencode builder is held forever with reason no-profile.
A profile needs, per the existing CLAUDE_PROFILE / CODEX_PROFILE / agy shapes:
markerPattern — the composer's prompt glyph at the input row startregionEndPatterns — the line(s) that bound the composer region below
These must be MEASURED from a real captured screen, never guessed. The file's own warning:
REGION_END_PATTERNS is "FAIL-SAFE but DRIFT-FRAGILE"; a too-loose pattern is a false-clean that
injects a message while the agent is mid-typing and corrupts its input. Capture real frames from a
live opencode TUI (idle-empty, mid-typing, mid-stream, and with a dialog open) and derive the
patterns from those captures. Include the captures in the PR.
Acceptance
afx spawn --task "sit idle" with shell.builder: "opencode" produces a builder that actually runs.afx send <that-builder> "hello" returns delivered, not held/no-profile.afx send while the opencode builder is mid-turn HOLDS rather than injecting (no false-clean).- Spawning a harness that has no gate profile fails loudly at spawn time with a clear message,
instead of producing a silently unmessageable builder. - Captured frames used to derive the profile are committed.
Notes
- Do not "fix" this by loosening the shared
REGION_END_PATTERNS. Give opencode its own patterns,
the way agy got its own for a different marker glyph and color rule. resolveHarness's claude fallback must not be reused here — gate-profiles deliberately keeps a
strict app-identity table so an unknown app never inherits claude's (wrong) profile.
Goal
Make
opencodework end-to-end as a builder harness in this fork, so it can host Grok. This is theprerequisite for #2 (per-spawn
--model): a harness without a working launch and a measuredrender-gate profile produces a builder you can spawn but can never message.
Fork-only. We are not sending this upstream.
Two defects, both must be fixed
1. Launch is broken — the prompt is passed as a project path
A builder with
shell.builder: "opencode"launches, immediately exits 0, and shows"Agent exited at your request. Press Enter to relaunch, or close this terminal." It never runs.
Cause:
packages/codev/src/agent-farm/commands/spawn-worktree.ts:875passes the initial prompt as apositional argument — the claude/codex convention:
opencode "$(cat '/…/.builders/task-XXXX/.builder-prompt.txt')"OPENCODE_HARNESS.buildScriptRoleInjectionreturns an empty fragment (opencode injects its rolefile-based, via the
opencode.jsonit writes:{ "instructions": [".builder-role.md"] }), so theprompt falls through to codev's generic positional form.
But opencode's positional slot is a project path, not a prompt:
Fix: emit
--prompt(oropencode run) for this harness instead of the positional form. Verifyagainst the installed opencode version rather than assuming the flag name — check
opencode --helpfirst and record the version you tested.
2. No render-gate profile
packages/codev/src/agent-farm/servers/gate-profiles.tsresolvesopencodetonull, so everyafx sendto an opencode builder is held forever with reasonno-profile.A profile needs, per the existing
CLAUDE_PROFILE/CODEX_PROFILE/ agy shapes:markerPattern— the composer's prompt glyph at the input row startregionEndPatterns— the line(s) that bound the composer region belowThese must be MEASURED from a real captured screen, never guessed. The file's own warning:
REGION_END_PATTERNSis "FAIL-SAFE but DRIFT-FRAGILE"; a too-loose pattern is a false-clean thatinjects a message while the agent is mid-typing and corrupts its input. Capture real frames from a
live opencode TUI (idle-empty, mid-typing, mid-stream, and with a dialog open) and derive the
patterns from those captures. Include the captures in the PR.
Acceptance
afx spawn --task "sit idle"withshell.builder: "opencode"produces a builder that actually runs.afx send <that-builder> "hello"returnsdelivered, notheld/no-profile.afx sendwhile the opencode builder is mid-turn HOLDS rather than injecting (no false-clean).instead of producing a silently unmessageable builder.
Notes
REGION_END_PATTERNS. Give opencode its own patterns,the way agy got its own for a different marker glyph and color rule.
resolveHarness's claude fallback must not be reused here — gate-profiles deliberately keeps astrict app-identity table so an unknown app never inherits claude's (wrong) profile.