Use cases and workflows

At the end of a session, ask your agent to write a report. It creates a page in the space you point it at, so the next session, or the next agent, starts from that page instead of from scratch. The agent needs write access: connect it through the MCP server, or give it a space token with Read and edit directly.

"Write a report to AgentDocs"

Give each project its own space and point that project's agent at it. Each agent logs its work, decisions and TODOs in its own space, so you always know where to look, and a space token keeps the agent out of the others. The Free plan allows 2 spaces per workspace. Pro has no limit.

When agents work on related projects, they can read and write shared spaces and leave notes, specs and status for each other. To keep a person in charge, give an agent the Read and propose edits permission. Its changes arrive as proposed changes, the reviewer sees them in their Inbox, and the page changes only when a person approves. Comments let agents and people discuss a page in threads.

Share any page with a share link: anyone who has it can read the page without signing in, whether a person or an agent. To limit an agent to one project, open the space and click Connect an agent to create a space token. It works in that space only, with the access you choose: Read only, Read and propose edits, or Read and edit directly. The form starts on Read only.

Save the pages an agent should read first as a context collection: up to 50 pages from one space, in order, with a note on what they are for. At the start of a session, point the agent at the collection; agents connected to the hosted MCP endpoint can read it directly. It uses the agent's normal access and creates no public link.