CorvinLabs/CorvinOS

It routes every turn to the cheapest model that fits — and proves the saving from its own audit log.
It remembers, learns in the shadow before it decides, and runs your team's agents behind fail-closed gates.
git clone https://github.com/CorvinLabs/CorvinOS.git && cd CorvinOS && ./install.sh
Token savings ·
Self-learning ·
Skills 2.0 & ACP ·
CorvinOS as an OS ·
Organizations ·
A2A ·
Video ·
Marketplace & plugins ·
Extensibility ·
Claude Code ·
Install guide
---
🎥 Video — Compliance in the AI era
A short walkthrough of how CorvinOS keeps AI work compliant with GDPR and the EU AI Act. The preview below plays right here on GitHub.
45 s preview · full video (MP4, hosted in this repo) · on YouTube
---
⚡ Quick Start
**TL;DR** — you need git; the installer brings everything else (Python via uv, Node.js, Claude Code).
The one-liner is a small bootstrapper: it git clones this repository into ~/CorvinOS /
%USERPROFILE%\CorvinOS (or fast-forwards an existing clone; override with CORVIN_DIR) and
hands over to the repository's own installer. Everything runs from that clone — there is no
PyPI package. Prefer to read before you run? Inspect
install.sh / install.ps1,
or clone by hand:
| | Linux · macOS · WSL | Windows (PowerShell) | Claude Code |
|---|---|---|---|
| **Install** | git clone https://github.com/CorvinLabs/CorvinOS.git && cd CorvinOS && ./install.sh | git clone https://github.com/CorvinLabs/CorvinOS.git; cd CorvinOS; .\install.ps1 | /corvin:install |
| **Update** | sh update.sh | .\update.ps1 | /corvin:update |
| **Uninstall** | bash uninstall.sh | .\uninstall.ps1 | — |
The console opens at **http://127.0.0.1:8765/console/** once it really serves the app.
Install and update are safe to re-run. Your data and configuration (.corvin/ inside the clone —
git-ignored — and ~/.config/corvin-voice) are never touched by an update.
Install — what it does and its options
1. Refuses to run outside a CorvinOS clone (no .corvin_repo / pyproject.toml) — before anything is downloaded.
2. Bootstraps uv (pinned, checksum-verified) and a local Node.js; installs your clone with uv tool install --editable, plus the offline voice models.
3. Installs Claude Code if it is missing.
4. Builds and starts the console, waits for an HTTP 200 with the app shell **and** a working local login, then opens the browser. If that proof does not come it says why instead of reporting success (Windows errors).
Because the install is editable, the code that runs **is** your clone.
**Windows:** if PowerShell answers "running scripts is disabled on this system", allow local scripts once
(Set-ExecutionPolicy -Scope CurrentUser RemoteSigned, or only for this window:
Set-ExecutionPolicy -Scope Process Bypass -Force) and run .\install.ps1 again.
Full reference: docs/setup/INSTALLATION.md ·
docs/windows-installation-guide.md
Update — what it does and its options
update.sh / update.ps1 pull main into your clone, reinstall, rebuild the console, restart, and prove
the new build is served (scripts/verify_install.py). If not, they **roll back** automatically.
Local changes are stashed and re-applied; a force-pushed main leaves your old HEAD as branch
corvin-update-backup- . Reload open console tabs with Ctrl+Shift+R afterwards.
Exit codes: 0 updated · 1 failed, rolled back · 2 rollback failed too · 3 another install/update runs.
Update never installs: with nothing installed (or a legacy PyPI install) it prints the install steps above.
More: docs/setup/UPGRADE_GUIDE.md
From inside Claude Code — /corvin:install and /corvin:update
Step-by-step: Installing via Claude Code below.
Uninstall
uninstall.sh / uninstall.ps1 stop the services, archive everything you cannot re-download (secrets,
bridge pairings, the audit chain, sessions, voice models) to ~/corvin-backup- .tar.gz
(mode 600; restore with tar -xzf -C /), remove the rest, and exit 1 if a leftover scan finds