Tag: ai-agents

A step-by-step checklist for lifting a hand-rolled Anthropic tool-calling loop onto a standalone MCP server. The tool bodies move almost verbatim; what changes is where the schema comes from, how results are wrapped, and how errors cross the process boundary.

A step-by-step checklist for moving an existing LangChain agent off inline @tool functions onto a standalone MCP server that any client can call. Covers extracting tools into FastMCP, re-wiring the agent with langchain-mcp-adapters MultiServerMCPClient, the sync-to-async switch, transports, and the gotchas that bite mid-cutover.

GitHub Copilot's modernize-dotnet agent shipped as a portable plugin on July 9, 2026. It now runs in VS Code, the Copilot CLI, and on GitHub, with an assess to plan to execute workflow whose artifacts get committed to your repo for review.

A step-by-step checklist for moving a .NET app off the raw OpenAI 2.12 SDK onto the provider-neutral Microsoft.Extensions.AI 10.7 IChatClient. Covers the AsIChatClient bridge, the CompleteChatAsync-to-GetResponseAsync rewrite, streaming, tool calling, DI registration, and the gotchas that bite mid-cutover.

VS Code 1.128 (July 8, 2026) lets one Claude agent-host session hold several parallel chats, each with its own history, title, and model. Here is what chat.agentHost.enabled actually unlocks and how the quick-chat and BYOK pieces fit.

Claude Sonnet 5 (claude-sonnet-5) shipped June 30, 2026 and now backs the 'sonnet' alias in Claude Code. Its new tokenizer emits about 30% more tokens for the same text, so cost estimates and max_tokens limits tuned for Sonnet 4.6 need a recount.

A step-by-step checklist for moving an existing Semantic Kernel 1.77 .NET app to Microsoft Agent Framework 1.13. Covers the Kernel-to-AIAgent rewrite, plugins-to-tools, thread-to-session, the KernelFunction compatibility bridge, DI changes, and the gotchas that bite mid-cutover.

Claude Code v2.1.198 (July 1, 2026) flips subagents to background execution by default, so the main agent keeps working while they run, and background agents that touch code now auto-commit, push, and open a draft PR when they finish.

Both let one agent spawn isolated workers from a Markdown file, but Claude Code nests five levels deep with per-agent tool allowlists and worktree isolation, while Cursor keeps it to two levels with a single readonly switch and reads Claude's format for free. Pick by where your agents run, not by brand.

Build a skill to change how Claude works, a subagent to protect your context window, and an MCP server to reach a system Claude cannot otherwise touch. They solve three different problems, not one. Here is the decision, the mechanics, and the config for each.