#tutorial
Every post tagged "tutorial".
92 posts · showing 51–60
-
Getting an Agent to Say How Sure It Is
Ask a model how confident it is and you get a plausible number that doesn't move with difficulty. Five signals that actually correlate with being right — and the calibration check that tells you if yours is noise.
-
Few-Shot Examples: When They Help an Agent and When They Hurt
Two or three similar examples is the worst case — enough to teach a template, not enough to convey the range. And the example nobody includes is the one where the right answer is to decline.
-
Latency Budgets for Agents: Where the Seconds Actually Go
"Try a faster model" addresses maybe a third of the time in a typical run. Split the twelve seconds five ways and the real culprits — turn count and tool latency — are usually the ones nobody measured.
-
Audit Logs That Survive an Incident
Audit logs get designed for compliance and used during incidents. One question — who caused what, to whom, under what authority — decides every field, and most logs can't answer the authority part.
-
Bisecting a Bad Run: Finding the Change That Broke It
It worked last week. Six things could have changed, and they vary independently — so bisect across the dimensions first, then within one. And diff the raw arrays for what's missing, not what's different.
-
Delegating to a Human as If They Were an Agent
Same interface, same contract, same result shape — a person is a worker with hours of latency and much better context. Which makes suspendable runs the prerequisite, not a nice-to-have.
-
The File System as a Tool: Underrated Agent Infrastructure
Four hundred thousand rows won't fit in a context window; a path and a preview cost nothing. A scoped directory solves large results, durable state, and reviewable artifacts at once — if you resolve paths correctly.
-
State Machines for Agents in Regulated Flows
When doing steps out of order is a compliance failure regardless of outcome, a model-decided control flow is the wrong shape. Put the ordering in code, the conversation in the agent, and scope the tools per state.
-
Give the Agent a Scratchpad: External Working Memory
Three small tools stop the context from being the only place findings can live. Compaction stops being lossy, long runs stop growing, and you get a readable record instead of a forty-turn transcript.
-
Multi-Tenancy for Agent Products: The Boundaries That Must Hold
Data, memory, context, and capacity — four boundaries, and two of them are agent-specific enough that no existing multi-tenancy checklist mentions them. Few-shot examples harvested from production are a leak.