What Stop does while an agent is browsing
Stop ends the agent work you can see. A page the browser already requested, and a tool result the client already accepted, are not pulled back.
Drafted with AI tools (Claude Code and Codex) and published by Rattana Devs. How we write
What Stop does is end further agent actions in the Kitsuvo window you are watching. Press it when you do not want the next click, read, or typed field. Stop does not erase a visit the website already handled, and it does not delete a tool result the connected client already stored.
We make Kitsuvo. These limits match the security page and the privacy policy. The published Windows 0.2.4 installer predates browser_status and cannot complete the current MCP connection check, so it is not a verified agent setup. See the Windows MCP compatibility limit. If browser_status is missing, the profile mode is unknown.
What ends when you press Stop?
On the current Mac release, an AI client drives the browser only after you connect it. The session is visible, and the Stop control is part of that window. Remote access from another device uses the host's separate agent profile, and the Stop control on the host still ends that agent work.
Use Stop when the next step is one you have not accepted: a new host, a form, a download, or a page that asks for a secret. The review to do before the click is in review an unfamiliar site before an agent clicks.
What does Stop leave in place?
A page load that already left the computer is a visit the site has. Stop does not ask that site to forget it. History, cookies, and the score for that visit can remain in the profile the agent used, on your computer, until you clear them.
The app has no telemetry. The connected client is separate. If it already received page text, a snapshot, a report, or a supported screenshot, that copy stays under the client's own policy. What stays on your machine when an agent reads a page sets out those copies.
kitsuvo mcp uses your normal signed-in browser profile by default. Add --separate-profile for a separate persistent profile. Hiding the window with --headless uses an isolated profile. Stop is the control for the session you started. It does not switch profiles or wipe the one the agent was using.
What to do after Stop
| If this already happened | Stop | What you can still do |
|---|---|---|
| The agent was about to open a new link | Prevents that next action | Open the link yourself, or leave it closed |
| The page already loaded | Does not unsend the request | Close the tab. The site may already have the visit |
| The client already received a tool result | Does not delete that result | Delete it in the client, if that product allows it |
Sign-in pages and password fields stay protected unless you start Kitsuvo with --allow-sensitive. Stop is not a substitute for leaving that flag off.
Questions people ask
Does Stop delete the page from the website's logs?
No. Stop ends further agent actions. A request the site already received stays on that site under its own policy.
Does Stop remove the result from my AI client?
No. A tool result the client already accepted remains with that client. Stop does not reach into the client and delete it.
Is the Stop control available when the window is hidden?
Hiding the window with --headless uses an isolated profile. Remote sessions still end from the Stop control on the host. Do not assume a hidden session has no effect until you have ended it.
Does Stop work as a verified control on the published Windows installer?
No. The published Windows 0.2.4 installer cannot complete the current MCP connection check. Windows 0.2.4 remains available for ordinary browsing and local filtering. Use the current Mac release for a verified agent setup.
Comments
Read the discussion or sign in to add a plain-text comment.
Loading comments…