```
CLI + generated files + MCP

One home for AI agents. One shared project brain.

AgentDock turns a GitHub repo into reusable context for Codex, Claude, Cursor, OpenClaw, Cline, and custom agents through CLI, generated files, and MCP.

Claude card visual

Claude

Keeps product intent, project constraints, and decisions in view.

Codex card visual

Codex

Uses the same repo brain to edit, test, and ship changes.

OpenClaw card visual

OpenClaw

Reads generated files and shared context without a reset.

Context anywhere

Now your agents can use the same context, anywhere you work.

AgentDock keeps your repository setup, product decisions, skills, memories, and handoffs in one clean workspace — then turns that context into files and workflows your agents can actually read.

1

Import a GitHub repo and create a project brain automatically.

2

Save the rules, memories, skills, and decisions your agents need.

3

Use the same context in your terminal, generated files, and MCP-ready workflows.

AgentDock context workflow

One project brain

Generated context for Claude, Codex, Cursor, Cline, OpenClaw, and MCP-ready agents.

How it works

From repo to agent-ready context in minutes.

AgentDock gives your AI agents the project context they usually miss: setup, decisions, skills, secrets, sessions, and generated files.

01

Create project from GitHub

Paste your repository URL. AgentDock fetches the repo name, description, tech stack, scripts, and setup details.

02

Store important memory

Save project rules, current bugs, product decisions, commands, and things every AI agent should remember.

03

Add skills for agents

Create reusable instructions like Supabase debugger, clean UI builder, security reviewer, or Codex prompt writer.

04

Save secret references safely

Do not expose real API keys. Store only safe references like agentdock://secrets/OPENAI_API_KEY.

05

Generate agent files

Create AGENTS.md, CLAUDE.md, Cursor rules, CLINE.md, OPENCLAW.md, and shared context files.

Access methods

Three clean ways to give agents the right context.

AgentDock does not force every agent into one setup. It creates the right context path for each tool — terminal, generated files, or MCP-ready workflows.

CLI Access illustration
Local command

CLI Access

Use AgentDock from the terminal to link projects, sync context, search memory, and generate agent files.

Learn how it works
Generated File Access illustration
Context files

Generated File Access

Generate AGENTS.md, CLAUDE.md, Cursor rules, OPENCLAW.md, CLINE.md, and shared context files.

Learn how it works
MCP Access illustration
Live protocol

MCP Access

Let compatible agents fetch live project context, memory, skills, and secret references through MCP tools.

Learn how it works

Supported agents

One project brain for every agent in your stack.

Keep Claude, Codex, Cursor, Cline, OpenClaw, and custom MCP agents aligned with the same project memory, skills, sessions, and generated files.

Codex illustration
Agent 01

Codex

CLI + AGENTS.md + MCP

Shared contextAgent-ready
Claude illustration
Agent 02

Claude

CLI + CLAUDE.md + MCP

Shared contextAgent-ready
Cursor illustration
Agent 03

Cursor

CLI + Cursor rules + MCP

Shared contextAgent-ready
OpenClaw illustration
Agent 04

OpenClaw

CLI + OPENCLAW.md + MCP

Shared contextAgent-ready
Cline illustration
Agent 05

Cline

CLI + CLINE.md + MCP

Shared contextAgent-ready
Custom Agent illustration
Agent 06

Custom Agent

MCP

Shared contextAgent-ready

Workspace views

Three ways the project brain stays useful.

Your project context should not stay trapped in one chat. AgentDock keeps it useful across setup, handoff, and build workflows.

Project context

Project context

Keep the repository brain visible before an agent starts.

Shared workflow

Shared workflow

Move from setup notes to generated files without scattered docs.

Agent handoff

Agent handoff

Give Claude, Codex, OpenClaw, and other tools the same context.

Ready workspace

Create a project brain and keep every agent aligned.

Go to projects