How do you find out what an agent doesn’t know?
Peter Richens
9 mins November 12, 2026

How do you find out what an agent doesn’t know?

How do you identify gaps in an AI agent’s knowledge when you don’t have ground truth about what it should have known? We built a gap finder that combines investigation traces, statistical testing, and live environment exploration to identify missing knowledge and prioritize the gaps worth fixing.

Read more

How we made evals 100× cheaper with multi-agent architecture

Dan Siwiec
11 mins November 3, 2026

When our evals became too expensive and slow to run, we rearchitected our single investigation agent into a team of ~40 loosely coupled agents. While there are some tradeoffs, it’s made evals run 5x faster for cents on the dollar, and we can experiment much more rapidly to evolve our product.

How we made evals 100× cheaper with multi-agent architecture

Jev the Decider: JIT for Agents

Michael Saah
6 mins September 25, 2026

Constraining action spaces for faster, cheaper agents

Jev the Decider: JIT for Agents

Roll for initiative: our week at AI Engineer World’s Fair 2026

Cleric
6 mins September 1, 2026

Everyone knows agents can write code, but the open question is what happens after the code is merged.

Roll for initiative: our week at AI Engineer World’s Fair 2026

Our LLM judge scored worse than chance until we made it compare

Peter Richens
25 mins July 23, 2026

We rank an agent’s investigation traces by comparing them in pairs and turning the wins into an Elo score. Grading each trace on its own scored worse than chance. Comparison made the ranking work, and it catches regressions our other evals miss.

Our LLM judge scored worse than chance until we made it compare

How we verify Cleric’s production fixes

Peter Richens
18 mins July 22, 2026

A correct diagnosis isn’t the same as a fixed problem. We built a verifier that checks Cleric’s fixes against the best ground truth available: production itself.

How we verify Cleric’s production fixes

You’re renting your institutional knowledge

Shahram Anver
12 mins June 7, 2026

Most AI agents rent knowledge back through forward-deployed engineers. The ones worth buying compound verified memory in systems you own.

You’re renting your institutional knowledge

How Cleric uses Tailscale to securely automate software operations

Michael Saah
7 mins May 1, 2026

An AI SRE has to access the same private resources a human engineer would. We use Tailscale to get there.

How Cleric uses Tailscale to securely automate software operations

Stop Reviewing Agent Output. Start Reviewing Agent Decisions.

Shahram Anver
7 mins April 17, 2026

When agents can produce anything, the bottleneck shifts from code to judgment. You manage that by reading the decisions, not the outputs.

Stop Reviewing Agent Output. Start Reviewing Agent Decisions.

Why Your AI SRE Needs Memory

Shahram Anver
8 mins March 19, 2026

Investigation logic is becoming a commodity. What won’t commoditize is operational memory: the ability to capture and persist engineering judgment.

Why Your AI SRE Needs Memory

Hooks Won’t Secure Your AI Agent

Michael Saah
8 mins January 30, 2026

AI Agents require strict network controls in order to keep the data they handle secure.

Hooks Won’t Secure 
 Your AI Agent

Subscribe to The Tavern

Cleric’s newsletter, featuring new articles on AI SRE and lessons from building Cleric.

By subscribing you agree to our Privacy Policy .