Captured today
- Slack14:42
Marcus confirmed the revised SOW
- Browser13:18
Security checklist: three open controls
- Meeting12:06
Pricing held at the current tier
The brief
The renewal can move without another meeting.
- The revised SOW is with Priya, receipt confirmed.
- Pricing stays at the current tier through Q3.
- Security review is Friday. Marcus owns it.
Briefed from this sphere
Each sphere decides who and what gets briefed.
Capture from the places you already are.
- Slack
- Discord
- Telegram
- Calendar
- Browser
- Meetings
Discord
Telegram
CalendarCuration without the chore.
Curated context beats captured context, but curation has always been the maintenance job that dies by Thursday. Virgil makes it one gesture, in the moment, in the place you already are.
- 01
Read it, add it.
Something worth keeping in your browser goes to the right sphere with one action. The source stays attached, so the why survives.
One gesture, source attached
- 02
Said in Slack, add it.
An important message keeps its author, thread, and time. The decision survives the scroll, and Telegram and Discord work the same way.
Meaning kept, not just text
- 03
Decided in the meeting, already in.
Virgil sits in your meetings. Decisions, owners, and open questions land in the sphere before you are back at your desk.
Up to date without trying
Spheres
Worlds that don't collide.
A sphere is a bounded world of context: the Acme renewal, the house move, the side project. Each has its own memory, its own view, and its own rules. Work never leaks into life, and one client never hears about another.
See it
Open a sphere and read exactly what Virgil knows. Prune it, correct it, pin what matters. Nothing is a black box.
Scope it
Every sphere sets its own permissions: which sources feed it, which people can see it, which agents may read it.
Prove it
Test a sphere against different models and compare how it performs before you rely on it.
Context that travels.
Context usually dies with the person holding it. In Virgil it ships. Hand a teammate the renewal sphere and they start from decisions, owners, and open loops instead of a cold thread. Bring the contractor into the renovation. Meeting notes arrive pre-briefed, and tasks carry their history with them.
- Decisions and their owners
- Open loops and what unblocks them
- Sources and receipts, attached
- Nothing from your other spheres
Priya is up to speed in one handoff.
- Claudeacme-renewal | house-move
- Codexacme-renewal | side-project
Sphere-scoped, read-only, revocable. Compare how a sphere performs across models before you rely on it.
Your agents, on staff.
Virgil speaks MCP, so the context you curate works everywhere you do: Claude, your coding agent, whatever ships next. No re-explaining, no per-app memory silos, no lock-in. Agents read sphere by sphere, with permissions you set, and your context never stops being yours.
Useful because it knows. Trustworthy because you decide.
Virgil runs on your machine. Spheres decide what it knows, who can see it, and which agents can read it. Nothing leaves without your say.
Plans
More spheres. More sharing. More agents.
Start where you are. Change plans as Virgil becomes the way your world stays briefed.
Compare every planStop re-explaining yourself.
Install Virgil, start your first sphere, and everyone who needs the context has it, human or agent.