Set up agents

Gutternote can hand a note to a coding agent in two ways:

• Built-in agent. Someone tags it in a thread. Gutternote runs it with your provider key. This page sets these up.
• Your own agent. A developer connects a tool such as Claude Code. See Resolve notes with your agent.

1. Choose an agent

Open the project’s Agents page. Cloud agents lists every built-in agent: Claude, Codex, Copilot, Jules, Cursor, Devin and Grok. Grok answers in the thread. The others change code and open a pull request.

Select Set up on an agent’s card. Its settings open in a panel on the right. Set:

• Handle: what people type after @.
• Display name: how the agent signs its replies.
• Answer when someone writes @handle: turns the agent on.

2. Add the provider key

Paste the key from your account with the provider. Gutternote never shows it again. The provider bills that account for every run.

3. Set limits

• Runs per day: how many times the project can start the agent each day. The default is 50.
• Budget per run (cents): Claude only. The run stops once it has cost this much. The default is 500.

4. Allow repository access

Agents that change code need:

1. A repository chosen on the project’s GitHub repo page.
2. Access to that repository, through the GitHub App or a token.
3. Let agents push branches and open pull requests turned on under Repository access, below the agent cards on Cloud agents.

Grok doesn’t change code, so it needs only its key.

Who may tag an agent

On Configure, pick an option under Who may tag an agent, then select Save who may tag an agent:

Setting	Who may tag
Signed-in members	Workspace members who are signed in. The default.
Your own domains only	Members who sign in with an email domain from your allowed list.
Members who may comment	Members who also pass the Who may comment rule.

The same rule decides whose notes reach a connected agent on their own.

Work destination

The Work destination card on Agents sets where code goes:

Setting	Result
Open a new pull request	The agent works on its own branch and opens a pull request. The default.
Update the branch under review	The agent commits to the preview’s branch, so the same preview redeploys.

The second option needs the build tags on the preview. See Build context.

If an agent is missing from the picker

The @ picker shows only agents that are ready and that you may tag.

1. Check that you’re signed in to the widget as a workspace member who passes Who may tag an agent.
2. Check that the agent’s card on Agents shows Ready. If not, the card names the first thing missing, such as Needs a key or Push is off.
3. Reload the page. The widget loads the agent list when the page loads.