Files
oh-my-opencode/docs/reference/known-issues.md
T
YeonGyu-Kim 8914dab414 docs(known-issues): reference delegate fallback tracking issue
Update the v4.2.0 known issue with the filed follow-up issue and exact PR #3825/#4044 commit details.

Refs #4059.
2026-05-16 01:34:38 +09:00

2.2 KiB

Known Issues

Tracks bugs that are present in the current release but have been intentionally deferred. Each entry should explain the symptom, the history, any workaround, and the planned resolution.

v4.2.0 - Delegate-task early-failure-fallback (BLOCKER-4, deferred from PR #3825)

Symptom

A delegated child session that fails on its very first promptAsync call (for example, the provider rejects the request before any session history is persisted) may not advance to the configured fallback models. The session ends in early failure instead of retrying with the next fallback in the chain.

This affects subagents launched via the delegate-task tool (background or sync) where the first provider call fails immediately and session.messages is still empty.

History

PR #3825 (tw-yshuang/fix/delegated-child-session-early-failure-fallback, commit fac90d69f, author tw-yshuang, merged on 2026-05-15) introduced a shared bootstrap context (src/shared/delegated-child-session-bootstrap.ts) to capture the retry payload before the first prompt dispatch, so empty-history failures could still retry with the fallback chain.

After the merge landed on dev, the PR's own regression test (delegated child-session empty-history fallback retries with captured bootstrap prompt in src/hooks/runtime-fallback/index.test.ts) failed on a clean root bun test --timeout 30000 run (6828 pass / 1 fail). PR #4044 (code-yeongyu/revert/3825-delegated-bootstrap, commit 3c7d1299a, merged on 2026-05-15) reverted the merge to keep dev green (6823 pass / 0 fail / 6 skip across 709 files).

The original failure-mode the PR targets remains in v4.2.0.

Workaround

  • For delegated subagents, prefer providers that succeed reliably on the first call (rarely fail with auth/quota errors at request time).
  • Configure fallback models conservatively in categories[].fallback_models and accept that the very first failure may not auto-retry.
  • The existing runtime-fallback persisted-history retry path still works after the subagent produces any history.

Tracking

Issue #4059 tracks the reland with stabilized regression coverage. The reland is deferred to a follow-up release and should account for current schema-shape changes plus prompt-async-gate semantics.