Open source · Windows

A kanban board where Claude Code does the work

Put a task on the board and Vexa takes it through planning, code, tests, code review and a security check on its own git branch. You approve the plan and accept the result — everything in between runs by itself.

Download for Windowsv0.3.0

Windows 10/11 · x64 · MIT license

Runs the Claude Code CLI you already have, on your Pro or Max subscription. No API keys, no terminal.

$ claude -p --output-format stream-json --permission-mode acceptEdits --append-system-prompt <developer.md>
what Vexa runs for every agent

Every task, the same full cycle

Six preset agents, each with its own prompt, model and permissions. Tasks run strictly one after another, so agents never trip over each other’s changes.

  1. 01

    Plan

    planner

    Reads the project and its CLAUDE.md, asks questions if the task is ambiguous, writes a plan.

  2. 02

    Approve

    your call

    Edit the plan, re-plan or approve it with one button.

  1. 03

    Code

    developer

    Implements the plan on the task’s branch.

  2. 04

    Tests

    tester

    Writes and runs tests for the change.

  3. 05

    Review

    reviewer

    Reviews the diff and requests changes.

  4. 06

    Security

    security

    Audits the change; high and critical findings block it.

Failed tests, requested changes and serious findings go back to the developer automatically

  1. 07

    Release

    release

    Proposes MAJOR / MINOR / PATCH and a CHANGELOG entry.

  2. 08

    Merge

    your call

    Review the diff and reports, accept — Vexa merges, bumps the version and tags.

Built for handing work off, not babysitting it

Everything the CLI can do, behind buttons — with the git hygiene you would do by hand.

Three steps

  1. 01

    Open a folder

    Any git project. Vexa checks that claude and git are installed and that you are signed in.

  2. 02

    Describe the task

    Title, description, type and priority. Optionally a branch name and “Discuss before planning”.

  3. 03

    Approve and accept

    Approve the plan, go do something else, come back to a reviewed, tested, versioned change.

Install

A regular installer: choose a folder and you are done. Installed copies update themselves.

Download for Windowsv0.3.0

Windows 10/11 · x64 · MIT license

“Windows protected your PC”?

The installer is not code-signed yet. Click More info → Run anyway.

  • Windows 10 or 11

    macOS and Linux are planned.

  • Claude Code

    Installed and signed in with a Pro or Max subscription.

  • Git

    Vexa creates a branch per task and merges locally.

What’s new

v0.3.0released

Added

  • Images in tasks: attach any number of screenshots or photos with a button, Ctrl+V or drag and drop; agents open them while planning and implementing. Images live in the app data folder, never in the repository.
  • "Resolve conflict" for a merge conflict on accept: Vexa merges the base branch into the task branch, the developer fixes the conflicting files and the checks run again.
  • "Waiting for you" everywhere: counters on the Board and Projects icons and on project cards, a "Waiting for you" bar on the board with one-click chips, highlighted cards with an action button, and the board scrolls to them.
  • Desktop notifications when a task needs you while Vexa is in the background, and a counter on the taskbar button (toggle in Settings).
  • The top bar is now the window title bar, colored to the theme and dimmed with the page.

Changed

  • The accept button shows where the task is merged: "Accept & merge into main".
  • A merge conflict is shown once, on the task card, in the interface language.

Fixed

  • Two tasks waiting for review no longer propose the same version: the release stage reads the version from the base branch, and accepting one task moves the others to the next version.
  • npm run dev showed an empty window when the dev server listened on IPv6 only.
Full changelog →

Questions

Is it free?

Yes. Vexa is open source under the MIT license. You only need your own Claude subscription.

Do I need an API key?

No. Vexa starts the claude CLI installed on your computer, so work counts against your Pro or Max plan the same way as in the terminal.

Where does my code go?

Nowhere new. Vexa runs locally and talks only to the Claude Code CLI; nothing is sent to Vexa’s authors.

Can agents break my main branch?

Every task works on its own branch. Nothing lands on your base branch until you press Accept, and then it is a regular --no-ff merge you can revert.

Does it work with any language or framework?

Yes — agents work the way Claude Code does. Version bumps understand package.json, pyproject.toml, Cargo.toml, *.csproj and VERSION files.

macOS or Linux?

Not yet. Windows comes first; the app is built with Electron, so other platforms are a matter of time.