Coordination layer for AI coding agents, built on Git
Loom Version control for many hands moving at once. Git is the filesystem; Loom is air traffic control. You point two Claude Code sessions at your repo.
- ▪Loom Version control for many hands moving at once.
- ▪Git is the filesystem; Loom is air traffic control.
- ▪You point two Claude Code sessions at your repo.
Hacker News (AI / LLM) files mainly under ai. We currently carry 2,225 of its stories.
Opening excerpt (first ~120 words) tap to expand
Loom Version control for many hands moving at once. Git is the filesystem; Loom is air traffic control. Two timelines Without Loom. You point two Claude Code sessions at your repo. Agent A spends 40 minutes and ~200k tokens rewriting src/auth/ around a new session model. Agent B, told to "clean up the login flow", touches the same files with the opposite assumption. Neither knows the other exists — git has nowhere to put that knowledge. B finishes last, so B's edits win; A's work is silently gone from the tree. The test suite goes red at commit time, and you spend the evening (and another few hundred thousand tokens) having a third session diagnose a breakage that is really two AIs' half-rewrites interleaved.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Hacker News - Newest: ""AI" "LLM"".