Viewing profile — felix9527

We instrument production services with traces and structured logging. AI agents that touch the same codebase? Most people have zero visibility once the session ends. The scrollback…

The study only looks at what lands in the PR. In my experience a single prompt can trigger 20+ tool calls, most of them reads and greps. The final diff is a tiny fraction of what a…

The article treats this as AI being stupid, but it's a design category error. Spotify is applying rules ("don't repeat artists," "mix genres") to a system whose behavior space is u…

Been running Claude Code with hooks recording every tool call for two weeks. ~25k actions across 116 sessions. The thing that surprised me: 24 tool calls per prompt on average. "Ju…

Exactly. The moment an agent touches prod, "we logged it" isn't enough — you need "here's the cryptographic proof of what happened, and you can verify it without trusting us." Comp…

Sure — it's at https://github.com/PunkGo/punkgo-jack It hooks into PostToolUse, PreToolUse, SessionStart/End, and UserPromptSubmit. Each event gets submitted to a local kernel that…

The core problem this article surfaces is forensic: once the agent session ends, the evidence is whatever the vendor chose to log. Terminal scrollback is lossy, session logs are ve…

Interesting approach to the PreToolUse side. I've been building on the other end — PostToolUse hooks that commit every tool call to an append-only Merkle tree (RFC 6962 transparenc…