Agent Godette

ACP Agent in the Godot Editor

Per-session model, mode, and reasoning — switch model, reasoning effort, and permission mode per thread, right from the composer bar.

Plan · Queue · SceneTree focus — the agent's TodoWrite plan collapses above the composer, queued follow-up prompts stack underneath it, and any node you've selected in the SceneTree auto-attaches as implicit context on send.

Token flame — Balatro-inspired count-up badge in the dock header. Tracks cumulative tokens since first install (per project), animates a slot-machine count-up + flame shader on every mid-stream usage_update from the adapter. Click the widget to tweak colour, animation speed, count-up duration, and pulse cadence.

https://github.com/user-attachments/assets/d366bfae-d72f-47c6-94e8-c1d31f29df22

What it is

A Godot 4 editor plugin that talks to local ACP (Agent Client Protocol) adapters — Claude and Codex run as stdio subprocesses, the editor is the client. No HTTP bridge.

What it solves

Godot had no in-editor agent. This plugin makes the editor itself the chat surface: attach scene nodes, FileSystem files, or pasted screenshots as context; the agent edits your project in place. No copy-paste between a separate chat app and the editor.

Requirements

Node.js 18+ is required to run the local ACP adapters. Recommended install:

npm install -g @agentclientprotocol/claude-agent-acp @zed-industries/codex-acp

The plugin also falls back to npx -y <package> on first run, so global install is optional — it just avoids the one-time download and works offline afterwards.

Picking a Claude adapter

Two ACP adapters can speak Claude. The dock auto-detects whichever you have installed; both are supported.

Picking a Codex adapter

Only one production option here. OpenAI hasn't published an official ACP adapter, and @agentclientprotocol/codex-acp is still pre-1.0 / experimental.

Authentication

Each adapter handles its own login. Run the underlying CLI once outside Godot to sign in:

• claude-agent-acp / claude-code-acp → Claude CLI login
• codex-acp → OpenAI Codex CLI login

Updating to newer models

Model names and descriptions ("Opus 4.7", "GPT-5.4 / xhigh", …) are sent by the ACP adapter, not hardcoded in this plugin. So when Anthropic / OpenAI ship a new model, what surfaces in the dock depends on which adapter version is running on your machine.

How the dock picks an adapter

The dock probes in this order and uses the first one that exists:

1. Globally installed adapter (npm install -g …)
2. Adapter found in your local Zed install (if you have Zed)
3. npx -y <pkg>@<version> — the plugin pins a specific version here, which is what makes plugin builds reproducible

The plugin pins are bumped each release. If you want fresher model strings without waiting for a plugin release, just bypass the pin by installing the adapter globally — option 1 wins.

Refreshing model strings

# Claude (Anthropic official)
npm install -g @agentclientprotocol/claude-agent-acp@latest

# or Claude (Zed adapter — note: SDK is intentionally older here)
npm install -g @zed-industries/claude-code-acp@latest

# Codex
npm install -g @zed-industries/codex-acp@latest

Then start a new thread in the dock — existing threads keep whatever model list was cached when they were first created. The new thread will get the fresh strings.

Why two projects can disagree

Each Godot project carries its own copy of addons/godette_agent/. If project A has the latest plugin (newer pin) and project B has an older plugin (older pin), they'll show different model descriptions even on the same machine. To unify them: update the plugin in both projects (AssetLib re-download, git pull, or just copy the folder over) — or globally install the adapter so the pin doesn't matter.

Credits

Standing on Zed's shoulders — the ACP transport and most of the UX (plan / queue drawers, composer chips, transcript persistence, tool-call rendering) are modeled directly on Zed's external-agent implementation.