Glean 拾遗
Recent picks

2picks · chronological

11-13

Two Agents, One Record: Git-Style Branches Instead of Row Locks

Two agents doing read-modify-write on shared memory lose updates silently: because an agent writes back the whole record it read, a stale save can reset a field another agent just changed, and both report success. The post walks through the three usual fixes—single writer, row locks or optimistic version checks, last-write-wins—and argues all fall short for multi-step tasks spanning several records, since none produces a reviewable diff or an audit trail. It then demos Omnigraph, an MIT-licensed graph database in Rust with a Git-style model: each agent commits to its own branch, merges compare against the merge base, and a stale branch is rejected with divergent_update instead of publishing. The walkthrough uses Claude Code and Codex, covering @key stable IDs, --snapshot reads of old commits, and a Cedar policy with per-agent tokens returning HTTP 403 for writes to main. Useful for anyone building multi-agent shared state, though the headline's 1,000-agent scale is never shown—the demo is one developer and two agents.

x.com · 11 min · Agent Infrastructure · Agent-Memory · Multi-Agent
09-01

A Git-compatible VCS with a commit-centric workflow

Jujutsu (jj) is an open-source version control system written in Rust. It aims to make the everyday VCS workflow simpler while staying compatible with the Git ecosystem. The key design is a working copy that is automatically committed: every file change becomes a snapshot you can revisit or revert. An operation log records every state mutation, providing robust undo/redo. Conflicts are first-class data objects instead of inline text markers, making merges and rebases more predictable. jj can be used in existing Git repositories or as a standalone VCS, so it supports incremental adoption. This project is relevant for engineers exploring modern VCS design, Git workflows, and high-quality Rust-based tooling.

github.com · 2 min · CLI · Developer Tools · Rust