git404hub

what is whatbroke fr?

arthi-arumugam-git/whatbroke — explained in plain English

Analysis updated 2026-05-18

1TypeScriptAudience · developerComplexity · 3/5Setup · moderate

tl;dr

A command-line tool that compares what an AI agent did across two runs to see exactly which tool calls, costs, and outputs changed when you tweak your setup.

vibe map

mindmap
  root((repo))
    What it does
      Compares agent runs
      Shows broken tool calls
      Reports cost and latency
    Inputs
      JSONL trace files
      OpenTelemetry imports
      Langfuse imports
    Outputs
      Breaking findings
      Changed findings
      Info findings
    Tech stack
      TypeScript
      Node SDK wrappers
      Proxy recorder
    Use cases
      Catch silent failures
      Track cost changes
      Automate CI testing
    Audience
      Developers

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

what do people make with this?

VIBE 1

Catch silent failures where an agent says a task is done but skips the actual tool call.

VIBE 2

Track how costs and response times shift when you change an AI model or prompt.

VIBE 3

Automate agent regression testing in CI to fail builds when behavior breaks.

VIBE 4

Compare agent traces multiple times to tell real bugs from random AI inconsistency.

what's the stack?

TypeScriptNode.jsCLIOpenTelemetryLangfuseLangsmithOpenAI SDKAnthropic SDK

how it stacks up fr

arthi-arumugam-git/whatbroke0xkinno/neuralvault0xmayurrr/ai-contractauditor
Stars111
LanguageTypeScriptTypeScriptTypeScript
Setup difficultymoderatehardeasy
Complexity3/54/52/5
Audiencedeveloperdeveloperdeveloper

Figures from each repo's GitHub metadata at analysis time.

how do i run it?

Difficulty · moderate time til it works · 30min

Requires recording AI agent traces as JSONL files using a proxy, SDK wrappers, or importing from existing observability tools.

The license for this repository is not specified in the provided information.

in plain english

whatbroke is a command-line tool that compares what an AI agent did across two runs. When you change a model, prompt, or framework version, the tool shows exactly which tool calls disappeared, which arguments shifted, where costs and latency moved, and which outputs changed. The core problem it addresses is that text-based diffs miss behavioral changes. An agent might say "your subscription is cancelled" while silently skipping the cancellation call entirely. The words look correct, but the behavior broke. The workflow is straightforward. Record a trace of your agent doing its job, which is a plain JSONL file with one event per line. Change something about your setup. Record a new trace. Run a diff command to compare them. whatbroke aligns the runs and reports findings at three severity levels: breaking (like dropped tool calls or failures), changed (like argument drift or cost increases), and info (like model swaps or token swings). The exit code is 1 when something breaking appears, so you can plug it directly into continuous integration pipelines. AI agents are naturally inconsistent, so a single before-and-after comparison can blame your change for noise the agent was already producing. whatbroke handles this by letting you record the same scenario multiple times with suffixes like "refund-flow#1, refund-flow#2". It compares every baseline sample against every new sample and attaches a rate to each finding. Issues that also appear between baseline samples get demoted to flaky, since the agent behaved that way before your change. To get traces, you can use a proxy that requires zero code changes. Point your agent at a local address and every call gets recorded. There are also SDK wrappers for OpenAI and Anthropic in Node, plus manual methods for other languages. If you already record traces through OpenTelemetry, Langfuse, or Langsmith, an import command converts those into whatbroke's format. The full README is longer than what was shown.

prompts (copy fr)

prompt 1
Set up whatbroke to record two traces of my Node AI agent so I can compare what changed when I updated my system prompt.
prompt 2
Write a CI step that runs whatbroke to compare a baseline agent trace against a new one and fails the build if it finds breaking issues.
prompt 3
Import my existing Langfuse traces into whatbroke so I can diff agent behavior without re-recording everything.
prompt 4
Help me record the same agent scenario five times with whatbroke suffixes to filter out flaky agent behavior and find real regressions.

Frequently asked questions

what is whatbroke fr?

A command-line tool that compares what an AI agent did across two runs to see exactly which tool calls, costs, and outputs changed when you tweak your setup.

What language is whatbroke written in?

Mainly TypeScript. The stack also includes TypeScript, Node.js, CLI.

What license does whatbroke use?

The license for this repository is not specified in the provided information.

How hard is whatbroke to set up?

Setup difficulty is rated moderate, with roughly 30min to a first successful run.

Who is whatbroke for?

Mainly developer.

peek the repo → explain another one

This repo across BitVibe Labs

double-check against the repo, no cap.