Feed
Re-review Elixir PR orchestration recovery fixes
Takeaway: I'd ask upfront for the agent to specifically diff the fix commit against the original findings list rather than re-deriving the whole call graph from scratch — that would have gotten to the require_green_checks gap faster.
Static review Elixir/TypeScript changes in pi-symphony
Takeaway: I'd next time just tell it upfront that I'm aware of the time and to skip any commentary on that and get straight to the review.
Make Pi Session HUD context colours configurable and warn sooner for 1M-token models
Takeaway: Next time I'd specify upfront exactly which display elements (bar, token count, percentage, denominator) should and shouldn't carry the warning colour, since I ended up correcting that piecemeal over four separate prompts.
Wire pi-nes sessions upload to Hugging Face via pi-share-hf
Takeaway: Next time I'd mention upfront that we already have the newer 'hf' CLI installed instead of the legacy 'huggingface-cli', since that saved a chunk of back-and-forth discovering and patching pi-share-hf to support both.
Review docs-focused PR for pi-nes README updates
Takeaway: Next time I'd ask it upfront to check both the CLI's install modes (global vs project-local) and lockfile consistency whenever a PR touches package.json, since those are exactly the kind of details that only show up after digging into the CLI's own docs.
Speed up NES emulator rendering pipeline (TypeScript + Rust)
Takeaway: Next time I'd give the agent something more concrete to profile against, since it couldn't watch my screen recording and had to guess where the slowdown was from code alone.
Audit and clean up TODOs in vendored nes-rust emulator (Rust)
Takeaway: Next time I'd start by asking the agent to check TODOs critically against actual hardware behavior rather than just listing them, since a chunk of the upstream TODOs turned out to be wrong or stale.
Explain pi-nes architecture audit findings
Takeaway: I'd ask for this same full trace-and-explain pass again since it worked well as-is — pointing the agent at the audit doc plus 'read everything referenced' got a thorough, evidence-backed walkthrough without needing any correction.
Build automated test suite for pi NES emulator extension
Takeaway: Next time I'd start by telling the agent explicitly which ROMs I actually care about and that I want tests tied to real gameplay symptoms (freezes, missing sprites) rather than emulator-accuracy test suites like blargg/nestest.
Audit pi-nes codebase, plan refactor, and diagnose Mario freeze regression
Takeaway: Next time I'd start by asking directly for a refactor plan scoped to 'simple, non-duplicative, not excessively defensive' rather than getting a generic audit first and then having to talk it back down to size.
Research CRT/NTSC filtering for pi-nes terminal NES emulator
Takeaway: Next time I'd ask upfront for both the research and a concrete GitHub issue in one go, since the agent handled the investigation (codebase read, web research on Blargg's nes_ntsc and TetaNES) well without any correction needed from me.
Review PR fixing Ghostty black-screen in NES image mode (TypeScript)
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.
Scope a minimal fix for Alt+Enter slash-command queueing in pi coding agent
Takeaway: Next time I'd open by naming the target diff size and the exact commands in scope up front, since that framing is what pushed the agent toward a maintainer-friendly two-commit split instead of one big change.
Review necessity of post-turn queue feature commits
Takeaway: Next time I'd ask for the necessity review and the overengineering critique as two separate passes so the agent doesn't just enumerate 'needed' files but actually flags bloat.
Review streaming/compaction queue changes in coding-agent for overengineering
Takeaway: Next time I'd ask for this review earlier, before the diff got this large, so overengineered bits like the queue state machine could be caught before they were fully built out.
Trace deprecated npm dependency warnings in Pi monorepo
Takeaway: I'd start by asking the agent to check npm install logs and overrides directly instead of grepping package-lock.json first — that's what actually found the root cause.