docs/reference/known-issues.md
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.
limit do not auto-compactopencode.json without a limit block.0, so auto-compaction never triggers and long sessions can overflow the model window.limit block to each custom provider model in opencode.json, for example:{
"glm-5.1": {
"name": "GLM-5.1",
"limit": { "context": 200000, "output": 16384 }
}
}
BLOCKER-4 is resolved in v4.2.1. Delegated child sessions now retain the first prompt payload before dispatch and consume that bootstrap payload exactly once when runtime fallback must retry an empty-history child session.
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.
PR #3825 (tw-yshuang/fix/delegated-child-session-early-failure-fallback, merged as cd33f3a39 and then fac90d69f on 2026-05-07) 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, revert commit 3c7d1299a, merge-revert commit e2b8e49e2, 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.
categories[].fallback_models and accept that the very first failure may not auto-retry.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.
.opencode/oh-my-openagent.jsonc is silently ignoredoh-my-openagent.jsonc is not applied at runtime.lsp config instead.are you done?. After that nudge, the lead can call team_status and continue.team_status plus team_task_list. For long multi-round runs, prefer explicit team_task_* state over ad-hoc message counting so the lead has a deterministic completion signal.Affects: OpenCode 1.16.x with oh-my-openagent 4.7.x.
Symptom: After installing oh-my-openagent, the OpenCode agent list only shows the built-in build/plan agents. bunx oh-my-openagent doctor can still report System OK, so this looks like a successful install even though the OMO agents are not visible.
Workaround: Stop OpenCode, clear the OpenCode and OMO cache directories, then reinstall:
rm -rf ~/.cache/opencode/ ~/.cache/oh-my-openagent/ ~/.cache/oh-my-opencode/
bunx oh-my-openagent install
Status: Open. Tracked at https://github.com/code-yeongyu/oh-my-openagent/issues/4863.
@plan may stay in Sisyphus instead of switching to Prometheus@plan from Sisyphus can leave the request in Sisyphus instead of handing it to Prometheus./agent, ask for the plan there, then run /start-work after approval.opencode --pure starts, but normal opencode clears the terminal and stalls after service=plugin path=oh-my-openagent@latest loading plugin./tmp/oh-my-opencode.log gets a plugin entry, avoid the npm resolver path by using an absolute file:// plugin path or by pre-populating the OpenCode package cache. If logs point to a malformed or locked opencode.db, back up and remove ~/.local/share/opencode/opencode.db*; OpenCode recreates it on next start, but local session history is lost.lsp_install_decision and waits for an install prompt instead of continuing without LSP.declined install decision for the missing server with lsp_install_decision; future LSP calls collapse to a one-line warning. To share that decision across sessions, set LSP_TOOLS_MCP_INSTALL_DECISIONS to a stable decisions-file path.output hello world can repeat the plan-style status block instead of answering directly.opencode --pure or temporarily disable the plugin for that session./tmp/oh-my-opencode.log repeats promptAsync reservation release skipped for different source while child subagents emit message events."disabled_hooks": ["ralph-loop"] to oh-my-openagent.jsonc. If a loop is already active, run /cancel-ralph before disabling the hook.Affects: OpenCode Desktop on Windows with [email protected].
Symptom: The Desktop plugin list shows oh-my-openagent as loaded, but the UI only exposes the native build and plan modes. The OpenCode log may include Runtime skill source server requires Bun.serve failed to load plugin.
Workaround: Disable the runtime security skills that start the Bun-backed skill source server, then restart OpenCode Desktop:
{
"disabled_skills": [
"security-research",
"security-review"
]
}
Status: Open. Tracked at https://github.com/code-yeongyu/oh-my-openagent/issues/5025.
wait_agent timeouts while a planner or reviewer subagent remains running. Follow-up prompts may not recover the run, and the session can look stuck until the child agent is closed or respawned.BLOCKED, then record the child as inconclusive before closing or respawning it. Do not treat repeated wait timeouts as proof that the child finished.oh-my-openagent@latest.fetch() proxy.url must be a non-empty string before OMO loads, so OMO hooks and doctor cannot repair the install from inside the plugin.HTTP_PROXY and HTTPS_PROXY set, then preinstall the package into OpenCode's Windows config prefix with npm install oh-my-openagent@latest --prefix "%APPDATA%\\opencode". Restart OpenCode and verify with bunx oh-my-openagent doctor --json.tui.json includes oh-my-openagent/tui.NpmInstallFailedError and an unknown git error. Core OMO agents, skills, commands, and MCP tools still work without the TUI plugin.oh-my-openagent/tui from the plugin list in tui.json until the Bun npm install path is fixed.Sisyphus - Orchestrator until the TUI rendering path handles multi-byte character widths reliably.opencode agent list or the TUI still shows OMO agents, but the Desktop agent selector only shows native agents such as Build and Plan.oh-my-openagent doctor passes.Failed to load plugin oh-my-openagent@latest and missing files under ~/.cache/opencode/packages/oh-my-openagent@latest/node_modules.oh-my-openagent@latest package cache, then reinstall the plugin from the same working directory with opencode plugin oh-my-openagent@latest.opencode.json files. OpenCode can read a closer project .opencode/opencode.json instead of the user config you inspected.opencodeThird-party apps now draw from extra usage, not plan limits... for one project while similar projects still work.opencode in custom project rules, system prompt text, or OMO's legacy prompt identifiers.AGENTS.md, prefer oh-my-openagent, OMO, or OpenCode wording instead of the lowercase literal opencode when targeting Anthropic subscription providers.