Why TweakLine connects to your agent locally first
Your page, your edits and your screenshots stay on your machine. That is the reason Local is the default.
TweakLine connects to coding agents through the Model Context Protocol (MCP). In this release the only connection is Local: a small companion program on your computer that both the extension and your agent talk to over localhost. Nothing passes through a server of ours.
Why not start with a hosted relay?
The pages people open TweakLine on are often unreleased: a staging build, an internal tool, a redesign that is not public yet. Screenshots and change logs from those pages are exactly the kind of thing you do not want crossing the internet by accident.
Keeping the first version local means the question "where did my data go?" has a short answer: your browser, your computer, and whichever agent you chose to connect.
What does the agent get?
Over the connection your agent can read a short session summary, the full list of changes, and screenshots you took. It can also export styles as CSS, Tailwind, SCSS or JSX, mark changes or comments as done, and read or re-run the accessibility scan. Local adds one extra: the agent can wait for you to press Send, so you can work in rounds.
None of this gives TweakLine access to your code. The agent edits your repository with whatever permissions you already gave it.
What about Cloud?
Cloud and Self-hosted connections are coming soon. They will be useful when the agent runs somewhere other than your own machine. Until then, Copy as Prompt works with any agent and needs no connection at all.