Building it
Dispatch
Dispatch starts your project’s own coding agent when you hand an idea off. Walden opens an issue in your repository, the agent picks it up where it already runs, on your account, and Walden follows the build from there to the pull request.
What it saves you
Without dispatch, someone has to open their coding agent, connect it to Walden and ask it to build the idea. With dispatch, handing the idea off starts the build. You still follow it, answer its questions and review it from the idea, as in Following a build. Walden still builds nothing: the agent runs on your account with the company that makes it, not on Walden’s, and Walden never merges a pull request.
Which agents it can start
- Claude Code. Through its GitHub Action: Walden opens an issue that mentions
@claude, and the Action runs in your repository. - Copilot. Copilot’s coding agent: Walden opens an issue and assigns it to Copilot as you, once GitHub has confirmed it’s you.
Any other coding agent works the way it always has: someone starts it with a key. See Coding agents.
Set a project up
You do this once for each project, and the project needs a repository first. See Repositories.
- Open the project’s settings and choose the Builder tab.
- Under Which coding agent builds this project’s ideas?, choose the agent. None keeps things as they are. It saves as you choose. If the project has more than one repository, choose which one it builds in.
- Follow the steps under Set the repository up once. Each is yours to do on GitHub, and Walden gives you anything to paste, with Copy.
For Claude Code
- Install the Claude Code GitHub Action in the repository.
- In the repository’s Settings → Secrets and variables → Actions, add two repository secrets:
ANTHROPIC_API_KEY, your Anthropic API key, andWALDEN_KEY, a key you make in Settings → Coding agents. The workflow sees only these: not an environment’s secrets (GitHub may list Production and Preview ones, made by your host), and not the Agents tab’s, which is Copilot’s. - Add the workflow Walden shows you at
.github/workflows/walden.yml, on the repository’s default branch.
For Copilot
- Turn on Copilot coding agent for the repository. It needs a Copilot plan that includes it.
- Make a key in Settings → Coding agents and add it as the Agents secret
COPILOT_MCP_WALDEN_KEY, under Secrets and variables → Agents. Only that drawer reaches Copilot’s MCP servers, and only names startingCOPILOT_MCP_. - In the repository’s settings, under Copilot → MCP servers, add the configuration Walden shows you.
Start a build
- Open the idea’s More actions menu (…), choose Hand off…, then With a coding agent. As with any hand-off, Walden lists what’s still open first. See Handing off.
- Choose Start it now in your repository, and if more than one agent is set up for you, choose which. (I’ll start my own agent gives you the line to paste into an agent instead.)
- Press Hand off and start the build (Start the build, for an idea already handed off). The first build sent from a project asks you to confirm, once: it runs on your own account with the company that makes the agent, not on Walden’s.
Walden opens the issue and says Sent to the repository, with the issue’s number. For Copilot, GitHub asks you to confirm first, then the issue is assigned.
The issue tells the agent to read the idea through Walden, keep its list of tasks there, and work on a branch named after the idea (walden/…). In a private repository, the idea’s text comes with the issue, for an agent that can’t reach Walden. In a public one it doesn’t, because an issue there is public.
Follow it
The build panel beside the idea says where the agent’s run stands at its foot, beside the repository, the issue and the pull request. Once the agent has read the idea and made its list, the panel shows its tasks, as it does for any coding agent.
- Opening an issue
- Walden is opening the issue in your repository.
- Sent
- The issue is open, and nothing has landed on a branch yet. The agent may already be reading the idea: its tasks show below as soon as it makes them.
- Working
- Commits are landing on its branch. The panel counts them.
- Pull request open
- Ready for your review. The panel says whether its checks pass, and whether it was merged or closed.
- Couldn’t be sent
- The issue couldn’t be opened. The panel says why, and you can send it again.
- Cancelled
- Someone stopped it, and the issue was closed.
- Its questions. An agent started this way can’t wait for a reply. It asks before its first task, about what the idea leaves open, in the idea’s own words. It builds everything that doesn’t depend on the answer, holds the tasks that do, and stops. Answer it on the idea, as you would any agent’s question: settle the unknown it asks about in the Unknowns list, or answer in the margin. Either closes the question. Walden then tells the agent on the issue and it starts again from there, on the branch its work is on. If it is still working when you answer, Walden waits until it has stopped, so that no second run starts beside the first; the panel says It’s still working. It’s told when it stops.
- When the idea changes. If the idea changes after it was sent, the panel says so at the top. Choose Tell the agent, and it reads the idea again from where it is. Answering its question doesn’t count as a change: it reads the idea again anyway.
- Reviewing. Review the pull request on GitHub, as you would any other. Then, in Walden, mark the idea built, or send it back with what’s left and the agent is started again from the issue. Only a person marks an idea built.
- Stopping it. Cancel the build, in the panel’s ⋯ menu, stops the run and closes the issue. Send it again starts a new one.
- How Walden speaks to it. Only in comments on the issue, or on the pull request for Copilot: a question answered, the build sent back, the idea changed, the build cancelled. Each names the branch the work is on, so a run woken from a fresh checkout carries on where the last one left off. Walden never pushes to the branch, never merges, and never reads what the agent writes on GitHub: what it shows comes from the repository itself.