felix9527

3 ms·

1.
by felix9527 7mo ago
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 is gone, the only record is whatever the agent chose to sum
2.
by felix9527 7mo ago
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 actually happened. Hard to judge quality without seeing the p
3.
by felix9527 7mo ago
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 unbounded. Rules are a blacklis
4.
by felix9527 7mo ago
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. "Just review everything" is not realistic at that rat
5.
by felix9527 7mo ago
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." Compliance teams (SOC 2, EU AI Act
6.
by felix9527 7mo ago
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 appends it to an RFC 6962 M
7.
by felix9527 7mo ago
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 vendor-controlled, and "undo" only works if you catc
8.
by felix9527 7mo ago
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 transparency log style). The two concerns are complementary: &