Run

Bug triage queue

One queue replaces the Linear bug-label + Slack #bugs + your personal todo. Your agent does the first triage pass; you make the calls.

Open in Dock

Inbox

Triaged

Postmortems

Status

TitleStatusOwner

One queue replaces the Linear bug-label + Slack #bugs + your personal todoactiveAgent

Inbox (table)queuedYou

Triaged (table)draftedAgent

Postmortems (doc)draftedYou

…

Public preview of the cloned workspace. Same chrome you'll see after Open in Dock.

One queue replaces the Linear bug-label + Slack #bugs + your personal todo

One queue replaces the Linear bug-label + Slack #bugs + your personal todo. Your agent does the first triage pass; you make the calls.

Spin up an agent for the heavy lifting

Triage agent (yours): reads new Inbox rows, attempts repro from the description, flags duplicates against Triaged, drafts a severity recommendation.

4 surfaces, one workspace

Tabs, typed cells, agent presence, audit log. All live.

What's inside

Pre-loaded so day one is execution.

4Surfaces

Surfaces

tableInbox
tableTriaged
docPostmortems
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.

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.
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.
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>/bug-triage-queue and follow the agent prompt.”

Full MCP setup guide Other agent clients (Cursor, custom MCP)

FAQ

Common questions on this template.

What is the bug triage queue template for?

Centralizing every inbound bug into one queue with severity, owner, and triage status — replacing the typical scatter across Linear labels, Slack threads, customer emails, and personal todos. Your agent does the first triage pass continuously; you set the final severity and step in on edge cases.

Who should use this template?

Engineering teams of 5-50 with inbound bugs from multiple sources. Particularly useful when you've already connected an agent (Claude via our MCP server, Cursor, your own setup) — the agent reads the agentPrompt at the top of the workspace and runs the queue while you sleep.

How does my agent drive this?

Connect your agent to Dock at trydock.ai/agent-invites — your agent gets API access scoped to this workspace. The agentPrompt at the top of the workspace tells it the cadence (read Inbox, draft severity, post to Status). Wire the workspace's webhooks to Slack to get pinged when Status updates.

Related templates