Self-hosted Agent OS / Rust core / local control

Captain

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.

Install Captain Watch Captain work

curl -fsSL https://github.com/Vivien83/captain/releases/download/v0.1.0-alpha.1/install.sh | bash Install

Release channel Public early access

Verified build Resolving manifest

Distribution Manifest-backed bundles

Loading release metadata

01 / Interactive product demo

Captain keeps the conversation alive while work continues.

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.

127.0.0.1:50051/terminal Interactive demo / representative data

Command

Codex / selected model

$ Ready. The demonstration starts when visible.

02 / Operational simplicity

One operator. Six clear hubs.

The everyday surface stays small. Advanced machinery remains behind the work instead of becoming another dashboard to manage.

Current focusChat

Keep the conversation available while tools and delegated work progress outside the message loop.

Visible: Streaming, tool progress, decisions, and approvals
Durable: Session events, memory links, and compaction checkpoints

03 / A living operating model

Work continues. Captain stays available.

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.

01
Resolve context
Conversation, memory, project state, and current runtime signals.
02
Plan dependencies
Separate independent work from ordered decisions and approvals.
03
Execute under supervision
Detached tools, isolated agents, budgets, timeouts, and progress.
04
Persist and adapt
Checkpoint state, surface uncertainty, ask when needed, then resume.

04 / Built for continuity

Autonomy that remains operable.

Durable by default

Projects, goals, checkpoints, sessions, schedules, and detached run history survive the chat and the daemon.

Interrupted work stays inspectable before retry.

Memory across the relationship

Captain combines bounded semantic recall, session history, user facts, project context, and a knowledge graph.

Corrections create retraction guards so stale facts stop resurfacing.

Agents as services

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.

Awareness without theatre

Consciousness means operational awareness: active goals, weak signals, errors, queues, project attention, and concrete next actions.

No claim of progress without observable state.

05 / Real product surface

Control when you need it. Conversation when you do not.

Captain Control reduces the runtime to six hubs and keeps health, active work, budgets, channels, queues, and recovery actions in one operable surface.

Captain Control showing runtime health, active agents, detached tool runs, budgets, and agent API status — Captain Control. Real product UI with representative, sanitized data.

06 / Production discipline

The operator can always see where control lives.

Constraints and recovery are part of the product, not a disclaimer below it.

Governed autonomy

Approvals, scoped capabilities, budgets, loop guards, and bounded retries.

Isolated boundaries

Deny-by-default channels, typed secrets, callback validation, and SSRF defenses.

Audit and replay

Hash-chained audit records, stable tool-call identity, duration, status, and cost.

Actionable health

Runtime status, queue pressure, disk thresholds, delivery failures, and recovery actions.

07 / Prebuilt and checksum-verified

Install a verified Captain build.

No Rust toolchain is required. Select the target, install the checksum-verified release bundle, then finish provider and channel setup in Captain.

The repository and container registry are currently private. Published release links require access to the Captain repository.

ShellInstaller

curl -fsSL https://github.com/Vivien83/captain/releases/download/v0.1.0-alpha.1/install.sh | bash

Runs the guided setup after installing the verified host bundle.

08 / GitHub release

Published bundles verified against the release manifest.

GitHub release

Loading platform artifacts and SHA-256 sidecars.

Early development

Unleash the future.

Run the operator on your hardware. Keep its history. Inspect its work. Decide what ships.

Start with a verified build