All posts

· The LVCS team · 1 min read

Never click “Update branch” again

Your team and your agents edit the same code at the same time, and it just merges. No rebase. No merge queue. No little yellow dot. LVCS runs on your laptop or your cloud VM, peer to peer, so the next time githubstatus.com turns orange, you'll find out from Twitter like everyone else. Oh, and it's free. No seats, no runner minutes, no server bill.

~/auth-service · src/auth/token.rsillustrative session
  1. use crate::key::Key;
  2. pub fn validate_token(raw: &str, key: &Key) -> Option<Claims> {
  3. let claims: Claims = decode(raw, key).ok()?;
  4. (claims.exp + LEEWAY_SECS > now()).then_some(claims)
  5. }
  6. pub fn refresh(token: &Token, key: &Key) -> String {
  7. encode(&token.renewed(LEEWAY_SECS), key)
  8. }
  1. agent-aannouncelines 3–6: “return the claims from validate_token”others are on the file, so it waits before it edits
  2. agent-bhold“mid-change on the expiry check”agent-a’s edit pauses; a thread opens on lines 3–6
  3. agent-beditmain · line 5finishes its own edit first
  4. agent-banswer“expiry check is in. all yours.”the hold is released
  5. agent-aeditmain · validate_tokenlive on main: everyone on the file sees it as it’s typed
  6. mayaeditmain · refreshsame file, other lines, same moment: both just merge
  7. runnerattestcargo test -p auth · passtoken.rs changed, so its action runs; the rest are reused
  8. cichannelci → 3f9a0cenough runners signed the same result
  9. mayacheckpointlvcs checkpoint 3f9a0ca git commit of exactly the revision ci passed
peers 3 · server noneagent-a may edit src/auth/** · no expiryci 3f9a0c

The pull request loop wasn't built for agents.

Push. Wait. “Some checks haven't completed yet.” Fail. “This branch is out-of-date with the base branch.” Update branch. Wait. Run it all again. You've done the dance. Your agents do it all day, in parallel, at full price.

1 in 5
of CI hours went to re-running checks after merging main into a branch.
8 in 10
of those merges conflicted. Mostly on one generated file.
12 min
median wait for the first reply to a review comment.

One company, one week. Some reruns earn their keep. Others are a very expensive space heater.

Your agents are in line too. Behind you.

We pulled GitHub's own Actions records (we're thorough like that) for 544 merged pull requests from Copilot, Claude Code, Codex, and Devin across 114 open-source repos, plus 496 from people in the same repos. The 90 days to October 27, 2026.

25 min
median an agent's pull request spends waiting on CI. One in ten waits over 6 hours.
1 in 7
of their CI runs re-test a merge from main. Same as people.
2.3×
longer CI waits for Copilot's pull requests than people's in the same repos, mostly for a human to click “Approve and run.” The future is here, and it needs a babysitter.

Agents wait about as long as people do. They just never clock out, never complain, and never get bored of it. Merged pull requests only, so this is the optimistic version.

Next: CI that doesn't check githubstatus.com first, and how LVCS works.

Saved to mainNovember 1, 2026 · The LVCS team