OpenCompanion

OpenCompanion is an open-source daemon you run on your own machine - the same machine where your subscription coding CLIs already live (Claude Code, Codex, opencode, Hermes). You pair it with an app you use; from then on that app dispatches work and your machine executes it, using your own AI subscription, pinned to a work folder it cannot leave, and recorded to a log only the daemon can write.

The app never holds your keys, your source, or a session on your machine. It composes the work; OpenCompanion runs it locally, inside limits you set and can see.

You can also sit down at it. opencompanion terminal opens your own coding CLI, wired to the app you paired - its tools on the CLI's MCP surface, its instructions in the model's context - in the app's work folder or in a folder of yours you grant. That session is the one thing that may leave the work folder, and only into a folder you named at this machine.

Three steps

Running on the same machine as the app instead? Local mode skips the pairing entirely - an app you install drives the daemon over loopback, with no browser approval, under the same policy and audit log.

When you want it

Reach for OpenCompanion when an app should act on your code or your tools without you handing it credentials or uploading your source:

• You already pay for a coding CLI and want an app to put it to work around the clock.
• You want the work to run on hardware you control - a laptop, a home server, a VPS.
• You need an after-the-fact record of exactly what ran, under what policy, that the app cannot forge.

One daemon serves every compatible app you pair. Each pairing is isolated: its own work folder, its own ceiling, its own audit entries.

Explore