Point at the page.Codex writes the fix.
PulseDev 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.
How does PulseDev run Codex?
It uses the Agent Client Protocol when the codex-acp adapter is installed, and codex exec otherwise.
PulseDev looks for the codex-acp adapter first. If it’s on your PATH, PulseDev starts it, points it at your codex binary, and talks to Codex over the Agent Client Protocol (ACP). Permission requests from Codex come back to the widget for you to answer.
If the adapter isn’t installed, PulseDev runs codex exec --json with the prompt and reads the JSON events. Messages and tool calls appear in the activity log as Codex works. Replies to a finished fix resume the same Codex session.
Either way, Codex runs on your machine in your project folder, signed in the way you signed it in.
With the codex-acp adapter on your PATH, PulseDev talks to Codex over the Agent Client Protocol. Without it, PulseDev falls back to codex exec with JSON output.
What does a fix with Codex look like?
The same loop for every agent. The widget on your page talks only to the PulseDev server on your machine.
- Point. Turn on Inspect in the widget and click the element. Shift-click to add more.
- Describe. Write the change in plain words and pick Codex as the agent. The widget sends your note with the page URL, the element’s selector and markup, styles, recent console errors and failed requests, a page outline and a screenshot of the element.
- Watch. PulseDev starts Codex in your project folder. Its reads, searches and commands show up next to the element as they happen.
- Approve. In review mode PulseDev asks the agent to propose a diff rather than edit files. Approve applies the proposal, Reject discards it, or reply to ask for another pass in the same session.
Runs are queued one at a time per project. Review the applied changes in your editor before committing them with your usual git workflow.
How do I set up Codex with PulseDev?
You need the agent CLI installed and signed in. PulseDev finds it on your PATH and in the usual install folders. Settings › Agents has detection and custom-path controls for Claude Code, Codex and Gemini CLI.
- Install PulseDev. Download the app, add your project folder and click Set up project. That adds the widget script tag (or the Vite plugin) to your dev site.
- Install the Codex CLI and sign in. Install codex and sign in from a terminal once. PulseDev uses that login.
- Optional: add codex-acp. If the codex-acp adapter is on your PATH, PulseDev uses ACP, which lets Codex ask for permissions in the widget. Without it, PulseDev uses codex exec.
- Check Settings › Agents. Codex should show as found, with its path and version. Pick it as your default agent or choose it per fix in the widget.
- Optional: connect your editor. Connect editor (MCP) writes the PulseDev MCP server into
.mcp.json(Claude Code),.cursor/mcp.jsonand.vscode/mcp.json, so your editor can list, read and close annotations.
{
"mcpServers": {
"pulsedev": {
"type": "http",
"url": "http://localhost:3899/mcp",
"headers": { "Authorization": "Bearer YOUR_TOKEN" }
}
}
}The app fills in your project’s port and token. The MCP server offers four tools: list_annotations, get_annotation, update_annotation_status and get_element_context.
Codex and PulseDev: common questions
- Does PulseDev need an OpenAI API key?
- No. It runs the codex CLI you installed, with the login you set up. PulseDev never sees your credentials.
- What happens in review mode?
- PulseDev asks Codex to read the code and return its change as a proposed diff instead of editing files. You approve or reject it in the widget. With Auto-apply on, PulseDev runs codex exec with --full-auto, or answers ACP permission requests with allow.
- Can I use Codex on the Free plan?
- Yes. Free includes one project and one agent of your choice, so Codex can be that agent. Pro and Founder Lifetime include every supported agent.
Other agents PulseDev runs
- 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.
- 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.
Keep Codex.Add a pointer.
Free to start. No credit card.