Why one service instead of separate tools?
Running coding agents in their own git worktrees is a known idea. Cerberus puts it next to the rest: it is a background service you reach from any browser, your phone included; it hosts the models and one OpenAI-compatible gateway, so agents can run on a model your own machine serves; and it measures what each request costs in tokens, money and energy.
Do I need an agent framework on top?
For many jobs, no. A flow gives you a planner, a fan-out to several models or agents, branches, a judge gate and an approval, saved as a file the service runs by hand or on a schedule. It is a fixed list of steps that jump forward, not a general graph, and its templates run no code. When a job needs your own code between the steps, call the /v1 gateway from your program or framework.
Can I use my LLM subscription?
Yes, but only through the vendor's official command-line tool, run as an agent session. Cerberus never proxies a consumer subscription. API keys are different: they go through the gateway, from the vault.
Do I need a particular vendor's software?
No. Everything works with no vendor CLI installed: the built-in agent uses whatever model the gateway serves, local or cloud. Other CLI agents and cloud providers are optional profiles you add.
Which systems does it run on?
Linux first. The code is pure Go with no cgo, so it builds for macOS and Windows today. macOS runs the service and agent sessions, without the Linux-only extras. Windows has no agent sessions yet. A desktop client comes later; until then any OpenAI-compatible chat app can use the gateway.
Do I need a GPU?
Not to start. Cerberus reads NVIDIA and AMD cards when they are there, and plans model loads around free VRAM. Without one, you can run small models on the CPU through your engine, or use cloud models through the gateway with your own keys.
Can I put it on the internet?
Please don't. Keep it on loopback, your LAN or your tailnet, use TLS for anything that is not loopback (for example tailscale cert), and pair each device instead of sharing the admin token. The threat model explains why.