The assistant stays on this computer

You still click tabs.

If an agent opens a group of sites and clicks a signed-in console, it should not ask you to paste the page into a chat. 2.0.0 put local access under Settings → AI. This computer only. Tokens stay. Pages are not uploaded to Floweb.

This is not a chatbot product. No progress modal on the canvas. Turning access on and handing over the token authorizes page writes for the session; money and password hosts still have a boundary. Live-site quota and the second-account Pro gate are the same latch as the dock. The agent does not bypass them.

Settings · AI

Local access on

127.0.0.1

Paste the config into Cursor or Claude Desktop. It can list groups, open sites, and click on a signed-in page. Live-site quota is the same latch as the dock.

Not a chat-window product. No progress modal on the canvas.

The assistant talks to Floweb on this computer. Tokens stay local; pages are not uploaded. You still click tabs. The agent uses the local interface.

Connect

Settings → AI, turn access on, paste the config into Cursor or Claude Desktop. Confirm the workspace loop first: add a site, switch groups, pop out. Then let the agent list, open, click. Opening a whole group at once came later and still uses quota.

Playbooks (record once, replay without a model) are a later article. Do not park the daily loop inside a chat log.

Do not

Do not bind access to a non-local address.
Do not describe Floweb as “ChatGPT inside.”
Do not turn the workspace off and leave only the agent. If the hands path is broken, a complete protocol is still the wrong product.

How you pay: Buyout is not Cloud.