Section 2 of 6

Concepts (12)

Twelve cross-cutting ideas — agent loops, memory compression, prompt caching, sandboxing — each followed across the 18 codebases. Patterns you'll see again and again, with a project-by-project breakdown of the variations.

Come here when you're trying to understand a technique and want to see how five different teams attacked it.

Start with Agent loop — the foundation everything else attaches to

Extended thinking

Models that reason before answering — handle the signatures correctly or break your cache.

2 projects 1 insights 3 variants

Agent loop

The skeleton every agent shares — read state, ask the model, parse, act, repeat — and how the wiring choices shape every other system around it.

12 projects 4 insights 4 variants

Prompt caching

Pay 10–50% of input cost on cached tokens. The art is choosing where the static-vs-dynamic boundary lives.

7 projects 3 insights 3 variants

Memory compression

Long sessions overflow the context window. The good implementations don't summarize — they enumerate what to keep.

5 projects 2 insights 4 variants

Multi-agent coordination

When one agent isn't enough — three questions to answer for any review pipeline, planner-executor flow, or critic loop.

7 projects 3 insights 3 variants

Mailbox & message-passing

How agents talk to each other when they share a process — and why most teams reach for Redis when a Python dict would do.

0 projects 1 insights 3 variants

Skills as markdown

Move agent expertise out of code and into versionable markdown. Domain experts contribute via PR; the loop almost never changes.

3 projects 1 insights 2 variants

Sandboxing

Limit what the tool layer can do regardless of what the agent intends. Docker, firewall, process limits, or all three.

3 projects 0 insights 4 variants

Guardrails

Layered defenses — prompt, schema, controller, sandbox — each catching a different class of failure. The story you tell auditors.

8 projects 2 insights 4 variants

Provider abstraction

Decouple agent code from a single LLM vendor. Three patterns observed; each pays a different tax.

8 projects 0 insights 3 variants

Streaming tool calls

Don't wait for the full response. Parse tool calls as they stream and dispatch the moment you have enough — sometimes earlier.

6 projects 1 insights 3 variants

Tool calling formats

How the agent and the model agree on 'I want to run this function.' Get this wrong and you're locked into one provider, can't stream cleanly, or pay for trailing hallucination.

11 projects 1 insights 4 variants