Why does your terminal scrollback vanish when OpenCode restarts?
I kept losing terminal scrollback whenever the OpenCode server restarted mid-task, and renamed terminals reverted to old names. OpenCode now makes desktop terminals belong to the session, so they survive restarts with scrollback intact and stay synced with the TUI and other windows.
What it is
Persistent desktop terminals tie terminal state to the OpenCode session rather than the window process. Scrollback, names, and view state are preserved across server restarts and synchronized everywhere.
Applied case
In my multi-window setup, a server restart mid-run used to wipe all scrollback and reset terminal names. With this release, terminals belong to the session, keep their scrollback through restarts, and stay synchronized with the TUI and other windows. Renamed terminals also keep their names across restarts, so I never re-label anything after a bounce.
- Terminals survive OpenCode restarts with scrollback and names intact (#60346)
When to use it
Use when you run long agent sessions across multiple windows and restart the server often.
Skip when you use a single throwaway terminal; this also does not recover output from a terminal closed before the restart.
Read more
Recommended for you
- WorkflowOpencode
How do you keep coding agents on task without babysitting every step?
Agent sessions drift from the objective, forcing you to watch every turn; opencode's /goal lets a session run until a reviewer confirms the goal is met.
- WorkflowHerdr
How do you supervise coding agents without watching every window?
I run Claude and opencode side by side in one terminal. Three herdr habits replaced window-polling with state-waiting: persistent sessions, the agent loop, a setup script.
- WorkflowSuperpowersClaude Code
Why does your multi-agent workflow keep colliding?
Two agents in two threads share files but not context. Both decide on stale state. Fix: one fresh agent per task, with isolated context.
- WorkflowSuperpowersClaude Code
What makes agent output trustworthy when the model is not the problem?
The reliability problem is not the model. It is the missing disciplines around it. Brainstorm, plan, test, verify, review: each gate before the next step.
Enjoyed this article?
Subscribe for new articles. No spam. Unsubscribe anytime.