10 sessions on pi-tui with a coding agent: the agent failed at least once in 3, and 4 finished without a human stepping in.
Takeaway: Next time I'd point straight at extensions/pi-traceline/index.ts and docs/design-language.md instead of letting it grep the whole repo first, since that's where the emphasis logic and tone table actually lived.
Takeaway: Next time I'd put the design contract itself up front in the first prompt — asking for a written design-language doc before any code — since that's what let the later passes move fast once agreed.
Takeaway: I'd open with the concrete repro and screenshot up front rather than asking 'why' first — the JSONL forensics dig was the right instinct but could've started immediately.
Takeaway: I'd start by pointing the agent straight at the diff and the specific files touched (renderer.ts, index.ts, config.test.ts) instead of letting it explore the whole codebase from scratch.
Takeaway: Next time I'd start by checking upstream/issues for the bug number before spending an hour building a consolidated fix, since the maintainer landed a one-line getExpandedText() fallback for the same bug while I was still refactoring.
Takeaway: I got sidetracked asking the agent about its own thinking blocks and context files instead of pushing forward on the actual todo app design, so next time I'd hold off on meta-questions until after getting a concrete plan or prototype out of it.
Takeaway: Next time I'd start by just playing the game myself before asking for a review, since most of the real bugs (unwinnable speed, glitchy edge bounces, AI difficulty swings) only showed up once I actually tried to beat Pi.
Takeaway: I'd start by asking directly whether Kitty's z-index image layering was available, since that's what ultimately worked — a lot of early exploration time went into overlay/theme APIs that were dead ends.
Takeaway: Next time I'd start the first prompt with the actual failure mode (freeze on huge folders) plus a constraint like 'don't break full-repo navigation with diff counts', since that shaped the whole design conversation later anyway.
Takeaway: Next time I'd specify upfront that the opponent should be labeled 'Pi' (mixed case) and that command names might change mid-session, since renaming from paddle-ball to /ping caused a few redundant edits.