Open source · Apache-2.0 · runs locally
Point at what is wrong in your running app and your AI agent gets a real task — the CSS selector, source file and line number already attached.
No account No cloud Node 22+
.vibeflow/, inside your repo
npx @vibeflow-tools/cli — nothing to install
The re-explanation tax
Reviewing an agent's work is the hidden cost of AI-assisted development. The context lives in the browser, the description lives in your head, and the task lives somewhere else. Vibeflow collapses the three.
A picture of a broken button is detective work. Your agent needs the element, the file and the line — not a JPEG and a guess.
Four paragraphs to describe a layout bug the browser could have named in one click. Every paraphrase loses precision, and the agent guesses at the rest.
A designer spots it, a message gets sent, a developer re-derives the context ten minutes later. A two-minute fix costs twenty.
How it works
No extension, no account, no config file. One command starts a local server that injects the annotation layer into any page — including the app you already have running.
Start the local server and the kanban board opens — the same server serves the annotation overlay. Drop one script tag into the app you already have running, or drag the bookmarklet.
Nothing is proxied and nothing is rewritten — the overlay is a single script that talks to your machine.
Hover to see the selector, click to pin a task, type one line, set a priority. Vibeflow captures the CSS selector, the React component and the source file and line number for you. Alt+A toggles annotation mode.
Screenshots attach to the element they describe, and everything lands
in .vibeflow/ where it can be committed to git.
Paste one line into Copilot, Claude Code, Cursor or opencode. The agent claims the highest-priority todo task, moves it to in-progress, reads the full context and implements it.
The claim is atomic, so several agents can run at once without ever picking up the same work.
Not just annotations
Annotations create tasks — and the tasks live on a board you will actually open. Real hierarchies, real statuses, real history, and a CLI that mirrors every action so your agent never needs the browser.
Backlog → todo → in-progress → review → done, with filters by status, tag, type and user, plus an activity feed per task.
Break an epic into children that keep their own status and history. The tree renders in the board and in the CLI, so an agent can pick up a leaf.
Paste a screenshot anywhere in the panel, or let Vibeflow capture the annotated element — it lands on the task, not in a Downloads folder.
Every task is a JSON file in .vibeflow/. Commit it, diff it,
grep it, delete it. No database, no proprietary format, no lock-in.
Every action exists in the terminal and on the board. Humans use the board; agents use the CLI; both read the same tasks.
--next claims atomically, so a swarm of agents
can drain a backlog without two of them ever touching the same task.
tasks --next.
Bring your own agent
No API keys, no plugin, no vendor lock-in. Tasks are plain files and the CLI is a single command, so anything that can read a file or run a shell can use Vibeflow.
Paste it once. --next claims the top todo task
atomically, prints the selector, file and line, and moves it to
in-progress — safe with several agents running at the same time.
Install
No sign-up, no dashboard, no onboarding. Run it once with npx,
or install it globally for day two.
npx @vibeflow-tools/cli kanban
localhost:3700/inject
Drag the annotate bookmarklet to your bar — no code change, any page.
npx @vibeflow-tools/cli serve ./my-app
The same overlay, injected for you — an alternative to the script tag or bookmarklet.
npm install -g @vibeflow-tools/cli
Adds the short alias: vf kanban
Requires Node.js 22+. Any framework — context is richest with React in dev mode. Licensed Apache-2.0.
Who it is for
You build it, you own it, you ship it with an agent.
Designers, PMs and devs working from the same board.
Questions
No. Vibeflow injects its annotation layer with a script tag, its own file server, or a bookmarklet. No extension, no store approval, no browser permissions — and it works on any page, including a production build.
No. Local mode runs entirely on your machine and stores tasks as plain JSON files inside your project. Nothing is uploaded, there is no dashboard to sign in to, and the CLI works offline.
Yes. React, Vue, Svelte, Next.js, plain HTML — anything that renders in a browser. Context is richest with React in development mode, or any build that ships source maps, because Vibeflow can then resolve the component, file and line number for the element you annotate.
In .vibeflow/tasks/ inside your project, as
versioned JSON files. No database, no proprietary format, no lock-in —
commit them to git, read them with any tool, or delete the folder and
nothing breaks.
They solve planning; Vibeflow solves context transfer. Vibeflow's task is created where the bug is visible — in the browser — with the element, file and line already attached, and it is designed to be claimed by an agent from the command line.
It stores plain JSON, so it can live alongside the tracker you already have. Keeping both is a perfectly reasonable setup.
Yes. tasks --next claims the highest-priority
todo task atomically and moves it to in-progress, so two agents running
at once never pick up the same work.
Local mode is free and open source under Apache-2.0, and it always will be. A shared team version is in beta and free for early users; pricing has not been announced.
One command, no account, and the tasks stay in your repository.
Apache-2.0 · Node.js 22+ · no account required