Your agent. Connected to Dee.

Connect Codex, Claude Code, or OpenCode to your Dee documents. Install the connector, approve access, and create your first document.

Connector available for macOS · Apple Silicon, macOS · Intel, Linux · ARM64, Linux · x86-64

For documents and discussion, open Dee in your browser.

InstallApproveUse in your agent

Step 1

Install and connect.

On the computer where you use your agent, open Terminal and run the command below. It installs the Dee connector for your user account and opens your browser for approval.

Setup detects Codex, Claude Code, and OpenCode from their command or existing configuration. Dee’s document workspace runs in your browser. You can sign in or create your Dee account during approval.

Available for macOS · Apple Silicon, macOS · Intel, Linux · ARM64, Linux · x86-64Version 0.1.0

Install and connect

curl -fsSL 'https://dee.cool/install.sh' | sh

What to expectYour browser opens an approval page. Keep Terminal running while you connect.

Downloads and checksums

The recommended command above installs and connects Dee for you. These native executables are available for manual installation.

macOS · Apple Silicon 6.0 MBSHA-256: f905dc2fb7d2a761e578c4d12a92b0f74e789c5a99fd0284c5fe2313c847637a

macOS · Intel 6.7 MBSHA-256: dd367ca184dcb92f6d41ab331dadb8c350a2037ed22fc1162ac7e7443715b434

Linux · ARM64 6.0 MBSHA-256: 0c141cc3d1d08d6036881c35dc80d7af0b06e90078c35a6a1bf8b597cc05008b

Linux · x86-64 7.0 MBSHA-256: b0e82d1960e55bb911bc698d1e18e339600693ab4ee84da96330c42ae5c35db1

For a manual installation, create ~/.dee/bin, save the executable as ~/.dee/bin/dee, make it executable with chmod +x ~/.dee/bin/dee, and run ~/.dee/bin/dee --base-url 'https://dee.cool' agent connect.

Step 2

Approve access in your browser.

Sign in to Dee if asked. Check that the account shown is the one you want to connect, and compare the verification code with the code in your terminal.

Choose Allow connection, then return to Terminal. Dee links its skill and configures optional MCP for detected supported agents. The terminal lists each result, the paths changed, verification checks, and any steps still needed. Only approve a connection you started.

What to expectTerminal confirms authorization and lists the setup result for each detected agent.

Step 3

Give your agent a first task.

After your terminal confirms setup, open a new agent conversation. Ask it to create a Dee document with a short introduction and give you the document link.

Open the returned link in Dee to check the saved result. You can read it, edit it, discuss it, and use the same link in your next conversation.

Try this in a new agent conversation:

Create a Dee document titled “My first Dee document” with a short introduction, then give me its link.

What to expectYour agent returns a Dee link. Open it to check your saved title and content.

Check or disconnect at any time.

Use the installation check command to check your skill links, client entries, authorization, and tool catalog. The disconnect command revokes this connector’s credential and keeps your browser session signed in.

Dee keeps its executable, skill source, configuration, credentials, state, and update backups in ~/.dee. Client skill directories contain soft links; MCP entries point to the same executable. A convenience link is added to an available user PATH directory, preserving existing files.

Check your installation

~/.dee/bin/dee agent doctor

Connect again

~/.dee/bin/dee --base-url 'https://dee.cool' agent connect

Disconnect this connector

~/.dee/bin/dee agent disconnect

Good to know

Do I install the skill and MCP separately?

The installer configures both where supported. Skill and MCP are independent: the Skill guides your agent, while MCP or the Dee CLI calls document tools. Run agent connect --no-mcp to use Skill + CLI without changing MCP settings.

What if the browser does not open?

Open the authorization address printed in Terminal. Check your account and compare the code, allow the connection, then return to Terminal. Keep the installer running while you approve.

What if I cancel, or the code expires?

Run the connection command again to get a new request and verification code. Dee reports a connection failure separately from a successful installation, so you can reconnect without reinstalling.

What if I already have a Dee connection?

Running setup again updates a connection owned by this installer and connector. Existing unrelated settings are preserved. A conflicting client entry is kept and reported separately while setup continues for other clients. Running connect again discovers newly installed supported agents and reuses valid authorization.

Review your first document.

Open the link your agent returned. Check the saved writing and keep working in Dee.

Open your documents