An early, read-only attention console for OpenCode V2 sessions across projects.
This is a small prototype for a six-person usability experiment, not a replacement for OpenCode, Herdr, ocmux, or opencode-sidebar. It asks whether people who already run several OpenCode sessions will repeatedly use a separate observer to find sessions running or waiting for a permission/question.
- Reads session metadata, active-session status, pending permission requests, and pending forms/questions through OpenCode's V2 API CLI.
- Groups sessions by OpenCode project; search by title, project path, agent, model, status, or attention detail.
- Press Enter to suspend the dashboard and open the exact session in the installed OpenCode TUI, then return to the overview when you exit. Answer permissions/questions there.
- Uses OpenCode's installed CLI for service discovery and authentication.
- Does not read transcript text, read/write the OpenCode database, modify permissions, approve requests, launch new agent turns, install host services, send telemetry, or provision a browser.
- OS: Linux (developed and tested on a Fedora/GNOME workstation). macOS and Windows are untested.
- Python: 3.11 or newer (tested on 3.14.4).
- OpenCode: a V2 installation with its background service running (tested against 2.0.14). V1 servers are rejected on purpose.
- An interactive terminal; the dashboard does not run over a pipe.
The pilot uses OpenCode's installed CLI (opencode on PATH, or set
OCDECK_OPENCODE_BIN) for service discovery and authentication. It stores no
credentials.
git clone https://github.com/omkarchandra/ocdeck-watch.git
cd ocdeck-watch
python -m venv .venv
. .venv/bin/activate
python -m pip install .
ocdeck-pilotTo choose a non-default executable or server:
ocdeck-pilot --opencode /path/to/opencode
ocdeck-pilot --server http://127.0.0.1:4096--once prints only version and aggregate counts, and is useful for diagnosing
installation/service discovery:
ocdeck-pilot --oncepython -m pip uninstall ocdeck-pilotThen delete the checkout directory (including .venv) if you want everything
gone. The pilot writes no config files, services, or state outside its own
process; nothing else to clean up.
| Key | Action |
|---|---|
/ |
Search |
Enter |
Open the selected exact session in OpenCode |
| Click/Enter on project | Filter by project |
r |
Refresh now |
Esc |
Clear search, then clear project filter |
q |
Quit |
This is an experiment build. It has not been tested by outside users, and its installation has not been validated on clean third-party machines. Please report which workflow you use today and whether this view earns repeated use; a star or one-time install is not evidence of product fit.
The proposed two-week study asks six heavy OpenCode users to try their normal
baseline and the pilot on real work. Continue only if at least four voluntarily
use it on four distinct work days during week two and identify a recurring task
it improves. See PILOT_STUDY.md for the full cohort,
install, repeat-use, pivot, and stop criteria.
If several users share the same OpenCode server, its authorization and location behavior remain OpenCode's responsibility. Review the server configuration before connecting to a remote instance.
The code is an isolated pilot beside the author's workstation OC Deck. It does not change or install over the deployed dashboard. Outside-user onboarding has not started; treat everything as experiment-grade.
See PILOT_STUDY.md for the predeclared two-week comparison,
privacy boundaries, continuation/pivot/stop thresholds, and neutral recruitment
copy. No outside users have been recruited yet.
MIT. Not affiliated with or endorsed by the OpenCode maintainers.