Portable personas
Move identity, memory, conversation, skills, and bindings as one hash-verified unit.
LONG-LIVED AI PERSONAS
Keep your AI personas continuous across machines, models, and restarts.
Virgo runs AI personas as portable, first-class workloads. Identity, memory, conversation, tools, and authority move together as one verifiable persona—not as a disposable chat session.
Virgo is in active development.
QUICK START
From a new machine to a running persona.
Onboarding measures before it asks. Initialization creates your private canon and the default home workspace. Then add and activate a persona.
01 curl -fsSL https://virgo.codes/install.sh | sh
02 virgo onboard
03 virgo init
04 virgo persona add
05 virgo persona up <name>On the first machine, virgo onboard sets up the hub. On later machines, it joins an existing hub address. Persona creation can suggest a name, asks for a class, and lets you describe its personality—or start with a sensible default.
WHAT IT DOES
A control layer for work that outlives a session.
Continuous context
Resume the same persona lineage across restarts, machines, and model changes.
Recoverable fleet
Measure machines, fence active runtimes, checkpoint state, and recover without creating a duplicate identity.
One CLI
Onboard machines, manage workspaces and personas, run the hub, and inspect the whole system through virgo.
Mechanized safety
Capability stamps, CLEAR tokens, and context receipts turn invariants into loud, verifiable refusal.
One hub dashboard
See system status, edit safe preferences, and finish optional setup from one authenticated local interface.
Multiple workspaces
Keep job, personal, and client domains in one Virgo while mechanisms refuse cross-workspace access.
Use your messenger
Attach Teams, Telegram, Slack, or Email through one adapter contract without changing the persona.
Projects inside workspaces
Bind a persona's concrete duties to a project—the formal work unit, typically a repository—inside its workspace.
Walk your knowledge
Your records are a knowledge graph you can walk, not files you grep. Search, filter, follow provenance, and navigate connected records.
Your system stays yours
Your canon, personas, and records remain owner-controlled. Credential values never travel inside persona snapshots.
CREATE A PERSONA
Give it a duty, then make the character yours.
virgo persona add can suggest an owner-neutral constellation name, then asks which class the persona should serve. The first persona defaults to secretary.
Describe its personality in a few lines to generate its CHARACTER.md, or start with the class default. Language and tone are optional at creation and can be refined later from the Hub.
THE MENTAL MODEL
Three parts, one continuous system.
Persona
A long-lived AI identity with continuing memory, conversation, tools, and duties.
Machine
A replaceable, workspace-neutral place where one or more fenced personas can run.
Hub
Deterministic transport, graph and record storage, channel adapters, and the operational view.
WORKSPACES & PROJECTS
Separate work domains without separate installations.
Every Virgo starts with one implicit home workspace. Add domains for work, personal life, or individual clients while keeping one hub and one machine fleet.
virgo workspace add job
virgo workspace add client-a
virgo workspace listCapability stamps and transport rules deny unauthorized cross-workspace access. Machines stay shared, workspace-neutral resources. Inside a workspace, projects define concrete units of work—typically repositories—and persona duty bindings attach at that project level.
ARCHITECTURE
State moves. Authority stays bounded.
Owner canonbase · classes · people
↓
Lossless persona snapshotidentity · memory · conversation
↓
Factory capability stamptools · scope · workspace · project
↓
Persona runtime
↕
Redis Streams hubtransport · graph · records · fences
↕
Channel adapterTeams · Telegram · Slack · Email
↕
Human
One release SHA covers the CLI, daemons, and hub UI. Persona lifecycle operations require audit-bound evidence; runtime consumers lose authority when their fence is no longer current.
PERSONA LIFECYCLE
Up, work, down, and resume—without replacing the persona.
- UpRestore, verify, stamp, bind, and activate one fenced copy.
- WorkCoordinate, query knowledge, communicate, and land experience inside declared scope.
- DownQuiesce, checkpoint, preserve conversation, fence, and stop safely.
- Resume or moveRestore the same lineage on an eligible machine instead of creating a replacement chat.
TOOLS & AUTHORITY
One stamp. Three consumers. No shadow allowlists.
The same capability stamp drives the exposed tool surface, handler authorization, and launcher allowlist. Ordinary recoverable work inside stamped scope is allowed; credential export, authority-material export, and unauthorized cross-workspace or cross-persona access are denied.
Consequential boundaries route to the correct human or owning lead and are durably recorded before execution.
Read Capability Surface v1 →CHANNEL ADAPTERS
One persona. Any supported channel.
Personas use one transport-neutral human surface. A hub binding selects the channel, adapter, and lane, so moving from Teams to Telegram, Slack, or Email does not rewrite persona tools or identity.
- Cards become text only when an explicit fallback exists.
- Typing may degrade to a reported no-op.
- Unsupported reactions or files refuse loudly.
Nothing is silently dropped.
HUB DASHBOARD
The system's eyes—and the place to finish setup.
Status shows machines, personas, fences, streams, and lifecycle events. Personas brings together each character overlay, language and tone, channel bindings, class-scoped configuration, and related records. Preferences edits non-secret configuration. The setup checklist guides channel credentials, bindings, integrations, and persona settings after onboarding.
A persona edit creates a candidate generation. The owner reviews its diff and restart effect; applying it runs checkpoint → compose → audit → same-identity restart. A failed gate leaves the current generation active.
The dashboard is one authenticated loopback or tailnet interface with a workspace filter. Credentials are never displayed or edited, and every mutation uses the same gated mechanisms as the CLI.
KNOWLEDGE EXPLORER
Your records are a knowledge graph you can walk, not files you grep.
A reusable, record-kind-agnostic explorer lets you browse, filter, and search records, inspect provenance, and follow edges to connected knowledge.
The same component appears in the main Explorer, the Personas records tab, and record details reached from Status, so navigation works the same wherever a record appears.
ONE ENTRYPOINT
The command surface follows the system.
virgo onboardPrepare or join a machinevirgo initCreate your canon and home workspacevirgo workspace add/listManage work domainsvirgo persona add/up/down/statusManage persona lifecyclevirgo hub start/stop/statusOperate hub servicesvirgo statusInspect the whole systemGO DEEPER