Use Taskhold with Grok Build

What you get with Grok Build and Taskhold

• Grok claims tasks as "Grok Build in <repo>" and plans each one into steps.
• Progress, the running step and blocked questions on the live board.
• A summary on each finished task, readable from any device.

Connect Grok Build to Taskhold

1. Start the 7-day trial, open Settings > API keys and create a key for this machine. It starts with atd_sk_. One key per tool and machine lets you revoke each one on its own.
2. Export it in your shell profile: export TASKHOLD_API_KEY=atd_sk_...
3. Add the server to ~/.grok/config.toml. That's the user config, so the entry stays out of the repo.

[mcp_servers.taskhold]
url = "https://taskhold.com/api/mcp"
headers = { "Authorization" = "Bearer ${TASKHOLD_API_KEY}" }

Or add it from the command line. The single quotes keep your shell from filling in the variable, so the config stores the reference and not the key:

grok mcp add --transport http taskhold https://taskhold.com/api/mcp \
  --header 'Authorization: Bearer ${TASKHOLD_API_KEY}'
grok mcp doctor taskhold

Tell Grok Build how to use the list

Grok loads AGENTS.md (and CLAUDE.md) from every directory between the repo root and where you start it, once you trust the folder. Add the workflow to AGENTS.md:

## Tasks (Taskhold)

The person and I share a task list through the taskhold MCP tools. They watch a live board while I work.
Pass project: "<repo folder name>" on every call (created on first use, no ids needed).
- Session start: taskhold_get_current and taskhold_updates, both with project. Keep the cursor.
- New request: taskhold_begin with title, project, steps and agent: "Grok Build in <repo>". It files the task, plans the steps and starts the first one. Queued work: taskhold_list (project, status todo), then taskhold_begin with task_id.
- Each step done: taskhold_complete with start_next: true. Steps drive the progress bar.
- Long step: taskhold_progress on the step (N of M, or a percent) with a short message. Every few minutes at most.
- Need a decision: taskhold_block with one specific question, then taskhold_updates with task_id, since and wait: 50 until the reply arrives.
- Done: taskhold_complete on the task with what changed and how I checked it.
- A TODO or bug I'm not fixing now: taskhold_create with project (or taskhold_create_from_todo with file and line).

One limit to know

Grok also loads MCP servers from ~/.claude.json, Cursor's mcp.json and a project .mcp.json. If Claude Code reaches Taskhold through keyless sign-in, Grok picks up that entry with no key, and every call fails with 401: Taskhold's sign-in only works for Claude Code, Cursor, Codex, claude.ai and ChatGPT. Name your config.toml entry taskhold, as above. When names match, config.toml wins. Keep the host as taskhold.com, because www.taskhold.com redirects and the header doesn't survive the redirect.

What leaves your machine, and how to disconnect

Taskhold receives task titles, steps, progress messages, questions and summaries, whatever the agent or script sends. Taskhold never sends code or commands to your machine, and it doesn't read your repository.

To cut a tool off, open Settings > API keys and revoke its key. The next call fails with 401. Then remove the Taskhold entry from the tool's config so it stops trying.