Introducing `lane` — a CLI to manage: 🔹copy-on-write (CoW) worktrees 🔸 durable, in-project memories Plain worktrees throw away every ignored file that made your checkout fast: node_modules, target/, .env files, etc. So you reinstall and rebuild, even though the caches are already on disk. lane clones them by reference instead. lane also manages project memory. Attach a note to a file and a symbol: $ lane note add src/auth.rs -a 'fn verify' 'must stay constant-time' # or $ git commit -am "fix(auth): prevent timing attach \ Why: src/auth.rs#fn verify | early return leaks token length" When `fn verify` changes, the note is flagged. It stays flagged until someone resolves it. A confidently wrong note is worse than no note. Lanes are cheap enough to run several at once, so parallel agents each get their own tree and their own notes. Every note is a separate file, so multiple agents can annotate the same function without a conflict. lane never calls a model. GitHub: github.com/lukeed/lane Docs: lane.lukeed.com/

We are launching Workers Cache, a regionally tiered cache that sits directly in front of your Worker entrypoints. Infinitely composable, configured via standard HTTP headers. cfl.re/44IVyfI

Bro wants to kill the IDE to make it harder to see the slop code.