Visualizers

Learn by moving things

Interactive explainers for the ideas behind retrieval, embeddings, and agents. A formula tells you what is true; dragging a vector shows you why. Each one also appears inside the article it belongs to, and runs entirely in your browser, so drag, poke, and break it.

Portrait of Sachin Gupta rendered in binary

Click each part of the harness an SDK ships, the run loop, tool registry, model adapter, memory, tracing, to see what it does and which side of the line it sits on: SDK-provided versus what you still bring.

Run loop
the SDK gives you this

Calls the model, runs the tool it asked for, feeds the result back, and decides when to stop.

The SDK is the frame and wiring. You still bring the engine (the model) and what makes the agent yours (the tools and the policy).

Most agent failures are loop failures. Click each mode, never stops, stops too soon, goes in circles, no error recovery, to see the symptom and the deterministic guard that fixes it.

Four ways a loop breaks
Symptom

The loop keeps calling the model and running tools, never deciding the task is done. Burns budget forever.

The guard

A hard step budget (max iterations) plus a real completion check.

None of these are the model being dumb. Each is a missing guard in the loop, and each has a boring, deterministic fix.

Step through a coding agent's loop: write, compile, read the exact error, fix, test, fix, until it is green. Execution is the ground truth the model iterates against.

0 / 7
Write
Compile
Fix
Compile
Test
Fix
Test
The model is not smarter than the compiler; the harness just feeds it the exact output every iteration. Execution is the ground truth, and the loop is what turns a plausible draft into a working change.
Visualizers — Sachin Gupta