Here is a concise news summary based solely on the provided article body. The developer of NanoAgent, a local AI coding agent designed for terminal, desktop, editor, and CI workflows, integrated DeepSeek as a first-class provider, treating it as a real engineering integration rather than a cosmetic entry. This required DeepSeek to produce exact JSON arguments, file paths, patch text, and tool-call history for the runtime, as a small formatting mistake can stop the entire workflow. The integration added DeepSeek to provider selection, onboarding, and environment configuration, pointing to the base URL "https://api.deepseek.com/v1". However, once DeepSeek was running inside real tool-heavy workflows, the developer identified a more interesting problem: tool calls are fragile. For example, a model might call a tool to read a file using `{ "path": "README.md" }` or write a file using `{ "path": "docs/intro.md", "content": "#`.