These pages are the specifications themselves, not summaries of them. Each document is rendered from an exact pinned commit and states that commit and its hash, so what you read here is what was audited.
Guides
How the product is put together, what the integrated capabilities do, how an installation is verified, and what the evidence actually supports today. Published in English and Korean, from an exact pinned commit.
| Guide | What it covers |
|---|---|
| How Virgo works as a team | How a persistent AI team is organised — Accounts, Spaces, Seats and roles — and how the Hub, Hosts and adapters carry one piece of work from your request through to its delivery. |
| What you can do with Virgo | What the team can do: give work an owner, reach agents through connected conversations, run across machines, control access, schedule requests, and continue with the right context. |
| Installing Virgo | The installation contract, what an installation needs, the current preview command surface, and how to verify completion from the bottom up. |
| Install and update an additional Host | The canonical authenticated procedure for adding a Host to an existing Hub, and for updating, rolling back and reactivating it. |
| Operations and verification | Which status observation establishes what, how to update and roll back an explicit instance, and how to verify each capability from its real entrypoint. |
| Availability and evidence | Dated evidence for each capability at this snapshot, and the delivery boundaries that remain open. |
All guides pinned at e106595060cc2787403439a45e1ef52c191e25f7.
Chat adapters
How to connect Discord, Microsoft Teams or Telegram to a Virgo installation you already run — what each provider needs, and exactly how far the current release takes you.
| Guide | What it covers |
|---|---|
| Connect a chat app to Virgo | What a chat adapter is, who is allowed to talk to the team, what each provider can do, and how to add one to an installation you already have. |
| Add Discord | Discord prerequisites, the minimum channel permissions, where the bot token lives, the descriptor you will need, and the verification chain. |
| Add Microsoft Teams | The public HTTPS endpoint Teams requires, how inbound activities are authenticated, card and file limits, and what stays outside this adapter. |
| Add Telegram | Why one bot token allows exactly one poller, the approval default and its administrators, allowed chats, and what the adapter can and cannot do. |
Written against product 50a34893e3086a6012fd136d5e4a492a9066c5bc.
Manual
The system explained topic by topic — personas, workspaces, machines, channels, the hub, safety, the CLI, and troubleshooting. Start here if you are reading about Virgo rather than looking something up.
Command reference
Every command and option, with what ships in the pinned release kept separate from what is approved design.
Command reference — 16 shipped commands, 19 designed commands.
Specifications
All documents pinned at d62e85485903a5537ee2b73c14201597e29bdaa5.
| Document | Source path | sha256 |
|---|---|---|
| Virgo overview | README.md | 5a5fe652efe4 |
| CLI specification | docs/design/CLI-SPEC.md | 5796137f060f |
| Hub API | docs/design/HUB-API.md | f1eefdd139b8 |
| Hub web dashboard | docs/design/HUB-WEB-DASHBOARD.md | b7f333e51f00 |
| Store schema | docs/design/STORE-SCHEMA.md | 521a417fa9e6 |
| Product record graph | docs/design/RECORD-GRAPH.md | b320c871efce |
| Resident collaboration | docs/design/RESIDENT-COLLABORATION.md | 7ce0d4ed7990 |
| Persona capability surface | docs/design/PERSONA-CAPABILITY-SURFACE-V1.md | 39151a737f91 |
| Audit-gated lifecycle tokens | docs/design/AUDIT-GATED-LIFECYCLE-TOKENS.md | 6df8edb68d2d |
| Channel adapters | docs/design/CHANNEL-ADAPTERS.md | 50de97c84b91 |
| Channel diagnostics | docs/design/CHANNEL-DIAGNOSTICS.md | fea0349bc5f7 |