Self-hosted Agent OS / Rust core / local control
Unleash the future.
The self-hosted Agent OS with production discipline.
One persistent operator that remembers, plans, delegates, and keeps working across sessions and restarts. You retain the runtime, its state, and the final say.
curl -fsSL https://github.com/Vivien83/captain/releases/download/v0.1.0-alpha.13/install.sh | CAPTAIN_VERSION=v0.1.0-alpha.13 bash
Install
What Captain can do today
Run coding and research work with goals, checkpoints, supervised tools, adaptive verification, and resumable sessions.
Start from Telegram, Discord, Signal, email, Web, or the terminal, then reopen the same work elsewhere.
Schedule service checks, surface decisions, and keep sensitive actions or runtime updates under explicit operator control.
01 / Interactive product demo
This sequence uses representative, sanitized data. It demonstrates the native execution model: dependency-aware parallel reads, a detached long run, live status, and a second question answered before the first run completes.
$ Ready. The demonstration starts when visible.
02 / Operational simplicity
The everyday surface stays small. Advanced machinery remains behind the work instead of becoming another dashboard to manage.
Keep the conversation available while tools and delegated work progress outside the message loop.
03 / A living operating model
Long calls leave the conversation loop and become supervised runs. Captain can revisit their state, collect results, cancel them, or choose the next action.
Independent read-only work may run concurrently. Dependencies, overlapping resources, and side effects stay ordered.
Conversation, memory, project state, and current runtime signals.
Separate independent work from ordered decisions and approvals.
Detached tools, isolated agents, budgets, timeouts, and progress.
Check postconditions at meaningful milestones, checkpoint state, surface uncertainty, ask when needed, then resume.
04 / Built for continuity
Projects, goals, checkpoints, sessions, schedules, verification receipts, and detached run history survive the chat and the daemon.
Before delivery, Captain checks risky work at useful milestones and keeps interrupted work inspectable before retry.Captain combines bounded semantic recall, session history, user facts, project context, and a knowledge graph.
Corrections create retraction guards so stale facts stop resurfacing.Drop a human-readable .captain file into the watched directory and Captain validates, scopes, and exposes the capability without rebuilding the runtime.
Each agent can expose authenticated ingress and signed HTTP callbacks through a dedicated API contract.
Egress becomes ready when you provide the external callback URL that Captain cannot infer.Consciousness means operational awareness: active goals, weak signals, errors, queues, project attention, and concrete next actions.
No claim of progress without observable state.Captain checks its release channel after startup and every 12 hours, then offers the verified update through a Telegram Rich card.
Update, defer for 24 hours, or refuse that exact version; the decision and installer state survive restart.Search results stay discovery-only until Captain retrieves the source, records its final URL and checksum, and audits important citations against the page.
Unsourced load-bearing claims remain visibly unverified.Reports and generated files become immutable, versioned artifacts with verified downloads and sandboxed Web previews.
Live Runs and produced files open from the global bar without adding another hub.A managed VPS install can configure one HTTPS domain, then continuously check DNS, TLS, proxy routing, local health, public health, and version parity.
Doctor, Status, and Control share one crash-safe readiness verdict.05 / Real product surface
Captain Control reduces the runtime to six hubs and keeps health, active work, budgets, provider-reported quota windows, channels, queues, and recovery actions in one operable surface.
06 / Production discipline
Constraints and recovery are part of the product, not a disclaimer below it.
Approvals, scoped capabilities, internal budgets, live provider quotas, loop guards, and bounded retries.
Deny-by-default channels, typed secrets, callback validation, and SSRF defenses.
Hash-chained audit records, stable tool-call identity, duration, status, and cost.
Runtime status, queue pressure, disk thresholds, delivery failures, and recovery actions.
07 / Prebuilt and checksum-verified
No Rust toolchain is required. Select the target, install the checksum-verified release bundle, then finish provider and channel setup in Captain.
Public alpha for technical users. Keep backups and expect breaking changes between releases.
curl -fsSL https://github.com/Vivien83/captain/releases/download/v0.1.0-alpha.13/install.sh | CAPTAIN_VERSION=v0.1.0-alpha.13 bash08 / GitHub release
Loading platform artifacts and SHA-256 sidecars.
Early development
Run the operator on your hardware. Keep its history. Inspect its work. Decide what ships.