SharedContext connects to an Agent through MCP. Once connected, the Agent can open one selected project's Context, keep a durable session map, and read or write scoped Markdown documents.
1. Connect your Agent
Claude Code has a dedicated Superself plugin. Other tools can connect directly when they support authenticated remote MCP at https://superselfs.com/mcp; their exact setup and validation vary by client. Follow the current steps on the installation page.
2. Open a session
Ask the Agent to call session_open once at the beginning of substantive work. Name the project when your Space contains more than one. The tool returns a session id, the project it actually opened, and the current personal, Space, and Project knowledge.
Open SharedContext for the Website Launch project. Tell me which project you opened and summarize only the returned indexes before continuing.
3. Work normally
The Agent logs completed steps, confirmed decisions, proposals, assumptions, and open questions to the session map as work progresses. Labels matter: an Agent proposal does not become a user decision because it was written down. This working record survives Context compaction, so the session can recover without asking you to reconstruct everything.
4. Save something worth carrying forward
Ask the Agent to preserve a confirmed decision, finding, or convention. It uses knowledge_write to create or update a Markdown document in the appropriate scope. Every change keeps revision history, but history alone does not establish decision authority.
Save the launch date I just confirmed as a user-confirmed decision in this project's Context. Keep the rollout idea as a proposal.
5. Check the result
On the next session, name the same project and verify that the Agent opens that project, finds the decision, and still treats the proposal as unresolved.
Next: Complete a first handoff.