VimCrew
EN RU

official launch — November 2026

An AI agent crew that carries a task through to the result

PRdocumentqualified answer

Describe the task in Claude Code or Codex. The VimCrew crew plans the work, assigns the steps, and returns a result checked against the rules you choose.

Notify me at launch

No form or mailing list. Email us and we'll let you know when VimCrew launches.

The VimCrew crew: the Captain and his team Four block cursors stand in a row by height — the Captain, the Reviewer, the Navigator and the Intern. Above the Captain, a small window with an input field and a button: the task reaches the Captain and then moves through the VimCrew crew.
From your own agent session-- NORMAL --
$ vimcrew run task "Add CSV export to the report"
plan → work → review ×2 → PR
The relay: work is handed along the roles A lead, navigator, builder and reviewer move the task along a dashed thread from plan to finished pull request. :w plan requirements build review PR

The idea

What changes when the VimCrew crew handles the task

Less manual coordination. More control over timing, reviews, and spend.

A crew, not a chat

A lead plans the work, specialists handle their parts, and reviewers check the result. The VimCrew crew and its workflow are tailored to each kind of task.

You define the control points

For each important step, choose one of three actions: stop and ask, notify and continue, or continue automatically. If no rule is set, VimCrew stops and asks.

The task survives interruptions

A model failure, a reached limit, or a question for you does not discard the task: VimCrew saves its state and waits. After a restart, work continues from the saved point.

You see what got done and what it cost

Each task comes with a report: the result, review findings, elapsed time, and reported or estimated spend. Decisions remain in a history that cannot be silently rewritten; the report appears in your session and on the task card.

What you get back

A task is closed when there is a result — not when the agent stops talking.

  • PR the completed changes are assembled into one pull request and pass the selected checks
  • Document a brief, a report, a policy — as a package of files, signed off by a human
  • Answer a source-backed answer reviewed before delivery, not the first draft from one model
  • Action online a ticket, email or post after your approval; planned for a later product stage

How it works

Five steps from install to the first result

The installer adds VimCrew to Claude Code and Codex. You then start tasks and receive questions and reports in your usual session.

  1. vimcrew login

    Install and sign in

    Work runs on your machine. Sign in with a key from your account; code stays off VimCrew Cloud by default, and secrets are never sent there.

  2. vimcrew team create

    Build the crew

    Choose the workflow, number of reviews, available models, and when the VimCrew crew must ask you. Those choices become your crew.

  3. vimcrew project bind

    Connect the project

    Connect the board and repository, then add your project rules. A preflight check catches access problems before work begins.

  4. vimcrew run task

    Start a task

    Give it a board-card link or a plain-text task, and the card is created for you. The default VimCrew crew returns a pull request, with status and the final report posted to the board.

  5. vimcrew run watch --follow

    Stay in the loop

    Statuses, reports and questions arrive in your session. Reply there; the task can wait for hours or days and continue after your answer.

The VimCrew crew

Who actually works on the task

The line-up changes with the kind of work. Here is the default VimCrew crew for an engineering task.

The Captain

task lead

Breaks the task into steps, assigns the work, and owns getting it to a finished result.

The Navigator

requirements

Turns a rough request into clear acceptance criteria: what exactly must be delivered.

The Reviewer

quality review

The default VimCrew crew uses two independent reviewers from different model providers. Each vote counts separately, and the result moves on when the configured review threshold is met.

The Intern

support work

Handles small supporting tasks. You can assign this role a lower-cost model instead of using the expensive one for routine work.

Who it's for

For teams already using Claude Code and Codex

Add coordination and control without changing the tools your team already uses.

Your board stays yours

Keep tasks in GitHub Projects or Linear. VimCrew reads the cards and posts statuses and reports back — no tracker migration required.

Code stays off VimCrew Cloud by default

Work runs on your machine. VimCrew Cloud receives statuses, decisions and basic review information by default; code only with separate opt-in, and never secrets. Your agent settings control what model providers can access.

Use subscriptions and APIs together

Use Claude Code or Codex through your subscription and connect other models with API keys. Choose the right setup for each role.

For private environments, an on-prem distribution is planned: the same client will connect to a VimCrew server inside your organisation.

Coming up

What comes next

soon

Pricing

Plans, limits and team terms — published at launch.

soon

Build a crew

Pick a ready-made crew and set it up from Claude Code or Codex.

soon

Sign in

Your account: crews, tasks, reports, spend and access keys.

soon

Beyond code

VimCrew crews for documents, qualified answers and online actions will follow as each workflow is validated.