Get started with Vowline

Create an account on this site with your email or Google, and download Vowline for Windows. Open it and click Log in or Sign up: the browser opens, you confirm it is you, and the app opens by itself.

Vowline needs the connection to your account to start. If the connection drops while you work, nothing closes: actions wait until it is back.

Vowline does not write code itself. It runs the coding agents you already use: Claude Code, Codex or Cursor, each through its own command line tool and your own login. In Settings → Executors Vowline finds them, tells you how to install one that is missing, and signs it in through the maker’s own page.

Vowline never sees their passwords or keys, and shows how much of each subscription is left as the agent reports it.

Choose the folder of a git repository. Free covers one project; Pro connects as many as you like and lets a workflow join several repositories, so one task can change the API and the web at once.

If the repository has no remote, the lead offers to connect one, so the code is kept somewhere besides your computer.

Vowline reads the code and groups the files into the parts of the product. Click Describe it and an agent writes .devflow/product.md: who uses the product, what each of them does, the steps of each flow, the files behind each step, and checkable criteria.

You never edit the map by hand: when the code changes, Vowline rebuilds it and marks what changed.

Vowline finds your test and lint commands (npm, pytest, go test, cargo, dotnet, Maven, Gradle, Make) and proposes them in .devflow/checks.json. You approve exactly that file once. An agent never chooses what it is judged by.

On the Team tab, add a lead first, then specialists: describe them in a few words (“backend on Python”) and Vowline drafts their role, their area of the code and a working brief with the best practices of their craft. Each one runs on the agent and model you pick.

Teammates read the code and plan, ask you what only you can decide, and talk to each other in chats; they never write code themselves.

Every task says what makes it done: short, checkable criteria that you confirm. A teammate or an agent then works on it in its own git worktree, so your branch is untouched. When it finishes, Vowline runs the approved checks on that exact commit.

You accept the change, send it back, or let the lead merge changes whose checks all passed.

The Overview shows how much of what the product promises is proven, what broke since yesterday, and what to close next. A promise counts as proven only when its checks passed on the code as it is now; when the code changes, it drops back until it is checked again.

Describe your environments in .devflow/deploy.json and approve it. The lead suggests a deploy when accepted work is ready; production goes out only when you click. Vowline runs it from a clean copy of the commit, keeps a journal, and can roll back.