#agentic-ai
Every post tagged "agentic-ai".
27 posts · showing 21–27
-
Do You Need an Agent Framework? Write the 40-Line Loop First
The agent loop is shorter than the quickstart for the framework that hides it. Write it once — then you can tell which framework features you actually need and which ones you'd be adopting on faith.
-
Green Evals, Broken Production: The Frozen Fixture Problem
An eval suite built on recorded tool responses stops testing your agent and starts testing a museum. Here are three cheap detectors for fixture rot — and the rule for when a case should call the live tool instead.
-
Who Decides the Agent Is Done? Three Stop Conditions, and Why "The Model Said So" Isn't One
Most first agents end their loop when the model stops calling tools — which means the model, not you, decides what "done" means. Here are the three stop conditions a real loop needs, and the twenty lines that turn a silent wrong answer into another iteration.
-
What Should Your Agent Forget? Give Every Memory an Expiry Rule
Agent memory systems have a write verb and a recall verb, but no verb for "stop believing this." Here's how to decide at write time what makes each memory stop being true — and why expiry should downgrade a fact rather than delete it.
-
How Should a Team Review a Tool Description Diff? Treat It Like a Schema Migration
A six-word edit to a tool description is a behavior change with no compiler to catch it. Borrowing the review checklist teams already use for schema migrations turns an unreviewable prose diff into something you can actually approve.
-
When Memory Contradicts the Tool Call, Which One Does the Agent Believe?
An agent had the live billing data and a three-week-old memory in the same context window, and answered from the memory. The reason isn't retrieval — it's how prompts are assembled, and there are three specific fixes.
-
What Crosses the Handoff: Transcript, Summary, or Contract?
A triage agent spends eleven tool calls finding the bug, then hands off. Passing the transcript ships its dead ends; passing a summary strips the uncertainty. What a typed handoff contract gets right — and the one field teams always forget.