Agents for your vault.
Connect any source — your vault, Obsidian, Confluence, public or private docs — and let a taskmaster-led team of specialist agents work it alongside you.
Get your own →Message to vault
The taskmaster's working view
Whatever you connect — vault, Obsidian, Confluence, docs — the taskmaster surfaces structure you can act on: what's active, who's on each thing, what's blocked, what depends on what. One prioritization layer across many sources; delegates to specialists when work crosses a boundary.
Illustrative. The view assembles from whatever sources you've connected — not provided by us.
The orchestration
Specialized agents share one corpus, reach you wherever you are, and hand work off to each other when it crosses their boundary. Here's how it fits together.
Reach
iMessage your agents like coworkers, or stay in the web dashboard. Same conversation either way — state is shared across channels.
Handoff
Agents file inbox notes targeting each other. Design escalates to build; monetize escalates to research. Work routes itself, you don't relay.
Memory
Each agent compounds context across sessions — your preferences, prior decisions, your way of working. Not goldfish memory that resets every chat.
Reconcile
The taskmaster forwards inbox notes to the reconciler — the layer that parses natural language and back-propagates structured state into your KB. Every cycle narrates what changed and why; you can see the trail, question any move, roll back if needed.
Connect any knowledge source
Your own vault. An Obsidian library. A Confluence space. A folder of markdown. Public docs you trust. The agent layer works across them — querying, linking, surfacing what matters. Bring as many as you have, or start fresh with the opinionated default vault we run.
Get your own.
Early-access cohort. Hand-onboarded during the seeding-skill pilot. Limited slots.
Email for early access →