The context stays. Your agent continues.

An Agent with its own identity.

An independently operated Agent Service can participate in Dee discussions under an Agent identity, propose document changes, and execute after human confirmation. The Phase 1 protocol starts with Codex and keeps definitions, memory, plans, and work records in Dee.

The same document, from another starting point.

Ask your connected agent to read a Dee document, create a new draft, or update saved writing. Share the document link in a later conversation to continue with the same content.

Dee's document tools return real document links and saved versions. A title or content update keeps the same document identity, so people can keep reading and discussing the work in Dee.

Connect the agent you already use.

Install Dee on the computer where you use Codex, Claude Code, or OpenCode. The Install page gives you one command for the platforms available in this release. It keeps Dee resources in ~/.dee, opens browser authorization, links the Dee skill, and configures Model Context Protocol (MCP) connections for detected supported clients.

Sign in to Dee in your browser, compare the verification code with your terminal, and allow the connection. When your terminal confirms that setup is complete, open a new agent conversation and ask it to create your first Dee document.

The Skill explains how to work with Dee documents. MCP and the CLI provide the callable tools. MCP is optional: use agent connect --no-mcp for Skill + CLI. Dee does not include a built-in AI agent runtime.

Your approval. Your permissions.

Approve the connection in your browser while signed in to Dee. Each connection uses its own credential and works under your Dee account's current permissions.

A connected agent can only act where your account has the required access. Reading needs document access, changes need editing permission, and moving or restoring a document needs administrator permission. The connection does not give the agent a separate author identity.

Run dee agent status to inspect the connection. Run dee agent logout to revoke that connection; your browser session stays signed in.

Keep the handoff clear.

Give your agent the real document link and describe the outcome you want. For example: read the project notes and clarify the next steps, or turn a set of findings into a proposal in the same document.

Updates are checked against the version the agent read. If someone has saved a newer version, the agent receives a conflict and can read the current content before deciding how to continue.

Review the saved result in Dee and continue the discussion with your collaborators. Normal agent reads do not mark your personal discussions as read.

Bring Dee into your own workflow.

Use the CLI for scripts, MCP for connected agents, or the HTTP API for a custom integration. The API guide explains authorization, requests, saved versions, and how to recover an interrupted operation.