3 people d747752496 fix(runner): record why an OpenCode turn fails when opencode serve stops (#16863) ...

When `opencode serve` stops during a turn, the OpenCode driver now fails the
active turn itself with a closed-vocabulary cause (server exit code or known
signal, allowlisted socket error code, HTTP status, or closed stream) instead
of leaving runnerd to close it with `error: null`. The proxy flushes stdout
before a fatal exit so the failed turn reaches runnerd, and the server records
OpenCode failed turns as `nativeTurnFailure` (live and persisted-recovery
paths) so the run-failure diagnostic names the cause. Provider text is never
copied. Run status, retries and recovery behaviour do not change.

Co-Authored-By: Paperclip Sentry triage <Paperclip-Paperclip@users.noreply.github.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-19 12:20:24 -07:00

..

scripts

perf(scripts): emit a server module beside the runtime bundle entry (#16765)

2026-10-18 12:16:13 -07:00

src

fix(runner): record why an OpenCode turn fails when opencode serve stops (#16863)

2026-10-19 12:20:24 -07:00

test-baselines

fix: use persisted state for lifecycle continuation and retry budgets (#13888)

2026-09-25 15:28:11 -07:00

CHANGELOG.md

fix: bound workspace Git scans (#11572)

2026-08-17 22:11:30 -05:00

package.json

perf(docker): start the server from a precompiled runtime bundle (#16672)

2026-10-17 16:22:35 -07:00

tsconfig.json

…

vitest.config.ts

fix: make accounting durable and synchronize cost reporting (#14997)

2026-10-06 22:26:48 -07:00