#agent-sdk
Every post tagged "agent-sdk".
7 posts · showing 1–7
-
Adopt the Agent Framework or Write the Loop Yourself? Count the Defaults You'd Have to Override
Framework feature lists don't settle this choice. What settles it is how many of the framework's hidden defaults your agent would have to fight, and a short audit on one real task tells you before you commit.
-
Before You Adopt an Agent Framework, Try to Break Its Loop: Four Escape Hatches You'll Need by Week Three
Time-to-demo is the one framework criterion that stops mattering the moment you ship. Four seams to test in an afternoon — and the production incident each one predicts.
-
Can You See the Raw Messages? The Question That Sorts Agent Frameworks
Every agent framework demos well. The one that survives your first 2am incident is the one that will hand you the exact bytes it sent to the model — and let you change them before they go.
-
Framework or Raw SDK? The Test Is Whether You Can Print the Exact Prompt
The framework debate is usually argued on taste. There's a faster test: build a two-tool agent and try to dump the exact request it sends on turn four. How hard that is predicts your next six months of debugging.
-
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.
-
Build or Buy the Eval Harness? What Each Choice Locks In
Teams buy an eval platform and keep their own scripts anyway. The reason is deterministic replay — it hooks into your dispatch layer, which is the one part no vendor can own.
-
Framework or Plain Loop? Four Questions That Actually Decide It
The core agent loop is under a hundred lines — that's never what a framework saves you. Four situational questions decide it, and the one about 3am debugging should carry the most weight.