tools i use for evals and agent testing
things that showed up in my own repos or in how i talk about the work. logos link out; chips link to project pages on this site.
12 tools, 5 projects
tracing
Langfusethe trace store openissue reads from. read-only on purpose. a seeded trace proves the api path works, not that anyone had the incident.
used inopenissue
OpenTelemetry + OpenInferenceif your spans are otel, openissue reads them without an adapter. the reference lab has to pass on fixtures and on otel, or it doesn't count. openinference is the span shape i used in the lab fixtures.
used inopenissue
LangSmithsimtest can turn a langsmith trace into a seed file, so a bad run becomes a test case instead of a screenshot.
used insimtest
evals
eve evalsscaffolded the local research brain with it and fought the node version first. the smoke evals run on a deterministic shim so ci doesn't need a key. the live ones need a real model and a judge.
used inpocket / probable
testing
Vitestwhere the boring checks live. the brain has a test that it refuses a live trade, which matters more than anything in the ui.
pytestdefault for the python side: simtest, gauntlet, and the sim engine.
used insimtestsolana agent safety
GitHub Actionssimtest runs on every pr as an eval gate. i added a branch that's supposed to fail, so i know the red actually shows up.
used insimtest
sims
Surfpoollocal solana validator i run exploit transactions against. gauntlet has a mock mode, but the real runs go through surfpool.
used insolana agent safety
models / infra
OpenAI APIin openissue the model only explains what the detector found. structured output, store off, and it can't touch the counts. also showed up in gauntlet and sim-engine model runs.
used inopenissuesolana agent safety
Anthropic APIsecond provider in openissue, same contract as the first. also the anthropic path in the local research brain.
used inopenissuepocket / probable
Vercel AI SDKwired into the local research brain via the anthropic provider. i'm not claiming live gateway judge evals here.
used inpocket / probable
OpenRouterhow we ran twelve models for beacon without twelve accounts. lossfunk gave us the credits.
used inbeacon
older stuff
W&B Weavemy first time wrapping a function so every call got logged. small 2024 notebook, but that's where traces started for me.
Giskardran a hallucination scan on a rag model in late 2023. tutorial-level, be honest about that.
Guardrails AIearly output validation experiment in 2023. a custom validator and a rail spec, nothing i ship on now.