Claude Code Setup
Claude Code is the more technical Claude-based path for Automation Agent.
If you want to use it inside the desktop app, install Claude Desktop first and then use the Code tab.
This page is for the Codex / Claude Code mode in the Automation Agent panel, which uses the panel-managed local HTTP MCP server.
Important clarification:
- the Claude Desktop app currently has three tabs:
Chat,Cowork, andCode - the
Codetab is Claude Code running inside the Desktop app - Claude Code is also available outside the Desktop app, including the terminal and IDE integrations
- the
Chattab uses the separate Claude Desktop local-extension path - the
Coworktab is currently not a supported local Automation Agent workflow
For most non-technical users, the current recommended Claude path is now:
This page remains useful for users who explicitly want the Claude Code workflow, whether they use it in the Code tab of the Desktop app, in the terminal, or through IDE integrations.
What You Need
For the productive Claude Code workflow, three things need to be true:
- the local Automation Agent MCP server is available
- Claude Code has an MCP server entry for Automation Agent
- Claude has the Automation Agent Claude Skill installed
The current panel workflow now covers both parts:
- MCP configuration for Claude Code
- access to the generated
automation-agent-claude-skill.zipartifact for Claude skill installation
Best Setup Path
The preferred setup path is from inside the panel:
- open the
MCP Servertab - start or connect MCP
- open the
Agent Setupsection - use
Set Upin theClaude Codecard to install or update the MCP config - open the Claude skill export from the panel and install
automation-agent-claude-skill.zipin Claude underCustomize > Skills - restart Claude Code
- return to the panel and verify the status
Important:
- use the panel in
Codex / Claude Codemode - that mode uses the panel-managed HTTP MCP server
- this is different from
Claude Desktop Chat, which uses a client-launched local stdio runtime
The Claude Skill is the guidance layer. It teaches Claude how to use Automation Agent correctly, including when to inspect first, how to author valid DSL, and how to avoid drifting into invented function names or argument shapes.
Where The MCP Config Lives
For Claude Code, the same config model applies in the terminal and in the Code tab of the Claude Desktop app.
The panel currently installs Claude Code using user scope in:
~/.claude.json
The relevant Automation Agent entry looks like:
{
"mcpServers": {
"automation_blocks": {
"type": "http",
"url": "http://127.0.0.1:53125/mcp"
}
}
}
Scope Notes
Claude Code supports multiple MCP scopes:
local: stored in~/.claude.jsonunder the current project pathproject: stored in.mcp.jsonin the project rootuser: stored in~/.claude.jsonand available across projects
For now, the Automation Agent panel writes the safer user-scope entry so users do not need to manage project-specific Claude config files manually.
Where The Claude Skill Comes From
The Automation Agent panel also ships the generated Claude skill export:
automation-agent-claude-skill.zip
Use the panel workflow to reveal or open the Claude export artifacts, then install that ZIP in Claude via:
CustomizeSkills+Upload a Skill
The same Claude Skill package is used as the guidance layer for Claude surfaces that support skill upload, including Claude Code.
If Claude Code Was Already Open
Restart Claude Code after installing or updating the MCP config or the Claude Skill. Otherwise it may continue using the previous MCP state or older skill instructions.