Why can't Cowork just write code? (asking for our PMs)
Half my company lives in Cowork now. Every week someone asks me why it won't touch the repo.
@ottoline
Tech lead, 12-person team, mixed agent adoption. I care about what scales past one enthusiast.
Reputation is earned per category — these are narrow, evidence-backed badges, not one karma number.
Half my company lives in Cowork now. Every week someone asks me why it won't touch the repo.
The agent worked for two hours and produced something plausible everywhere. Rubber-stamping is negligence, line-by-line is a full day. What's the actual workflow?
We rolled the hook out to the whole team via a checked-in .claude/settings.json. One gotcha: jq isn't installed on everyone's machine, so th…
on Claude Code keeps rewriting package-lock.json · 2d ago
Team angle: pick one surface as the team default even though they're interchangeable, because your runbooks and screenshots and onboarding d…
on Claude Code beginners: CLI, desktop app, web, or IDE extension? · 3d ago
For team adoption the review UI point is underweighted. I can get any of my 12 engineers to review a Cursor diff. Getting them to review 2,0…
on Claude Code vs Cursor for multi-file refactors · 1w ago
We adopted this for the team last quarter. One process note: we require the branch name in the agent's task prompt ('you are working on fix-…
on Safe parallel agents with Git worktrees · 2w ago
That matches what we saw the one time it happened here (hotel wifi, flaky network). Filed it as a distinct issue on the forum and linked thi…
on Cursor background agents create conflicting branches · 3w ago
Our new grad ships like a mid-level and I have no idea what he actually knows. The apprenticeship loop assumed you learn by writing — that assumption just quietly broke.
Run two background agents on related tasks and you get branches that both rename the same symbol, plus an occasional shared-working-tree stomp when an agent falls back from its isolated clone. Merging their PRs is a coin flip of conflicts.
The organizational failure behind the technical one: nobody owns a shared AGENTS.md, so it only ever grows. Every incident adds a section, n…
on Oversized AGENTS.md gets silently truncated · 2mo ago