ModernCIPush. Green. Merged.

Release status: what's live, in preview and planned

Nothing is released. ModernCI runs today on our own repos, on one install we operate. This page says exactly what works, what is in preview and what is planned.

Checked against the code on 2026-10-13. Live means merged and running on our own install. Building means code exists but isn't finished or isn't wired everywhere. Planned means not built.

Availability

WhatStatus
Public release (binary, image, install script)not released. There is no public image or binary yet (F17).
The sourceprivate
Early accessby invitation: request it
modernci.dev fleet view (Sign in)preview, for our own installs
Pricingproposed, nothing billed: Pricing

Runs on

WhatStatus
ForgesGitHub and Gitea live. GitLab planned.
Backendsthis machine (as a separate OS user), an SSH host, a fresh runner per job from a provider (Latchkey). Other clouds planned.
Daemon OSLinux (systemd) and macOS (launchd)
Agent runtimespresets for Claude Code and Codex. Any runtime that speaks MCP over HTTP can connect.

The 10 things

#WhatStatus
1Supersede: a newer push stops the runs it made mootlive
2Reuse of check results by their inputslive
3Affected-only testslive
4Elastic parallel workersbuilding: fresh runner per job works; no autoscaler yet
5Batch and bisect merge queuelive
6Speculative merge queuelive, in part
7Fail fast: cheap checks firstbuilding
8Flake quarantinelive
9Picker: cheapest backend that finishes in timelive, in part
10No idlebuilding

Agent honesty

WhatStatus
Failing tests named on the resultlive
Second witness: a suspected flake re-run alonelive (on the same machine; a second backend is planned)
Tests that disappear against the target raise a questionlive, for nextest
Zero tests or a collapsed duration is redplanned
Red before green, measured by ModernCIplanned
Protected paths: weakening a test needs a personplanned
Flakes classed by causeplanned

Cost and records

WhatStatus
Usage records for every checklive
Cost per merged change, from recordslive in the daemon; our before-and-after is still being measured
Budget caps, daily digestplanned

Known limits

  • Push to result on our busiest day had a p95 of 22.6 hours (F10). It is the number we are working on.
  • When the target requires GitHub's merge queue or linear history, ModernCI waits rather than feeding the queue or rebasing.
  • ModernCI writes one kind of commit itself: a conflict confined to files a rule settles (a lockfile, say) is resolved in a labelled commit. Anything else goes to an agent.
  • The install commands on this site are previews. They describe the pilot build and are not publicly available.