Deep-dive guides on AI agents, agent orchestration, MCP, and developer tooling.
9 posts found

Prompt engineering asked what to say to the model. Context engineering asks what the model actually needs to see, in what order, and what gets thrown away to make room for it: the discipline agents forced into existence.

Codex, Copilot's cloud agent, Cursor's cloud agents, Jules, Devin, and cloud Claude Code sessions all follow the same five-stage pipeline. The differences that matter are in sandbox scope, repo access, and where the real trust boundary sits.

Sampling is the MCP primitive that inverts the relationship, letting a server without its own model borrow the client's LLM through a two-gate approval flow. Here is how it works, and why the 2026-07-28 spec revision deprecated it.

In agent systems, instructions live across four surfaces (system prompt, tool schemas, tool results, and few-shot text), not one. Most prompt debugging still only looks at the first.

Vector similarity search answers what text is topically related, but long-running agents need to know what is true right now. Conflating the two is why agents keep resurrecting overturned decisions.
One email when a new post goes up. No other mail; unsubscribe in one click.
We store your email only to send new posts. See the privacy policy.