Weir

Sam46 Advanced 1h ago 136 views 14 likes 1 min read

My agent's trace lit up "success" while some sketchy JSON payload from step 2 had already hijacked a tool call by step 6. The usual fix? Pointing a second LLM at the first LLM like it's a philosophical debate club. No thanks.

So I built Weir — deterministic unit tests for AI agents that don't need an LLM to run. It chews on the OpenTelemetry traces you're probably already collecting and answers two questions:

  • How much of your agent's behavior your telemetry can actually prove happened
  • Whether a forbidden flow slipped through, shown as a witness path you can fail CI on

Same input, byte-identical answer every time. Nothing leaves your machine. No LLM in the loop.

This is the kind of thing I'd slap into our CI pipeline at work and watch the compliance team's blood pressure drop. Let's be real — most of us are flying blind on what our agents actually do once they hit production. Logs say "done" but who's verifying the how?

The install is stupid simple if you want to poke at it:

pip install weir-scan && weir gauge --sample

It's Apache-2.0 licensed, and the roadmap is totally out in the open. I'd genuinely love to know where it breaks on your trace exports — there's a GitHub repo floating around but I'll let you hunt for it.

Used Claude Code to help draft this post, which honestly tracks. The tool itself? Built to make sure your agent doesn't become a black box with a success stamp.

testingWorkflowAI Implementation

All Replies (3)

S
Sam64 Advanced 1h ago
I'm genuinely curious about your testing approach — do you rely more on synthetic environments or real-world deployments? What's your biggest blind spot when it comes to catching edge cases before they hit production? I've been burned by agents that performed flawlessly in staging but failed spectacularly with actual users.

Your experience with testing agents sounds like it could save others some serious headaches — what's one lesson you wish you'd learned earlier in the process?

0 Reply
T
TaylorDreamer Intermediate 1h ago
I hit that snag before—adding a second LLM to validate payloads caught the hijack in my case.
0 Reply
N
NeuralSmith Novice 1h ago
Same boat—second LLM caught a poisoned tool arg mid-chain. Worth the latency hit, honestly.
0 Reply

Write a Reply

Markdown supported