Local install
Run the daemon, CLI, and native tools on a developer machine.
Carina is designed to run primarily on the developer machine or an internal runner you control. Local-first is the base case.
Install
Section titled “Install”# shell installer (when published)curl -fsSL https://carina.nebutra.com/install.sh | sh
# from sourcegit clone https://github.com/nebutra/carina.gitcd carinamake installStart the runtime
Section titled “Start the runtime”# Prefer CLI-owned daemon lifecycle (discovers kernel + native tools next to the binary)carina daemon startcarina daemon status# Advanced: carina-daemon & (legacy / packaging layouts)
carina versioncarina doctorUse -tools / -kernel only to point at alternate build outputs.
Typical data layout
Section titled “Typical data layout”| Path | Contents |
|---|---|
| Config | Profiles, MCP servers, provider credentials (BYOK) |
| State | Sessions, audit segments, patches, memory |
| Socket | ~/.carina/daemon.sock (default) |
| Logs | Daemon diagnostics |
Exact paths are printed by carina doctor and release notes.
Reasoner
Section titled “Reasoner”- Auto-selects
model-routeronly when an enabled runtime provider is available - Set
CARINA_REASONER_MODELto pin a model-router / BYOK model - Select external compatibility backends explicitly with
CARINA_REASONER_BACKEND=claude-cliorCARINA_REASONER_BACKEND=codex-cli
Gateway (optional)
Section titled “Gateway (optional)”Optional listeners are off by default. Enable WebSocket/HTTP Gateway only with a signing key and explicit bind — see Runtime API.
Updates
Section titled “Updates”carina versioncarina doctorSource of truth
Section titled “Source of truth”- Daemon lifecycle:
carina daemon start|status|stop|logs·carina doctor - Packaging:
docs/release.md - Related: Installation · CLI reference · API overview
- Quickstart — first governed session
- Workers — when one machine is not enough
- FAQ — product boundaries
Was this page helpful?
What went wrong?
Thanks for the feedback.
One vote per page is recorded during this session.