You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The opencode harness starts opencode serve and POSTs one message, because the schema door (format: {type: "json_schema"}) exists only on the server API. The argv side lacks one flag.
Upstream state (verified 2026-09-02):
opencode run builds the same Server.Default() app in-process (packages/opencode/src/cli/cmd/run.ts:948) and its prompt payload already accepts format — run.ts never passes it.
Submit a fresh, rebased upstream PR with tests (the old diff was ~134 lines on run.ts).
When a release carries the flag: replace the serve-spawn/POST wrapper in backend/druks/harnesses/opencode.py with the flag on opencode run, keep the deadline and the typed-error parsing, delete the port-parse and abort plumbing.
Acceptance
Upstream PR submitted and linked here.
If merged: the harness invocation is argv-only and the suite passes unchanged.
What
The opencode harness starts
opencode serveand POSTs one message, because the schema door (format: {type: "json_schema"}) exists only on the server API. The argv side lacks one flag.Upstream state (verified 2026-09-02):
opencode runbuilds the sameServer.Default()app in-process (packages/opencode/src/cli/cmd/run.ts:948) and its prompt payload already acceptsformat—run.tsnever passes it.--output-schematorun. Open since 2026-03-13, no maintainer response, diff no longer applies.retryCountbeing dead code.What to do
run.ts).backend/druks/harnesses/opencode.pywith the flag onopencode run, keep the deadline and the typed-error parsing, delete the port-parse and abort plumbing.Acceptance
🤖 Generated with Claude Code