Stop starting
from the beginning.
Give an assistant the background it needs for one task. Choose the records, review what leaves your vault and keep the rest private.
Early access SEED Context and general vault API/MCP sharing are in development. Opening an outside assistant today does not connect it to your SEED vault.
Give your assistant a useful starting point.
Prepare for a project handover without handing over your entire life. Select the project notes, define the purpose and review the information the assistant receives.
A context permission
A chosen assistant and a specific task
- Included
- Selected project notes and the decisions needed for this handover.
- Excluded
- Private messages, health records and unrelated collections.
- Your control
- A reviewable scope, an expiry and a way to stop future access.
Start with what matters.
You choose the material and the result. Your private vault keeps the original records together.
Choose the task and tool
Name the assistant and what you want it to help with. A connection should have a clear purpose.
Preview the context
Select the records and review the material before authorizing access. Keep irrelevant information out.
Control the connection
Set the allowed scope and duration. Review access and stop future retrieval when the task is done.
Bring the right pieces.
- Selected records or a reviewable brief
- A named assistant or agent
- The purpose and access limits you choose
Make something useful.
- A useful context package for a defined task
- Scoped access for an approved connection
- A way to review and stop future access
A connection is a permission.
An outside assistant receives only the material you approve for that connection. Check its own data policies before sharing; its processing takes place outside SEED’s control.
Revoking access stops future retrieval through the service. It cannot erase information an outside tool has already received or someone has downloaded.
Privacy and controlA few useful answers.
Can I connect my whole vault to ChatGPT or Claude now?
No. General vault context sharing is on the waitlist. Links to an outside assistant open that service; they do not authorize or establish a vault connection.
Will there be an API and MCP connection?
Scoped API and MCP access are part of the planned Context experience. The integrations guide distinguishes that work from the separate deletion-guide MCP that is available today.
How is this different from making a brief?
A brief is a document you review and share. Context adds a defined permission for a tool to receive selected information, potentially through an ongoing connection.
Does stopping a connection recall everything it received?
No. It can stop future service access, but copies already received remain subject to the recipient’s own handling. Share only what the task needs.
Make room for
what comes next.
Leave your email for SEED updates and early access. Your account and private vault will bring your tools together.
