colineonset

Public

Onset: version control where nobody waits and nothing gets lost. The on command, its core and onset-server.

CodeIssuesChange requestsActionsDiscussionsCommitsBranchesReleasesSearchContributorsCompare

Code Issues Change requests Actions Discussions Commits Branches Releases Search Contributors Compare

Upstream

Docs Pricing Support Changelog

coline/onset

colineonset

Public

Onset: version control where nobody waits and nothing gets lost. The on command, its core and onset-server.

CodeIssuesChange requestsActionsDiscussionsCommitsBranchesReleasesSearchContributorsCompare

Code Issues Change requests Actions Discussions Commits Branches Releases Search Contributors Compare

perf(onset): merging an agent's edits skips what main changed elsewhere

Radin committed …

Author: Radin · radin@coline.appOct 31, 2026 at 23:34
Committer: Radin · radin@coline.appOct 31, 2026 at 23:34
Parents: ebfe1d131ea5

perf(onset): merging an agent's edits skips what main changed elsewhere

Landing on a busy project merged each change against everything main had
changed since its base: the whole diff, for rename following, and every
folder on the way rebuilt through three string maps. Now:

- Renames are followed only when the change removes a file, or a file it
  edits is gone from main; otherwise main's changes aren't listed.
- Folders merge in one pass over their sorted entries, copying names only
  where both sides changed one.
- lookup finds entries by halves instead of decoding the folder.
- An object's ID is hashed once (it was hashed again when stored), and
  objects loaded from storage keep the ID they were checked against.

A test merges 3,000 random trees both ways and gets the same trees,
conflicts and notes. Land bench (256 agents, Node): 1.09 to 0.73 ms CPU a
land.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

5 files changed+170−10

← Back to history