Make your computer a home for your AI partner. Avibe is the local-first Agent OS: Vibey, its built-in AI partner, works out of the box, and Claude Code, Codex & OpenCode run unchanged beside it — reach them from your browser, phone, or any chat app.
OpenCode Active-Turn Timeout Becomes Opt-In
Background
docs/plans/opencode-active-turn-timeout.md (#1197, fixing #1190) shipped a
90-minute wall-clock cap on accepted OpenCode turns. The incident's root cause
was OpenCode's ai-sdk runtime retrying exhausted-provider errors forever
without surfacing a terminal message, which left Avibe's error-driven
settlement nothing to observe.
Upstream has since fixed that class directly: OpenCode >= 1.18.x disables
ai-sdk internal retries (maxRetries: 0), runs its own bounded retry policy
(RETRY_MAX_RETRIES = 5, capped backoff), and writes the exhausted error onto
the assistant message, which Avibe's existing error path settles as a failed
terminal result. Verified against the locally installed 1.18.18 binary and the
dev-branch source (packages/opencode/src/session/retry.ts; fix commits
#40707, #41939).
The wall-clock cap therefore kills legitimate long turns while no longer guarding a live failure mode. It also disagrees with the other backends, which settle on surfaced errors rather than turn duration.
Goal
- Default-disable the cap:
agents.opencode.active_turn_timeout_secondsdefaults to0, meaning no wall-clock bound. - Keep the mechanism as an explicit operator opt-in; a positive value behaves exactly as before.
- Neutralize the legacy default echo at load: configs saved while the cap
shipped carry
5400because a settings save materializes the whole section, so exactly that value migrates to0. Any other persisted value is an explicit choice and survives. - Non-positive, missing, or non-finite config values read as disabled; they must not silently fall back to a cap.
Solution
config/v2_config.py:DEFAULT_OPENCODE_ACTIVE_TURN_TIMEOUT_SECONDS = 0,LEGACY_DEFAULT_OPENCODE_ACTIVE_TURN_TIMEOUT_SECONDS = 90 * 60, and_migrate_opencode_active_turn_timeout_on_loadwired into the load migration chain. The migration is a one-time neutralization guarded by thelegacy_turn_timeout_neutralizedprovenance marker: a legacy payload (no marker) with the echo value loads as disabled, while any config saved under the opt-in semantics carries the marker, so a deliberate 5400-second choice saved afterwards survives every later load.modules/agents/opencode/poll_loop.py: disabled timeout yields an infinite deadline;wait_forreceivesNonefor the infinite budget. Error-driven settlement, user stop, and shutdown cancellation are unchanged.- Poll-transport settlement: a persistent runtime outage (daemon unreachable,
non-200 responses) can no longer retry forever once the wall-clock deadline
is optional. Both poll loops settle the turn as a failed backend failure
after
_POLL_FAILURE_SETTLE_LIMIT(10) consecutive polling errors and best-effort abort the native session. The bound is on consecutive failures, never on total duration: a successful poll resets the counter, so intermittent blips never trip it. - UI: the Settings → Messaging field accepts
0(minutes) and documents the disabled semantics; hint copy updated in en/zh.
Pre-1.18 runtimes
Installations that upgrade Avibe while keeping an OpenCode binary older than
the bounded-retry change re-expose themselves to the unbounded provider-retry
hang #1190 documented. Avibe cannot reliably version-gate this: OpenCode is a
user-supplied cli_path, and the bounded-retry policy landed mid-1.18.x line
(build-date dependent), so a < 1.18 check would be wrong in both directions.
The cap remains fully functional as an explicit opt-in for those operators;
the product default follows the supported runtime behavior.
Scope
HFR-432 keeps its scenario ID and semantics for the opted-in lifecycle. The default-disabled deadline has its own unit coverage beside the poll loop (disabled-semantics seeding test plus a no-deadline prompt-poll test).