Bring your own agent.PulseDev points it.
PulseDev doesn’t ship an AI. It runs the coding agent CLI you already have installed and signed in to, in your project folder, and gives it the element you clicked.
Which coding agents does PulseDev work with?
Three agent CLIs currently. Pick a default in Settings › Agents, or switch per fix in the widget.
- Claude CodePoint at the element that’s wrong in your own browser, say what it should be, and PulseDev hands it to the Claude Code you already use. The diff waits for your approval.
- CodexPulseDev gives the Codex CLI the element you mean, its selector, styles and a screenshot. In review mode, it asks Codex for a proposed diff that you review and apply on the page.
- Gemini CLIPulseDev runs Gemini CLI in ACP mode, sends it the element you clicked and what you want changed, and shows Gemini’s work next to the element until you approve the diff.
OpenCode is temporarily disabled. See its integration status.
How does PulseDev talk to each agent?
Each agent has its own way in. PulseDev uses the one each CLI supports.
- Claude Code: the claude CLI in print mode with stream-json output. PulseDev reads each message and tool call as it streams.
- Codex: the Agent Client Protocol through the codex-acp adapter when it’s installed, and codex exec with JSON output when it isn’t.
- Gemini CLI: the Agent Client Protocol, with gemini --acp.
With ACP agents, permission requests come back to the widget and the run waits for your answer. With every agent, review mode asks for a proposed diff instead of file edits. PulseDev applies proposed changes when you click Approve.
PulseDev finds each supported CLI on your PATH and in the usual install folders (Homebrew, ~/.local/bin, ~/.bun/bin, ~/.npm-global/bin, ~/.cargo/bin). Settings › Agents shows detection, version and custom-path controls for Claude Code, Codex and Gemini CLI.
Questions about agents
- Do I need an API key?
- No. PulseDev runs the agent CLI with the login you already set up in it. It never asks for or stores your credentials.
- Do I pay PulseDev for tokens?
- No. Usage counts against your own agent plan, as if you ran the agent in a terminal. PulseDev has no AI service of its own.
- Can I use more than one agent?
- On Pro and Founder Lifetime, yes: every supported agent, chosen per fix. The Free plan runs one agent of your choice.
- Does my code go to PulseDev?
- No. Your agent sends prompts and files to its own vendor under that vendor’s terms. PulseDev runs on your machine and never receives your code or prompts.
- What about Cursor or VS Code?
- PulseDev doesn’t drive editors as agents. Connect editor (MCP) writes MCP config for Claude Code, Cursor and VS Code so they can read and close your annotations.
- Is my agent missing?
- For Claude Code, Codex or Gemini CLI, open Settings › Agents to check detection or set a custom path. OpenCode is temporarily disabled and is not listed in the widget picker.
Your agent already writes the code.Show it where.
Free to start. No credit card.