Open source · Windows
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.
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>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.
Reads the project and its CLAUDE.md, asks questions if the task is ambiguous, writes a plan.
Edit the plan, re-plan or approve it with one button.
Implements the plan on the task’s branch.
Writes and runs tests for the change.
Reviews the diff and requests changes.
Audits the change; high and critical findings block it.
Failed tests, requested changes and serious findings go back to the developer automatically
Proposes MAJOR / MINOR / PATCH and a CHANGELOG entry.
Review the diff and reports, accept — Vexa merges, bumps the version and tags.
Everything the CLI can do, behind buttons — with the git hygiene you would do by hand.
Drag cards into the queue; one runs at a time, each on its own branch from the right base.
When a choice changes the implementation, the planner asks with options. Tick “Discuss” to always talk it through.
Live agent log, a Monaco diff, every agent’s report, cost and time — then accept or send back.
A --no-ff merge, the version bump in package.json, pyproject, Cargo or csproj, a CHANGELOG entry and a vX.Y.Z tag.
Edit prompts, model, effort, permission mode and tools — globally or per project.
Status, commit with an AI-written message, branches, history, pull, push and stash.
Your 5-hour and weekly usage in the status bar. At the limit the queue pauses and resumes after the reset.
Open any project; agents follow its CLAUDE.md. None yet? Generate one with /init from the Project screen.
New versions from GitHub Releases, downloaded only when you agree and never in the middle of a task.
English and Russian, light and dark themes, a guided tour on first launch.
Any git project. Vexa checks that claude and git are installed and that you are signed in.
Title, description, type and priority. Optionally a branch name and “Discuss before planning”.
Approve the plan, go do something else, come back to a reviewed, tested, versioned change.
A regular installer: choose a folder and you are done. Installed copies update themselves.
Windows 10/11 · x64 · MIT license
The installer is not code-signed yet. Click More info → Run anyway.
macOS and Linux are planned.
Installed and signed in with a Pro or Max subscription.
Vexa creates a branch per task and merges locally.
vX.Y.Z tag builds the installer and publishes the release with update metadata.Yes. Vexa is open source under the MIT license. You only need your own Claude subscription.
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.
Nowhere new. Vexa runs locally and talks only to the Claude Code CLI; nothing is sent to Vexa’s authors.
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.
Yes — agents work the way Claude Code does. Version bumps understand package.json, pyproject.toml, Cargo.toml, *.csproj and VERSION files.
Not yet. Windows comes first; the app is built with Electron, so other platforms are a matter of time.