Pick the agent role you want, tell us about your business, and generate the first blueprint before you create the Command Centre account. The install clones the right repo onto your machine, runs setup with your answers pre-filled, and gets you running locally with full file access in under five minutes.
1
2
3
Pick the agent
How this works · security model
Local-first. Everything runs on your machine. Your API keys, files, and data live in + the agent's repo folder — they never leave your device. Our cloud only sees your tenant settings (encrypted at rest with a per-tenant key) and chat metadata.
~/.bravo
Bring your own model. OpenRouter (one key, every model) is the easy path. Direct Anthropic / OpenAI / Gemini also supported. Your key sits in .env.agents on your machine, gitignored, and is read at runtime when the bridge calls the model.
localhost:9100 is YOUR machine's loopback. Not a shared network, not someone else's computer. The bridge daemon binds to 127.0.0.1:9100 only — kernel-level, the OS will refuse any connection from outside your machine. When the dashboard fetches http://localhost:9100/chat, that request never leaves your computer.
Browser-side gate. Chrome blocks HTTPS pages from accessing local-network endpoints by default (Private Network Access). You'll see a one-time prompt the first time the dashboard tries to talk to your bridge — clicking Allow creates a per-origin permission. The only origins that can fetch your bridge are the dashboards in the bridge's CORS allowlist (today: agent-dashboard-cc90210.vercel.app + your own localhost dev server).
Command Center
Path-allowlisted file reads. The bridge can only read files under the agent's repo root. Any path that escapes (.., absolute paths outside the repo, OS-level paths like /etc or C:\Windows) is rejected before fs.read runs.
HMAC-paired heartbeat. The bridge identifies itself to the dashboard with a per-machine bearer token issued during pairing (HMAC-bound to your tenant + machine fingerprint, stored in ~/.oasis/bridge_token). You can revoke any paired machine from /devices — the bridge sees a 403 on its next ping and self-stops within 60s.
No third-party data sharing. Your file contents, agent prompts, and chat transcripts route browser → localhost direct. The model provider you chose (Anthropic / OpenRouter / etc.) sees the prompt + tool calls because that's how the model runs — but only through your key, billed to your account. We do not proxy your traffic through our servers.
Want a managed deploy? The local install above is fully self-serve and free to run. If you'd rather have us host the agent (managed deploys + premium support are billed monthly), reach out at conaugh@oasisai.work and we'll set you up.
