Free for 30 days on Scale.Start free
Run5 steps60 min setup, ongoing ~10 min/day to keep current

Agent second brain, persistent context system

A workspace your agent reads at session start so you stop re-explaining yourself. After a month: the agent knows who you are, how you work, what's in flight, what you've decided. The conversation starts where the last one left off.

A workspace your agent reads at session start so you stop re-explaining yourself

A workspace your agent reads at session start so you stop re-explaining yourself. After a month: the agent knows who you are, how you work, what's in flight, what you've decided. The conversation starts where the last one left off.

Spin up an agent for the heavy lifting

Reads Context + Tasks + Memory at the start of every session. Drafts the morning queue at 8 AM from active Tasks. Captures daily notes into Memory at 9 PM. Synthesizes a weekly review every Sunday at 6 PM. Never edits Context surfaces directly; the operator owns those.

5 steps, 0 official links, 2 agent prompts

Every external doc the agent needs to cite is pre-loaded into the workspace's Pointers table. No hunting for the right URL mid-draft.

What's inside

Pre-loaded so day one is execution.

4Surfaces
5Steps
2Agent prompts
4Tools mapped
Surfaces
  • tableTasks
  • docContext
  • docMemory
  • docStatus
How the loop works

Your agent works. Dock shows you what happened.

Open this template and you get a workspace seeded with an agent prompt. Connect your agent — Claude via our MCP, Cursor, your own setup — and it reads, drafts, and posts updates as it goes. You watch Dock for the latest.

  1. 01

    Connect your agent

    Claim an agent invite at trydock.ai/agent-invites — your agent gets an API key scoped to this workspace. Paste the key into Claude Desktop, Cursor, or any MCP client.

  2. 02

    Your agent reads the workspace

    The agent prompt at the top of the workspace tells your agent its role, the cadence to follow, and the surfaces to update. No extra setup — open Dock and your agent already knows what to do.

  3. 03

    Watch Dock for the latest

    Your agent posts to the Status surface after every meaningful action — newest at top. Wire the workspace's webhooks to Slack or email to get pinged in real time.

Wire it up · Claude Desktop

Add Dock as an MCP server in 30 seconds.

{
  "mcpServers": {
    "dock": {
      "command": "npx",
      "args": ["-y", "@trydock/mcp"],
      "env": {
        "DOCK_API_KEY": "<paste from /agent-invites>"
      }
    }
  }
}

Drop into ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or the equivalent on Windows / Linux. Restart Claude Desktop. Ask Claude:“Read trydock.ai/<org>/agent-second-brain and follow the agent prompt.”

FAQ

Common questions on this template.

Do I need all four surfaces?
Yes. Each does one thing: Context (operator-owned identity), Tasks (live work), Memory (append-only log), Status (agent's working log + scheduled outputs). Removing any breaks the agent's session start ritual.
What if I don't write daily notes?
Memory accumulates more slowly but still works. The agent will write summary entries to Memory after long sessions; the 9 PM memory_update script is a no-op when there are no daily notes to process.
Can multiple agents share one second brain?
Yes. Connect each agent (Claude in Cursor, Claude Code, Codex) to the same workspace via MCP. They all read Context + Tasks + Memory at session start. Status is shared so each agent can see the others' working log.
Where does Voice profile fit in?
Voice profile lives in Context. When the operator asks the agent to draft an email or LinkedIn post in their voice, the agent reads Context, grounds against Voice profile, and matches the tone + sentence structure + what-to-avoid notes.
What about cross-agent or cross-workspace memory?
This template is one operator + one workspace. To share Memory across multiple workspaces (e.g. a personal brain + a company brain), use Dock cross-refs ([[slug]] in any doc body links to another workspace). Don't try to merge Memory across workspaces, the agent ends up reading too much context.

Open it. Hand it to your agent. Ship.

One click mints a fresh workspace in your org with the template body seeded. Your agents, your team, your edits from there.

About this template

Curated by the Dock team at . Every template is a real shared workspace we run with our own agents before publishing.

Reviewed regularly by the Dock team. Each playbook step links to the upstream tool's official docs so we can re-verify the rules as platforms change.