FlowKy assumes you already have an agent and pay for it. It fits around that loop rather than replacing it.

The loop it is built for

You see something wrong in a browser. You capture it, with a comment. That capture reaches your editor with the console output, the failing requests and the screenshot attached — so the agent starts from evidence rather than your description of it.

The agent changes code. You replay the flow that covers the area it touched. If the flow still passes, the change did not break the path that mattered.

What the agent gets that it would otherwise guess

The current state of the page, not a description of it. The actual console errors. Which requests failed. The flows that constrain the area. The tasks already filed against the site. The brand details so it stops inventing placeholder copy.

What it does not do

It does not run your agent, choose your model, or write prompts for you. The AI features are on your own key, and there are none that run without you asking.

Which agent

Any of them. The bridge and the context are agent-agnostic — Claude Code, Cursor, Copilot and Gemini all read the same repository.

The editor and the site stay joined

Sync travels both ways: it brings your project's captures, tasks and flows into the repository for the agent, and it pushes the latest audit's digest — severity totals and the open findings — up to the project's page, where it sits beside the browser's captures as the project's third voice. The store of record stays in the repository.

FlowKy: Open this project on flowky.ai resolves the workspace to its web project from the git remote, or from the linked domain, and opens the right page — no hunting through a list.