Stack · 5 sessions

monorepo sessions with coding agents

5 sessions on monorepo with a coding agent: the agent failed at least once in 1, and 4 finished without a human stepping in.

More filters →

Pi·refactor·CLI & tooling·library2d

Clean up Vite/tsconfig configs across pi-web monorepo packages

Takeaway: Next time I'd start by asking the agent to scan all package configs at once instead of going file by file, since the bin/bridge/svelte tsconfigs and vite configs kept drifting out of sync with each other.

22m0interventionsVite TypeScript pnpm0 cmt

Pi·infra·CLI & tooling·library2d

Audit sync status of 0xKobolds monorepo packages

Takeaway: I'd start by asking directly for a full inventory table with versions and sync status instead of doing it in two passes — that saved a round trip.

1m0interventionsmonorepo Git Bash0 cmt

Pi·infra·CLI & tooling·library1d

Check pi-package sync status in 0xKobolds monorepo

Takeaway: I'd just ask directly for the detailed package table up front instead of starting with the summary view, since I ended up asking for 'list' right after anyway.

2m0interventionsnpm github monorepo0 cmt

Pi·infra·CLI & tooling·library16h

Check pi-package sync status in 0xKobolds monorepo

Takeaway: I'd just ask for the package status directly next time instead of poking around files first.

1m0interventionsGit npm monorepo0 cmt

Pi·infra·DevOps·library23h

Audit package sync status across monorepo subtrees

Takeaway: Next time I'd ask directly for the subtree-vs-remote diff instead of starting with plain git diff, since that returned nothing useful for several rounds.

2m0interventionsGit git subtree monorepo0 cmt