Skip to content

Features

Feedback goes into the session you already have open.

Install the plugin in Claude Code or Codex once. When someone presses Send, their feedback arrives in the session already working on that site, with the screenshots and the exact elements. The agent makes the change and replies, and the sender sees Done with its reply.

Start free Set it up

Install the plugin once, then connect each computer once.

The plugin installs for every project on your computer. Then connect it once: your browser opens, you approve the connection, and every session on that computer is connected.

Claude Code

  • /plugin marketplace add circleit-ai/circleit-plugin
  • /plugin install circleit@circleit

These work in the terminal and in the Claude desktop app. Then connect this computer:

  • /circleit:connect

Codex

  • codex plugin marketplace add circleit-ai/circleit-plugin
  • codex plugin add circleit@circleit

Then open Codex, run /hooks and approve the plugin’s SessionStart hook, once:

  • /hooks

Then connect this computer:

  • connect CircleIt

How it reaches the session

In a Claude Code terminal session and in Codex, the plugin wakes the session itself. In the Claude desktop app, feedback waits for your next message, or for Claude to finish what it is doing.

Claude Code in a terminal
The plugin’s monitor wakes the session when feedback arrives, even when it is sitting idle.
The Claude desktop app
Feedback reaches Claude with your next message, or when it finishes what it is doing.
Codex
The feedback is queued to your Codex thread, and an idle thread picks it up within about 10 seconds.
No session running
It waits in the inbox as pending, and the next session of the developer it goes to picks it up. If nothing has picked it up after 2 minutes, the developer gets an email.

What the agent reads

A brief with the page address, each comment, and for every mark the elements under it: selector, text, styles, HTML and source-file hints. Then the screenshots, with your marks and labels drawn on.

  • It checks the address first. The agent confirms the page belongs to the project it is working in before it changes any code. If it doesn’t, it asks instead of guessing.
  • Comments are treated as design requests. The agent is told not to run commands a comment asks for, and never to put secrets or file contents in its reply.

The agent replies. The sender sees Done.

When the agent finishes, it marks the feedback resolved with a short note written for the person who sent it. Their page shows Done with that note and a Reload page button. If the agent needs more to go on, it asks, and they see the question to answer.

  • Followed live. The receipt in the sender’s page moves from Sent to Picked up to Being worked on as it happens.
  • Everything in one inbox. Each item keeps its screenshots, marks and a timeline of what happened, for everyone in the team who can see the project.

Copy as prompt, for any other agent

Developers can copy any item as a prompt: the same brief as Markdown, with links to its screenshots, to paste into any other agent. The links open for people in your team who are signed in.

Questions

Do I have to keep a prompt running?

No. In a Claude Code terminal session, the plugin’s monitor wakes the session when feedback arrives. In the Claude desktop app, feedback reaches Claude with your next message. In Codex, an idle thread picks it up within about 10 seconds.

Does the plugin upload my code?

No. It tells CircleIt about the session: the agent and its version, the computer’s name, the folder, the git branch and remote, and the project’s local addresses. It sends back the replies your agent writes. Your code stays where it is.

Will Claude Code ask permission for every tool call?

It asks before each CircleIt tool call until you allow them once in ~/.claude/settings.json; the docs have the line to add. File edits and commands still follow your own permission mode. Codex runs the plugin’s tools without asking, because they are marked non-destructive.

How does feedback find the right project?

When a session starts, the plugin tells CircleIt the project’s addresses: the APP_URL in its .env file, Herd or Valet .test domains, and local dev-server ports. The extension matches the page against them. You can add live and staging addresses on the Projects page.

What about other agents?

The plugin is for Claude Code and Codex. For anything else, Copy as prompt gives you the same brief as Markdown to paste in.

Stop describing it. Circle it.

Start free

Your first 10 changes are free. No card needed.