#intermediate
Every post tagged "intermediate".
222 posts · showing 191–200
-
Run, Session, or Global? Scoping Agent Memory Correctly
Too-small a scope produces a visible annoyance; too-large produces a silent wrong answer. One question assigns any fact correctly, and one rule keeps multi-tenant reads from becoming an incident.
-
MCP: What a Standard Tool Protocol Changes, and What It Doesn't
Portable integrations and runtime discovery are real wins. Tool design, selection accuracy, permissions, and untrusted content are exactly as hard as before — and easy connection quietly makes two of them worse.
-
The Escalation Path Is Part of the Design
An agent with no defined way to stop will improvise one, and its improvisation is a confident answer. Escalation deserves a tool, a destination, and a metric — and one field that stops the human starting over.
-
The Demo-to-Production Gap Is an Evaluation Gap
Demos answer "can it?" Deployments ask "how often, across everything real users send, when the tools misbehave?" Five variants of your demo scenario will tell you more than the demo did.
-
Cost Attribution: Finding Which Feature Is Eating Your Token Budget
Agent spend is dominated by a tail of expensive runs, so every averaged chart hides the cause. Five tags on each model call, one table of your twenty priciest runs, and the mystery usually resolves in an afternoon.
-
Vector Database or Postgres? Choosing Storage for Agent Memory
Most agent memory reads are filtered similarity or plain structured lookup — relational workloads wearing an embedding. Write down your ten most common retrievals before you add a second database.
-
The On-Call Agent: What It Should and Shouldn't Touch During an Incident
An incident is when your system is least understood — a poor moment for an autonomous actor, an excellent one for an autonomous investigator. The line between them is read access and write access.
-
Specialist Agents or Specialist Prompts? The Cheaper Half of Multi-Agent
A separate agent buys separate context, separate permissions, and separate lifecycles. It does not buy expertise — that's what prompts are for, and they cost nothing and lose nothing at the boundary.
-
Where You Put Things in the Context Changes the Answer
Same instructions, same documents, different results — because the constraint sat in the middle of a long array. Two ordering rules, one of which also decides whether your prompt cache ever hits.
-
The Agent That Read Page 1 of 40: Pagination in Tool Design
It reported three overdue invoices. There were sixty-one. The tool worked as documented — which is exactly why this bug is so common and so quiet.