Supported agents

Which coding agents Blume works with, and what you get in each one: conversation tracking, usage and the Blume plugin.

Blume works with coding agents in three independent ways: it reads their conversations on your computer, it shows the usage of your subscription, and it adds the Blume plugin so the agent can record deliveries. Not every agent supports all three.

We recommend doing delivery work in Claude Code or Codex when you can. Only those two have hooks, which let Blume reach an agent between tool calls. Other agents get your answer the next time they call a Blume tool.

What each agent supports

AgentConversations in the appUsagePlugin
Claude CodeYesYesTools, skills and hooks. Installed and updated by the app.
CodexYesYesTools, skills and hooks. Installed and updated by the app.
CursorYesYesTools and skill, added with one click
PiYesNoTools and skill, added with one click
Oh My PiYesNoTools and skill, added with one click
Other listed agentsNoNoTools and skill, added with one click
AiderNoNoRuns Blume as a command
Grok BotNoNoConnects to Blume’s hosted tools with a setup message
Any other agentNoNoSets itself up from a prompt you paste

Add the plugin

Open Plugin in the app. Claude Code and Codex install from the Overview. Every other agent is under More.

Added with one click: Cursor, GitHub Copilot CLI, Gemini CLI, Antigravity CLI, OpenCode, Factory Droid, Qwen Code, Kiro, Cline, Amp, Pi, Oh My Pi, Hermes Agent, OpenClaw, Grok Build, Goose, Devin, Windsurf, Crush, Continue, Zed and Warp. These agents hold no key of their own. The connection comes from the Blume app you are signed in to.

Set up another way:

  • Aider has no MCP support. It runs Blume as a command and asks you first.
  • Grok Bot runs in xAI’s cloud. Choose Copy setup message and paste the message into the bot.
  • Another agent that supports MCP: choose Copy prompt and paste it into the agent. The prompt holds no secret.