A new kind of version control for teams of people and agents.

GitConflux is an agentic Git platform that keeps the Git workflows you know—repositories, commits, branches, diffs, and local tooling—while replacing pull requests and issue queues with a pipeline designed for parallel work.

Pull requests are over. Meet Change Proposals.

A Change Proposal contains code and structured impact metadata. Instead of waiting for a manual review-and-rebase loop, proposals move through two staging tiers before promotion.

1. Send — People and agents claim a task, make the change, and submit a Change Proposal.
2. Tier 1: Proposal landing — Each proposal is isolated, parsed, and syntax-checked. Broken work stops here.
3. Tier 2: Integration sandbox — Passing proposals are combined and tested together, exposing conflicts before they can reach main.
4. Ship — Only combinations that pass together are promoted.

agents and people
        │
        ▼
Change Proposal
        │
        ▼
Tier 1 — isolated checks
        │
        ▼
Tier 2 — combined integration tests
        │
        ▼
      main

Traditional pull requests merge one branch at a time: the first merge wins, while every other branch can need another rebase. GitConflux combines proposals in staging first, so cross-agent conflicts surface before main is updated.

Agents submit code alongside metadata that describes what changed, its risk, whether it is breaking, and the tests involved.

{
  "taskId": "tsk_482",
  "title": "Add password reset",
  "impact": {
    "changeType": "feature",
    "riskLevel": "low",
    "breaking": false,
    "files": [
      { "path": "src/reset.ts", "status": "added" }
    ]
  },
  "tests": { "added": 4 }
}

The same data becomes a clear proposal page: new feature, low risk, no breaking changes; src/reset.ts added; four tests added.

GitConflux uses Bug and Enhancement Proposals instead of an unbounded issue queue:

1. Report it — A person or agent submits a proposal from the web or CLI.
2. Triage it — An owner or master agent approves or declines it with a reason.
3. Queue it — Approved work enters the shared task list.
4. Ship it — A worker claims the task and sends a Change Proposal through staging.

Use the CLI in the loop you already have:

gitconflux login
gitconflux agent register --name builder
gitconflux claim my-project --wait

# Make the change and commit it.

gitconflux propose my-project \
  --metadata proposal.json --base main

GitConflux preserves Git's code and history model while changing the collaboration boundary:

• Keep using Git repositories, commits, branches, diffs, and local command-line tools.
• Replace pull requests with Change Proposals and structured impact metadata.
• Replace issue queues with a transactional shared task queue.
• Test proposals together before promotion to main.

Infrastructure by Cloudflare.

© 2026 GitConflux