@tessellate
Monorepo therapist. 400k LOC Nx workspace and five agents that all want to touch it.
Reputation is earned per category — these are narrow, evidence-backed badges, not one karma number.
Every session that touches a dependency ends with a 3,000-line package-lock.json diff, even when I asked for a one-line version bump. Turns out it runs `npm install` instead of `npm ci` and regenerates the lockfile against its own npm version.
Matches three weeks in the monorepo. The scoping discipline is the difference for me: Fable actually refuses out-of-scope edits and cites th…
on Fable 5 vs Opus 5 in Claude Code: early numbers and vibes · 2d ago
Commit it. The boundary is a property of the codebase, not of one engineer's setup. Local overrides go in settings.local.json, which stays g…
on Scope Claude Code to one package in a monorepo · 4d ago
Adjust the sed lines for whatever else is dangerous in your env.
on Worktree sessions inherit .env from the main checkout · 6d ago
The 'give it a decoy .env' approach deserves more attention — it's the only one that fixes the incentive instead of fighting it. Agent wants…
on Worktree sessions inherit .env from the main checkout · 1w ago
Fair, but the $9 wasn't the disaster — the disaster was my teammate losing an afternoon untangling the cross-package edits. Nobody invoices…
on Codex vs Claude Code for large monorepos · 1w ago
Monorepo amendment: the root CLAUDE.md should be nearly empty — mine is 12 lines of routing ('working in packages/api? read packages/api/CLA…
on What actually belongs in CLAUDE.md? · 2w ago
We tested both on a 200k+ LOC codebase. Claude Code navigates cross-package dependencies better; Codex scaffolds faster but wanders outside its assigned package.
In a 400k-line workspace, an unscoped agent burns half its context discovering packages it will never touch — then edits one it shouldn't. Run the agent from the package directory, deny writes outside it, and hand it the workspace-level commands it still needs.
The root file that keeps five agents from treating 40 packages as one big sandbox: affected-only commands, module boundaries with an owner column, and a hard rule about generated code.