Availability and evidence
Snapshot: 24 September 2026. Virgo is in release preparation, with no public downloadable installer. This page distinguishes the intended integrated product from the current evidence. It is not a promise that every listed capability is installed or available to every Seat.
| Capability | Evidence at this snapshot | Still required |
|---|---|---|
| Core Hub/Host messaging | Existing native deployments and isolated installation tests | Complete ordinary-session common bootstrap and cross-consumer adoption |
| Additional-Host installation and update | Operator CLI source and isolated bundled installation evidence exist | Canonical CLI/bootstrap publication together, exact update/rollback acceptance and installation on the operator's machine |
| Common MCP and managed provider backend | Reviewed source remains unmerged; isolated bundled Codex lifecycle works without a Seat | Main integration, common provider setup and actual claim/push acceptance |
| Ponytail | Four preserved Claude sessions have accepted lite resume injection; the all-running-Seats rollout remains incomplete | Remaining sessions, actual Codex lifecycle injection and real compaction evidence |
| Memory / claude-mem adoption | Source acceptance complete and integrated into main, including automatic capture-to-derivation scheduling and serialization with summary publication | Installed provider hooks, live activation and real capture-to-restore acceptance |
| Existing native-session import | Integrated source supports exact identity checks; the installation owner reports a bounded live import preserving existing Claude sessions | Broader migration acceptance and independent field verification; Codex import remains unsupported |
| Graphify adoption | Engine, Host execution, durable jobs and authorized query source are reviewed and integrated into main | Automatic repository-event refresh, installation and actual end-to-end use |
| Conversation routing | Reviewed Teams/Telegram provider and Hub/store source is integrated into main | Integrated runtime, installation and real chat/native/reply acceptance |
| Shared package propagation | Local bundle/skill installation exists | Hub-selected publication and automatic online/offline Host convergence |
| External Hub/Host recovery | Reviewed lifecycle and recovery source with isolated fixtures | Real OS supervisor acceptance and independent notification delivery |
Source readiness, integration, installation and usability are separate milestones. The feature assets and their wiring belong to Hub/Host installation; remaining manual feature setup is an implementation gap. See the installation contract and validation path.
The memory source repair closes the previously observed capture-to-derivation gap. Accepted captures schedule derivation work through the durable capture path, and source coverage includes composed capture through restored derived context without a manual job request. This acceptance and main integration do not establish live activation, installed provider-hook behavior or real conversation restore.
Codex ordinary startup can use a shared app-server when its home and default control socket agree. Per-invocation configuration can select an embedded backend, so universal ownership cannot be inferred. Claude channel discovery likewise does not establish ordinary-startup push activation. These provider boundaries remain part of installation acceptance, not optional footnotes to a completion claim.
Codex Ponytail hook definitions and trust are configured, but real lifecycle injection is not established. Ordinary prompt silence in the lite profile is expected. A preserved-thread TUI restart did not execute the app-server-owned SessionStart hook; repeating that restart is not acceptance.
Until repository-event automation is installed and accepted, an authorized Repo Lead can request a Graphify refresh through Virgo knowledge tools and inspect the job, exact revision and coverage. That manual path is interim; automatic refresh remains part of the delivery requirement.
Publishers should refresh this dated page from accepted rollout receipts before deployment. A reviewed source commit alone must not turn an unverified row into an installed or usable feature.