All activity
yuqiang@JEPleft a comment
The idea for Agent-Blackbox came from a real 3 AM Slack message I never want to see again. Our multi-agent pipeline had just wiped the staging database. PM-agent said the requirement was clean. Coder-agent said it followed the spec perfectly. Verifier-agent said it never even received output. Four hours of grepping through thousands of log lines later, we still had no idea which agent actually...
Agent-Blackboxgit blame for AI agents — find who broke prod in 3s
🔍 Agent Blame-Finder - Cryptographic blackbox for multi-agent systems. Find which agent messed up in 3 seconds. JEP/JAC IETF reference implementation. - hjs-spec/Agent-Blackbox
Agent-Blackboxgit blame for AI agents — find who broke prod in 3s
yuqiang@JEPstarted a discussion
Agent-Blackbox: git blame for AI agents – find who broke prod in 3s
I built Agent-Blackbox after losing a week debugging an 8-agent pipeline failure. Every agent pointed fingers at the next one, and logs were useless for tracing the actual decision chain. What it does: - 📍 Traces failures to the exact agent and decision point - 🔗 Reconstructs the full task-based-on chain across agents - ✅ Uses cryptographically signed receipts (JEP / JAC) so evidence isn't just...
Zero-config MCP proxy that shows agents only the tools they actually need — 98% token reduction, no API keys. - hjs-spec/shutup-mcp
shutup-mcpZero-config MCP proxy that hides 99% of tools
yuqiang@JEPleft a comment
I built this after watching my Claude Code setup burn ~60,000 tokens just loading tool definitions from four MCP servers—before I even typed a prompt. The problem: MCP gives agents access to hundreds of tools, but every tool description eats context. Redis published data showing the same thing—167 tools, 42% selection accuracy, 60K tokens of overhead per session. In production, it can hit 150K+...
shutup-mcpZero-config MCP proxy that hides 99% of tools