How Will the MCP Ecosystem Affect Developer Tools?
Technical trends, engineering practices, and an independent developer perspective on MCP and AI Agents.
AI Agent、MCP、工具调用、多 Agent 协作
This collection features articles and community discussions in the Agent 工程 space, focusing on real-world engineering scenarios, tool selection, practical paths, and risk boundaries.
The page is continuously updated and serves as a learning roadmap, technology selection reference, and technical review entry point.
Technical trends, engineering practices, and an independent developer perspective on MCP and AI Agents.
Human confirmation is not a simple "continue?" button. This article explains the action summary, scope, expiry, permission re-check, and audit fields that an Agent write-operation approval should contain, to prevent confirmation from being misused.
After the initial request times out, the tool may still be running server-side; issuing a cancel does not mean the side effects have stopped. This article establishes an operation identity, polling watermark, cancellation race handling, and a single terminal-state acceptance point for a single long-running tool call.
Agent tasks for research, procurement, and batch data processing often span minutes or even days. This article explains how to persist task snapshots, restore checkpoints, handle timeouts, and avoid duplicating external side effects after restarts.
A single Agent can confidently go off course on complex tasks. This article explains three multi-Agent orchestration patterns (supervisor, hierarchical, and handoff), implements a "supervisor + specialists" system with LangGraph's state graph, and covers the state, loop, and human-intervention engineering needed for production.
As memory grows, you can't save tokens by overwriting old summaries. This article designs fixed input snapshots, derived lineage, key-fact fidelity tests, invalidation propagation, and reversible switching.
Deleting one row in the primary table won't clear vectors, summaries, caches, or restored backups. This article uses a deletion state machine, generational tombstones, derived lineage, and end-to-end canary verification to truly forget.
User preferences, project decisions, and roles all change. This article separates facts using valid time and recorded time, explicitly handles supersession, late-arriving, and concurrent conflicts, and avoids last-writer-wins producing incorrect memory.
Preferences and facts a model extracts from a conversation cannot become long-term memory directly. This article designs candidate proposals, deterministic validation, deduplicated commits, revocation lineage, and a contamination-rate gate.
Passing offline evaluation does not mean an agent is reliable in production. This article designs online success rate, human takeover, rejection quality, tool recovery, and cost metrics to help teams use layered observation to judge whether a version deserves more traffic.
Multi-step agent errors often occur in intermediate tool results and state changes. This article explains how to save desensitized trajectories, build deterministic replays, handle external dependencies, and turn production incidents into reliable regression tests.
A production agent cannot be just a while loop. This article uses an explicit state machine to split planning, tool calls, waiting for approval, recovery, and terminal states, and provides transition constraints, persistence fields, and testing methods.