Send visual edits to Cursor or Copilot
inspecta does not write your repo. It hands the Changes batch to Cursor or GitHub Copilot, then clears the list when the agent is done.
How it works
- Install the inspecta VSIX in Cursor or VS Code. Open the bridge in the status bar and reconnect from Chrome.
- On localhost, send a batch from the toolbar or CSS Changes. Ask the agent to plan, then apply in one pass.
- inspecta watches the implementation and removes finished items from Changes. No localhost? Copy a prompt or share a link.
Frequently asked questions
Can I send visual QA fixes to Cursor?
Yes. After you apply a fix on the live page, send the Changes batch to Cursor or Copilot. inspecta does not write the repo. The agent does.
Do I have to paste CSS into Cursor chat?
No. inspecta sends the change to the IDE agent. You do not copy hex values into a chat window and hope it picks the right selector.
Does this only work on localhost?
Sending straight to Cursor or Copilot needs the project running locally and the inspecta IDE extension open. On staging you can still share the change as a prompt with full context.
Does inspecta write the files?
No. The IDE agent writes the repo. inspecta sends the batch over localhost and clears Changes when the work is done.
Can I send more than one element?
Yes. Send from the element toolbar, from a single row in CSS changes, or send every pending change in that panel at once.
What if I use another agent?
Copy the batch as a prompt for any IDE agent, copy plain CSS, or share a public link.