// instruments for OpenCode
A tool call has to finish. A dev server does not, and neither does the context window filling up behind you. Cockpit is the instrument panel: things your agent can use, and things that tell you what it is doing. One package per capability, one switch each.
Every bay is its own npm package with a switch in config. They share the daemon, the config file and the keys, so the second costs nothing and moving between them changes nothing you have already set up.
02 Background terminals
A tool call has to finish. A dev server does not — so your agent either blocks on it, or backgrounds it and loses the output. Shell gives it terminals with a real PTY that outlive the turn, wait for a port or a pattern, and hand back the part that matters.
agent Terminals that keep running you A panel that reports its own health
tapes/session.ts · a real model turn, start to finish
Everything long-running hits the same wall: the call either blocks until the process dies, or backgrounds it into the dark. Cockpit changes the shape of the call.
03 The session, at a glance
How full is the context? Where did the tokens go? What has changed? OpenCode answers the first in a corner and the rest not at all. The statusline answers them where you are already looking, and every part of it is a segment you can reshape, recolour or write yourself.
you What the session is costing you
A bay never re-solves process ownership, configuration or interface plumbing. It declares what it needs and gets the rest from the airframe.
OpenCode's interface and server run in separate threads that cannot share memory, and neither survives a restart. cockpitd owns the state: shared by every window, self-upgrading, reaping what crashes leave behind, exiting when idle.
Agent plugins are configured in opencode.json, interface plugins in tui.json. Cockpit reads a single file — global, then project, then plugin entry — and ignores a broken one rather than failing.
A docked panel, a full-screen console, a sidebar section, a keymap namespace. A bay asks for the slot it needs and inherits the chrome, the theme and the keybind conventions.
JSON-RPC over a private socket, schemas shared by client and daemon, versioned at protocol 1.3. A bay adds methods and events without the others knowing, and a mismatch is reported instead of guessed at.
Nothing is listed here that cannot be built with what OpenCode already exposes. One bay at a time, shipped before the next is announced.
A pull request in the terminal. Comment on a line, comment on a file, mark a file read, suggest the change instead of describing it — and none of it reaches the chat until you submit, when it arrives as one message instead of six interruptions.
session.diff carries each file's before and after in full; session.revert undoes one part.
One command that checks your setup and tells you how to fix it.
All bays, each with a switch: { "features": { "shell": true } }. New bays arrive with an update and stay off until you turn them on.
Just this bay. Same daemon, same config file, same interface slots — add the rest later without changing anything you already set up.
~/.config/opencode-cockpit/config.json.OpenCode 1.18+ on macOS and Linux. MIT licensed, every bay its own package.