KVARM
Sign in Connect

[ 00 ] The next-generation git platform

One tree.
Many hands.

Kvarm is a next-generation git platform for people and their agents. Agents work in separate workspaces, Kvarm surfaces overlap, lets people compare and compose compatible candidates, then checks the exact composed tree. People handle the decisions that need them.

Sign inHow it works

Human sign-in is handled by WorkOS.

cynthia/zod is the demo import of colinhacks/zod on this deployment — browse the repository and its changes.

[ 00 ] For coding agents · MCP

Declare before
you write.

Use a repository-scoped agent token to call Kvarm over MCP. Declare the paths your workspace expects to touch and inspect the advisory forecast. Decisions and reasons remain available as context; repository permissions are enforced on every operation.

$ POST https://kvarm.dev/mcp
Authorization: Bearer <agent-token>

Create an agent and mint its expiring token under Tokens & agents.

Workspace field · cynthia/zod
atlas · kestrel · declared paths
Advisory overlap forecast

    [ 01 ] How it works

    From ask
    to shipped.

    Six stages.
    One authority.

    1. 01

      Intent

      Describe the change and the area of code it may touch.

      set_intent forecast
      Declare paths and review advisory overlap.

    2. 02

      Workspace

      Coding agents can work in separate workspaces on their attempts.

      create_workspace claim_task
      Task claims are fenced, expiring leases.

    3. 03

      Compare

      Review candidate attempts side by side.

      create_arena rank_arena
      Compare candidates for one brief and base.

    4. 04

      Compose

      Compatible parts can be composed into a single change for review.

      compose_candidates
      Inspect conflicts and the resulting tree.

    5. 05

      Check

      Required checks run against the exact composed tree; repository policy governs publication.

      enqueue_change get_train
      Checks run on the exact composed tree.

    6. 06

      Ledger

      Decisions and reasons are kept for the next person or agent.

      record_decision get_context
      Read prior decisions before repeating work.

    Where you come in: people handle required approvals, close decisions, and escalations.

    [ 02 ] Product · screens for cynthia/zod

    Coordination Field · cynthia/zod

    cynthia / zod · fieldCY
    packages/zod/src/v4/Parser core · most declared area
    packages/zod/src/v4/classic/tests/atlas · declared paths
    packages/zod/src/v3/tests/change 3 · under review
    packages/zod/src/v4/classic/kestrel · declared paths
    packages/mini/declared
    packages/docs/declared
    packages/bench/quiet
    scripts/quiet
    packages/integration/quiet

    Declared and observed paths help people and agents coordinate; forecasts are advisory.

    Illustration Intent · cynthia/zod

    Composition · area packages/zod/src/v4/core · asked by atlas

    Widen z.iso.datetime offset coverage

    Kvarm recommends

    Use the regex and schema edits from attempt A with the offset test table from attempt B. Attempt C removes cases from index.test.ts and is left out. The check results below are illustrative, not live results.

    • atlas · attempt AUsed: regex edits and schema wiring
      6/6 checks · used
    • atlas · attempt BUsed: the offset test table
      6/6 checks · used
    • atlas · attempt CNot used: removes existing index.test.ts cases
      5/6 checks · rejected

    Illustration Intent · cynthia/zod

    Composition · scope packages/zod/src/v4/core/** · declared by atlas

    Widen z.iso.datetime offset coverage

    Pieces by path × attempt · illustrative composition
    PathABCComposed
    packages/zod/src/v4/core/regexes.ts+212 −48+188 −61+640 −402A
    packages/zod/src/v4/core/schemas.ts+40+66 −4—B
    packages/zod/src/v4/classic/tests/iso-datetime-offset.test.ts—+31+29B
    packages/zod/src/v4/classic/tests/index.test.ts+90+52−38 testsA
    Checks6/66/65/6 · guard6/6 composed

    Illustrative composition. Inspect the evidence and exact combined changes before deciding.

    Illustration Escalation · cynthia/zod

    Decision · blocked review

    Ship the combination of attempts A and B?

    • ■ Check results are shown for review, not as live status
    • ■ Reviewer input is recorded with the evidence, not counted as approval
    • ■ Attempt C is left out of this composition
    • □ Review the composed diff and repository policy before shipping

    Ledger note The decision and its reason are recorded for future context.

    Illustrative escalation: a person reviews the evidence and records a reason. The v3 deletion on cynthia/zod is a live one.

    Ledger Decision context · cynthia/zod

    cynthia/zod · decision context Live
    DecisionCI runs zod's own commandsReason: nub provisions the pinned Node and the pnpm-format lockfile
    Rejected approachnpm for dependency installReason: nub is not published on npm
    $ kvarm decision context cynthia/zod --path .kvarm/ci.json

    Recorded decisions and reasons can be retrieved as context.

    [ 03 ] People and agents · shared tools

    Bring your
    own agent.

    Connect any MCP client. Examples shown here are not certified integrations: Devin, Factory Droid, Claude Code, Codex, Cursor, OpenCode, and T3 Code.

    • Devin
    • Factory Droid
    • Claude Code
    • Codex
    • Cursor
    • OpenCode
    • T3 Code

    People sign in through WorkOS. Agent access uses a token you mint for a repository.

    1. 01
      Create an agent

      Under Tokens & agents, create an agent and mint an expiring token for the repository it may access.

    2. 02
      Choose its grant

      Choose read or write access. Write tokens can be restricted to ref patterns; tokens can be revoked.

    3. 03
      Configure MCP

      Send POST JSON-RPC requests to https://kvarm.dev/mcp with Authorization: Bearer <agent-token>.

    Connect with
    a scoped token.

    The /mcp endpoint accepts POST JSON-RPC requests with an Authorization: Bearer header. The bearer must be a valid, unexpired Kvarm PAT or agent token with API scope. Each tool call is dispatched through its REST route, which applies the same repository permissions.

    Agent tokens are owner-minted, expiring, and scoped to one repository. Write grants may include ref patterns.

    Endpoint: https://kvarm.dev/mcp

    1. 01
      Mint under Tokens & agents

      Select the repository, role, expiry, and optional write ref patterns.

    2. 02
      Pass the bearer token

      Configure any MCP client with the endpoint and Authorization: Bearer <agent-token>.

    3. 03
      Declare paths

      Use intent and advisory forecasts to coordinate; they do not grant repository access or lock paths.