Agent Mode & MCP

Alpha — available for testing and feedback. Its tools and setup may change.

360 Hextile's hextile-agent plugin lets your AI coding agent open and run the same .hextile.json Workflow files used by the desktop studio. It uses MCP (Model Context Protocol) over local stdio. Merge, validation, queueing, and rendering stay in the running 360 Hextile app on your NVIDIA GPU.

This is separate from AI Copilot. Copilot is the chat panel inside the app. MCP is the external automation interface used by Claude Code, Codex, Grok, or another MCP client.

Before you start

• Install and launch 360 Hextile. The local app API must be running.
• Keep the Workflow and its input files on this computer.
• Install hextile-agent in the agent host you use.
• Leave Agent Mode / MCP follow off for headless work, or turn it on if you want the open studio to follow the agent's current render.

There is no cloud renderer or public remote-control service in this path. The MCP server is a thin local proxy to 127.0.0.1:8000.

Install the plugin

Claude Code

Run these as two separate commands:

/plugin marketplace add ansonphong/360-hextile-plugins
/plugin install hextile-agent@360-hextile

Codex

Codex 0.34.0 or later can install from the public package checkout:

git clone https://github.com/ansonphong/360-hextile-agent.git
cd 360-hextile-agent
python3 codex/install.py

Restart Codex, then confirm that the hextile MCP server is connected. The installer also adds the Hextile skill. Use python3 codex/install.py --uninstall to remove both entries.

Grok

grok plugin marketplace add ansonphong/360-hextile-plugins
grok plugin install hextile-agent --trust

Enable hextile-agent in Grok's plugin settings after installation.

Run your first Workflow

The reliable sequence is list → get → validate → run → status:

1. list_workflows lists builtin, user, and project Workflow shelves.
2. get_workflow returns the full Workflow and its editable fields.
3. validate_config dry-runs the same merge and validation used by a real run.
4. run_workflow queues the GPU job. A live run needs a valid, non-empty input path.
5. get_status reports the run until it is completed, failed, cancelled, or crashed.

Send a workflow_id, its origin, and only the overrides you want to change. Objects merge. Arrays replace the existing array; they do not append. The app remains the authority for defaults, validation, model availability, and GPU execution.

Agent Mode follow

Agent Mode is opt-in and off by default. Turn on MCP follow under Help or Settings when you want the running studio to open and follow the agent's local render work. Leave it off when you want the run to remain headless.

• Take control stops the studio from following the agent. It does not stop the render.
• Cancel stops the active GPU work.
• Agent Mode follow is not Copilot Auto and does not give the agent unrestricted UI control.

Troubleshooting

• Agent cannot connect: launch 360 Hextile first, then restart or reconnect the MCP client.
• Workflow validation fails: run get_workflow, keep the original structure, and send a smaller override. Remember that arrays replace wholesale.
• Run stays headless: this is normal while MCP follow is off. Turn on Agent Mode if you want the studio to follow it.
• Input path error: use an existing local file path that the running app can read.

See the Agent Mode feature page for the full tool map and worked recipes.