A Self-Hosted Command Center for Your OpenCode Workflows
If you've been using OpenCode to get work done, you've probably run into the same friction: your sessions live in one place, your git workflow in another, and your terminal somewhere else entirely. Jumping between tools gets old fast. OpenCode Manager is a self-hosted web app that pulls those pieces together—sessions, git, terminal, and schedules—into one place you can reach from your desktop or your phone.
What It Does
OpenCode Manager is a web application that acts as a command center for OpenCode. Rather than bouncing between separate tools, you get a single interface covering your sessions, source control, a terminal, and scheduled tasks. The README's screenshots show it working on both mobile and desktop, including things like permission requests, a project switcher, and a live Preview panel during a session.
Under the hood, it's a pnpm workspace with a few distinct pieces: a backend built on Bun and Hono, a frontend using React and Vite, a shared package for schemas and types, and an ocm CLI. It's designed to be self-hosted via Docker, so your setup stays on your own machine or server.
Why It's Cool
It meets you where you already are. The pitch here isn't a new way of working—it's a consolidated view of the way you already work with OpenCode. Sessions, git, terminal, and schedules are the four things you'd otherwise context-switch through, and putting them behind one web app is a genuinely practical call.
Mobile isn't an afterthought. The README leads with mobile screenshots (permission requests, project switching, source control, schedules) before it shows the desktop view. That's a telling choice. Being able to check on a session or approve a permission request from your phone is the kind of thing that sounds minor until you actually need it.
Docker-first install keeps it simple. A single curl command gets you running, and the installer is upfront about what it's doing—it asks before sharing anything from your machine, and re-running it handles updates. That's a small but considerate detail for something self-hosted.
The ocm CLI rounds it out. There's a dedicated CLI alongside the web interface, which suggests the project is thinking about workflows that don't always happen in a browser. It's documented separately, so there's more there than the README spells out.
Admin accounts on first launch. When you start it up, you create an admin account—a sensible default for anything self-hosted that might be reachable beyond localhost.
How to Try It
You'll need Docker with Compose v2. Then it's a one-liner:
curl -fsSL https://opencodemanager.app/install | sh
The installer starts OpenCode Manager on http://localhost:5003 and asks before sharing anything from your machine. Re-run the same command whenever you want to update. On first launch, you'll create an admin account.
If you'd rather not use the installer script, the docs cover Compose and source installs, along with requirements, configuration, and the ocm CLI:
For contributors, the repo is a straightforward pnpm workspace. Clone it and run:
pnpm install
pnpm dev
pnpm lint
pnpm typecheck
pnpm test
The Development Guide covers setup, scripts, database notes, and testing. You can grab the latest release or poke around the source at github.com/chriswritescode-dev/opencode-manager. PRs are welcome, and it's MIT licensed.
Final Thoughts
OpenCode Manager is for people who've bought into OpenCode and want a tidier way to run it—especially if you like the idea of checking in from your phone without setting up a whole remote-access stack. The Docker-first approach and the ask-before-sharing installer make it low-friction to try. If you're happy with your current setup, it won't rewrite your workflow, but if the tool-switching has been wearing on you, this is a reasonable place to consolidate. The project is actively developed with a documented CLI and a clear development path, so it's worth a look if self-hosted tooling is your thing.
Follow @githubprojects for more developer tools and open source projects.