Loading articleโฆ
Loading 4weirdโฆ
Loading 4weirdโฆ
Loading articleโฆ
DocsTerminal
Docs ยท desktop ยท opencode
The web /terminal runs allow-listed local commands only โ no server exec, no eval. Driving OpenCode is the desktop panel's job: it shells to your installed opencode binary with a working-dir guard, timeout, and stop button.
Web side
The web terminal maps every input to a TypeScript handler โ there is no remote shell behind it. Use it for local power-user commands (help, coin quotes, deterministic seeds); it stays fail-open offline.
opencode binary. For Export / Fix / Heal, move to the desktop panel below.Desktop side
The desktop terminal panel (sibling desktop lane) offers a command input, scrolling output, working-dir picker, and stop button. It spawns headless opencode runs โ it never reimplements the CLI bridge.
Working-dir guard
Runs are rooted at your workspace โ never the repo root, never your home directory.
Timeout + stop
Every run carries a per-run timeout and a stop button; stdout/stderr stream back live.
Fail-open when absent
No binary on PATH? The panel shows the install hint and Export still writes the BUGFIX report.
Up next
Once the panel is green, the Heal button loops bugtest โ fix โ retest until clean or the budget is spent. The next page covers that loop.