Canvas (macOS app)
The macOS app embeds an agent‑controlled Canvas panel usingWKWebView. It
is a lightweight visual workspace for HTML/CSS/JS, A2UI, and small interactive
UI surfaces.
Where Canvas lives
Canvas state is stored under Application Support:~/Library/Application Support/Clawdbot/canvas/<session>/...
clawdbot-canvas://<session>/<path>
clawdbot-canvas://main/→<canvasRoot>/main/index.htmlclawdbot-canvas://main/assets/app.css→<canvasRoot>/main/assets/app.cssclawdbot-canvas://main/widgets/todo/→<canvasRoot>/main/widgets/todo/index.html
index.html exists at the root, the app shows a built‑in scaffold page.
Panel behavior
- Borderless, resizable panel anchored near the menu bar (or mouse cursor).
- Remembers size/position per session.
- Auto‑reloads when local canvas files change.
- Only one Canvas panel is visible at a time (session is switched as needed).
CANVAS_DISABLED.
Agent API surface
Canvas is exposed via the node bridge, so the agent can:- show/hide the panel
- navigate to a path or URL
- evaluate JavaScript
- capture a snapshot image
canvas.navigateaccepts local canvas paths,http(s)URLs, andfile://URLs.- If you pass
"/", the Canvas shows the local scaffold orindex.html.
A2UI in Canvas
A2UI is hosted by the Gateway canvas host and rendered inside the Canvas panel. When the Gateway advertises a Canvas host, the macOS app auto‑navigates to the A2UI host page on first open. Default A2UI host URL:A2UI commands (v0.8)
Canvas currently accepts A2UI v0.8 server→client messages:beginRenderingsurfaceUpdatedataModelUpdatedeleteSurface
createSurface (v0.9) is not supported.
CLI example:
Triggering agent runs from Canvas
Canvas can trigger new agent runs via deep links:clawdbot://agent?...
Security notes
- Canvas scheme blocks directory traversal; files must live under the session root.
- Local Canvas content uses a custom scheme (no loopback server required).
- External
http(s)URLs are allowed only when explicitly navigated.