Stack · 5 sessions

jq sessions with coding agents

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

Pi·infra·CLI & tooling·library1d

Install and scope pi extension go-to-bed from agent-stuff repo

Takeaway: Next time I'd ask upfront to install only the specific extension rather than the whole package, since the agent installed everything first and then had to go back and filter settings.json down to just go-to-bed.

1m0interventionsTypeScript pi Node.js0 cmt

Pi·debug·CLI & tooling·library2d

Fix agent stall from stripped tool schemas on continuation calls

Takeaway: Next time I'd start the prompt with the concrete symptom and my suspicion of the recent stream-proxy change, since that's exactly where the bug was.

50m1interventionTypeScript anthropic api Vite0 cmt

Pi·docs·CLI & tooling·library2d

Inventory monorepo packages and versions

Takeaway: I'd start by just asking for a full package inventory with versions and descriptions right away instead of doing it in two steps.

1m0interventionsNode.js jq Bash0 cmt

Pi·docs·CLI & tooling·library8h

Audit package sync status across 0xKobold monorepo

Takeaway: I'd just ask for the full package table with names, versions, and sync status up front instead of doing it in two passes.

2m0interventionsGit Bash jq0 cmt

Pi·docs·CLI & tooling·library1d

Audit package sync status across 0xKobold monorepo

Takeaway: I'd probably just ask for both the sync status and the full package inventory in one go next time, since I ended up asking for them as two separate follow-ups.

1m0interventionsNode.js npm jq0 cmt