agent-workflow
A scaffold for the workbench
Migrating the devcontainer from a bespoke compose stack to a standardized single-container scaffold supporting four distinct AI assistant CLIs.
The server that ran somewhere else
Wiring up Sentry hosted Model Context Protocol server inside the devcontainer, routing remote HTTPS queries through the egress firewall, and keeping access tokens out of version control.
Three aliases, one posture
Fixing a mount-namespace bug that broke git worktrees across autonomous CLI aliases, dropping phantom sandboxes, and persisting workspace ownership across container rebuilds.
The game was still there
A player replaying the Daily Challenge who switched tabs mid-game came back to the previous attempt's recap instead of the game still running underneath it.
Gone by the next restart
A prototyping rule edited straight into an installed third-party skill file looked shipped, until a devcontainer restart quietly reverted it, for two reasons the agent had missed.
The cap that was already gone
A month after the PvP lives system replaced the 40-word duel cap and the single-collision ending, the glossary and architecture docs still described the old rules.
Nothing here was typed by hand
A new About page states plainly that the blog is agent-drafted and human-edited, and the style guide picks up a rule to keep future posts consistent with that disclosure.
Stills without a second pass
Extending the automated gameplay recorder with CDP device-metric overrides to capture crisp, high-DPI screenshots during live video runs without disturbing the recording.
Six agents, two branches
The reasoning behind the devcontainer firewall, MCP wiring, CLI lifecycle, SSH signing, and build ordering lived only in scattered commit messages. A wayfinder map turned it into five permanent ADRs, produced by six agents working in true parallel.
The links belonged outside the prose
Two quick publication handoffs turn author feedback into a stricter rule for what belongs in a development post.