Repository navigation
Open
Labels
pending_reproRepro attempted; still pending conclusive reproductionRepro attempted; still pending conclusive reproduction
Description
Operating system
macOS (Darwin 25.6.0)
Orca version
1.4.218
Details
While coordinating a supervised orchestration run (coordinator = Claude Code; implementers = codex and antigravity; reviewers = opencode), several problems repeated across ~30 dispatches in one Run.
1. Prompt injection does not land in opencode (and once in antigravity)
orchestration worker-start --agent opencodereturnsok: truewithprompt.stages: ["input_accepted", "turn_started"], but the opencode TUI shows an empty input box and never starts a turn. This happened on every opencode dispatch.- It also happened once with
--agent antigravity: the agent only saw the "You have 1 orchestration message" notice, not the task prompt. codexdispatches were not affected.- Workaround:
orchestration dispatch-show --task <id> --preamble, write the preamble to a file, thenterminal send --text "read <file> and follow it" --enter.
2. Workers cannot get their dispatch capability, so every lifecycle message is rejected
- When the prompt is delivered through the workaround above, the preamble returned by
dispatch-show --preamblehas no--dispatch-capabilityvalue. - Result: every
worker_done,heartbeat,askandescalationfrom those workers is rejected withdispatch_capability_invalid("The Dispatch capability is missing" / "is invalid" / "is revoked"). - The coordinator has to read the verdict out of the rejected message, then settle by hand (
worker-stop→ oftenstop_unknown→worker-abandon→task-update --status completed). - Expected: either injection works, or there is a supported way for the coordinator to re-deliver a full preamble including the capability.
3. A reviewer worker became the Run's coordinator
- Mid-run,
run-showreportedcoordinator_handle= the opencode reviewer's terminal (consumer_generationwent 1 → 2). From then on the real coordinator gotconsumer_fencedonworker-start,check --ackandtask-update. - This happened after the reviewer had repeated
worker_donerejections (problem 2) and was trying to report. - Recovered with
orchestration run-use --id <run>from the original coordinator terminal. - Expected: a dispatched worker terminal must not be able to (re)bind itself as the coordinator of the Run it works in.
4. Workers read Orca's internal state to look for the capability
- After the rejections, two different workers (antigravity once, opencode once) searched
~/Library/Application Support/orca/(terminal history) and queriedorchestration.dbwithsqlite3 SELECTto look for the capability. One reported seeingcapability_hashthere. - Reads only, as far as we could see, but the agents treat local Orca state as reachable when the documented path fails.
- Fixing problems 1 and 2 would likely remove the incentive. Consider whether the DB and terminal history should be readable from worker terminals at all.
5. Smaller items
worker-stopon an idle-but-live opencode/codex terminal frequently returnsstop_unknown, and a retry fails withdispatch_inactive. Onlyworker-abandonsettles it, and the terminal stays open.worker-releasesometimes returns"state": "retained"for a dispatch that had earlier been retained and was then settled.- Abandoned reviewers keep sending heartbeats and
statusmessages with a revoked capability. These land in the coordinator inbox and wakecheck --wait.
Repro outline
orchestration run-createworker-start --spec "<task>" --worktree path:<repo> --agent opencode --json- Observe the opencode TUI: input empty, no turn.
dispatch-show --task <id> --preamble→ no capability in the text; deliver it viaterminal send.- Worker finishes → its
worker_doneis rejected withdispatch_capability_invalid.
Metadata
Metadata
Assignees
Labels
pending_reproRepro attempted; still pending conclusive reproductionRepro attempted; still pending conclusive reproduction
Activity
leovibecoder commentedon Oct 7, 2026
Same missing-capability symptom reproduced on Orca 1.4.217, WSL2 (Ubuntu) with OpenCode v2.0.24,
--agent opencode2, over 4 consecutive supervised workers (2026-10-06/07).Every run
worker-start --spec ... --worktree id:<repo-id>::\\wsl.localhost\Ubuntu\... --agent opencode2 --jsonreturnsstate: ready,stage: input_accepted,turnStart: unsupported,prompt.provider: unsupported.dispatch-show --task <id> --preamble+terminal send --text <bracketed-paste preamble> --entergets it delivered.dispatch-show --preambleoutput contains no--dispatch-capability. The preamble'ssend --from <handle> --type worker_done ... --task-id ... --dispatch-id ...is rejected withThe Dispatch capability is missing. Pass --dispatch-capability <token> from your dispatch preamble.Heartbeats and--type escalationare rejected the same way.Rejected worker_done: ...with the original body. We now use that, plus waiting for the worker's PR, as the completion signal.task-update --status completedis refused (task_not_startable), andworker-stoplands instop_unknown(cannot stop from stop_unknown). Onlyworker-abandon+terminal closecloses the worker.Possibly related
A worktree created with plain
git worktree add(notorca worktree create) has noprojectId. The worker's terminal is reportedorphaned: true(paneRuntimeId: -1) and never appears on the Agent Dashboard. Withorca worktree create, it is attached and visible. Prompt delivery and the missing capability are the same in both cases.Happy to run a debug build or capture more receipts if useful.
nwparker commentedon Oct 24, 2026
Thanks for the report! The OpenCode half should be fixed in newer builds. Please retest on 1.4.239+ and tell us whether OpenCode and antigravity workers still miss the dispatch prompt and capabilities. Include Orca version, OS, and versions of the agents. If it still fails, the coordinator-binding behavior is better tracked separately. Please redact anything private before sharing; screenshots or log excerpts are fine.
nwparker commentedon Nov 6, 2026
Thanks for the report. We couldn't reproduce this on the current build, and several related fixes have landed since. Could you retest on the latest Orca and, if it still happens, reply with: OS + Orca version +
agy --version, minimal steps to reproduce, and any relevant logs/screenshots? We'll close this as insufficient information in 14 days if we don't hear back.