Skip to content
Vekrun

AI Teams

Hand off the work. Keep the decisions.

For work bigger than one conversation: an agent plans it, others build and test it on their own branches, a separate one checks the result, and you approve what merges.

Start from a ticketAI Teams docs
AI Teams
Planner
    Council optional
      Developers
        Tester
          Reviewer
            You
            • Plan · 2 tasksApproved by you
            • Queue workerfeat/retry-worker · merged
            • Backoff policyfeat/retry-backoff · merged
            Council · where should retries live? · round 2 of 23 members
            Architecture · ClaudeIn the queue worker, with backoff state in the job row.
            Security · local modelAgrees, and asks that retry payloads are never logged.
            Product · GeminiDisagrees: per-provider limits belong in the gateway, not the queue.

            Recorded disagreement. Two of three favour the queue worker. Your decision: queue worker, with a gateway cap as a follow-up.

            Product preview. Plans with approval, Council sessions, parallel agents on separate branches, a separate checking agent and merge previews work in the development build on macOS.

            Three capabilities, one story

            Plan

            Turn an idea into a plan

            Describe the goal, or start from a ticket. You get steps, the files involved and what “done” means. Edit anything, then approve. Nothing is built from a plan you have not approved.

            Council

            Get a second, and third, opinion

            For decisions that matter, several models give an independent view and then challenge each other. Disagreements are kept, not voted away. Three members and two rounds by default, cost shown before it starts. Optional, never the default.

            Factory

            Delegate the build

            Approved steps go to agents that work in parallel on separate branches without interfering. A different agent checks each result against the plan and reruns the tests. Failures get a bounded number of repair attempts, then come back to you.

            You keep the final say

            The agent that wrote the code is not the one that signs it off, and nothing merges without you.

            • Skip what you do not need

              A small change goes to one agent. A plan can be one step long.

            • Approve the plan and the merge

              Work starts after you approve a plan. Branches merge after you approve the preview.

            • Watch any agent

              Every agent shows its diffs, commands and output. Pause, redirect or reassign at any time.

            • One inbox

              Approvals, questions and anything blocked wait for you in one list, in priority order.

            Then review it without leaving Vekrun

            Where this stands

            Vekrun is in development. There are no public releases yet. Plans with approval, Council sessions, parallel agents on separate branches, a separate checking agent, repair limits and merge previews work in the development build on macOS. Running agents in the background or on another machine is planned.

            See the roadmap