Give Claude Code a signed-in browser and project memory
Connect Claude Code, or any MCP coding agent, to project memory and a browser that keeps its logins, then check past decisions against the live site.
Move work between tools 3 min read
Bring project memory to a coding agent
Use the Dray CLI. One command saves supported coding sessions, imports local history and connects each agent to your shared memory, and none of it needs the browser extension. A memory connection does not give Dray access to your repository files.
ON THIS PAGE
Save coding sessions without the browser extension
The CLI supports Claude Code, Codex, Cursor, Grok Build, OpenCode, Antigravity and Kimi Code. Install it with curl -fsSL https://api.withdray.com/cli/install.sh | sh (on Windows, irm https://api.withdray.com/cli/install.ps1 | iex in PowerShell), approve this computer with your Dray account, and restart your agent. Setup asks which of the agents it found to set up, installs capture hooks or a plugin and Dray instructions, and connects each one to your memory. In Codex it trusts Dray’s hooks for you.
Setup offers to import the last 30 days of local Claude Code, Codex, Grok Build, OpenCode, Antigravity and Kimi Code transcripts. Cursor hooks save new sessions only. For another import, use dray import --since 30d --agents claude,codex,grok,opencode,antigravity; add --dry-run to preview. Upload and memory processing are separate, so imported context may not appear in search immediately.
Separate remembered intent from current code
A planning conversation might say the app uses email sign-in. The repository may already have changed. Ask the agent to compare the remembered design with the files it can see, and report a mismatch before editing.
A useful handoff names the branch, the intended behavior, and the checks that define completion. Leave credentials out. Tell the agent which paths it may change and which existing work must remain untouched.
Connect MCP and check both directions
Setup connects each agent it sets up to your memory directly, with no page to approve. dray mcp lists those connections and dray mcp on restores one. For another agent, add https://mcp.withdray.com/mcp as an HTTP / Streamable HTTP server. If its sign-in asks for the extension, choose Use an access key instead and paste the output of dray key privately into that page. Keep the key out of chats.
Claude on claude.ai and Claude Code are separate clients. Setup’s direct connection replaces the claude.ai connector inside Claude Code, but the computer still needs CLI sign-in before capture can upload. Web chats already saved to the same Dray account are shared through MCP; the CLI imports local coding transcripts, not web history or Claude’s native memory.
Run dray status to check capture and pending uploads, then ask the agent to retrieve a harmless stored detail and name its source. A working MCP lookup does not prove capture is running. A missing browser extension is not a coding-sync failure.
TAKE THIS WITH YOU
A coding handoff
An illustrative template. Replace the details with material you are allowed to share.
Goal: [behavior to add or repair] Relevant prior decision: [decision and source] Repository and branch: [current checkout] Allowed scope: [paths or subsystem] Do not change: [unrelated work] Checks to run: [project commands] First inspect the code. Report any conflict between this brief and the repository before proceeding. Never copy secrets into the brief.
USING THIS WITH DRAY
Keep the context. Check the source.
Dray’s CLI saves prompts and final replies, with pasted images where the agent supports them. It leaves out tool output, local files, worktrees and reasoning. MCP reads the same account’s saved memory. Other MCP clients can use that memory, but automatic coding capture is limited to the six supported agents.
Available sources and connections depend on your setup. Read the privacy policy before granting access.
Sources & next reads
Product details are grounded in the guides below. Example projects and prompts are illustrative, not customer results.