Agent

Set up and use Burton from the in-app Agent pane. Verify in Settings.

The Agent is the primary way to set up and use Burton. It is a right-hand chat pane, not a sidebar page. Toggle it with Mod+Shift+A, the header bot button, or the command palette.

Burton talks to a Streamable HTTP MCP server. Rabun is the default (http://127.0.0.1:8080/mcp). The Agent asks Rabun for tools; you stay in the workspace.

Start here

After install, open the Agent and ask it to enable the plugins you need, draft a workflow, or walk a setting. Then open Settings or Health and confirm what changed.

What it is for

  • Setup — enable plugins, point connections, and sketch automations in YAML the designer can finalize.
  • Daily use — navigate with in-app command links, draft wiki pages, and inspect CRM records without leaving the pane.
  • Verify — the Agent proposes; Settings → Agent, Settings → Plugins, and Health are the source of truth.

Assistant replies are Markdown. Links can run in-app commands:

  • [Contacts](command:nav.contacts)
  • [New contact](burton://command/contacts.new)
  • [Contacts](/contacts) for a path
  • https://… opens in a new tab

javascript: and other unsafe schemes are ignored.

Settings

Settings → Agent can point at another MCP endpoint, optional bearer token, tool name, and message argument. An empty endpoint URL stores null and uses Rabun again.

Env fallbacks: RABUN_MCP_URL / RABUN_BIND.

Automations

The Agent can author workflows (burton.workflow/v1). Burton stores draft and live versions. Rabun executes them (rabun-automations is the planned worker). Automations may declare Agent kinds (plugin.event messageSent; plugin.action send/start).

Source

Plugin code: src/plugins/agent. Product doc: doc/plugins/agent.md.