{
  "id": 11087595,
  "title": "A new agent, and nothing else moved",
  "url": "https://urgent.news/2026/10/01/a-new-agent-and-nothing-else-moved",
  "topic": "ai",
  "section": "AI",
  "published": "2026-10-01T02:40:01.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/someone_somewhere_05cad9e/a-new-agent-and-nothing-else-moved-5hca"
  },
  "original_language": "en",
  "account": "On the day of the article's publication, DeepSeek, a new agent, entered the scene and seamlessly integrated using the Agent Client Protocol (ACP). This new addition was verified through the introduction of a single file, deepseek-acp.ts, which implements the AgentAdapter interface shared by other agents. The agent was added to the registry, verified through the default allowlist, and recognized by both the standalone application and VS Code extension due to their shared registry reading process.\n\nDeepSeek is now one of ten agents, with five speaking ACP, alongside Claude, Copilot, Codex, and Gemini. Upon activation, the agent ran using the default DeepSeek-V4-Flash model, which was made available for selection. However, no further options for selecting a model were provided at the time. The agent exhibited two noteworthy behaviors: on Node 22.11 running under Volta, it exited with a code of 0 without providing any output, and on Node 24.18, it completed its process.\n\nTo ensure compatibility with the host environment, the agent reports the Node version it was run on, prompting users to update if they are using an outdated version. The agent does not report any usage information, which means it contributes no spending to the ceiling set for usage limits. The agent's behavior is guided by the instructions provided, executing them in order without deviation, and indicating completion of each step before moving to the next.\n\nAdding DeepSeek as an agent adhered strictly to the design architecture, with the implementation completed within a short time frame. The full implementation details, including the agent's code, can be found in the repository at github.com/VeryComplexAndLongName/OpenSpec-UI. The underlying architecture is detailed in the article \"One core, two hosts.\" Notable findings from the implementation include the agent's behavior on specific Node versions and its lack of usage reporting, which has implications for resource allocation and spending ceilings. The complete details of the agent's integration and functionality are available in the repository and related documentation.",
  "summary": "First published on openspec-ui.dev . The last article argued that a shared core is what keeps a VS Code extension and a web app from drifting apart. Two days after it went out, a new agent arrived, and it is as good a test of that argument as any: DeepSeek, over the Agent Client Protocol, requested by the owner and added the same day. What it took One new file, deepseek-acp.ts , implementing the…",
  "key_points": [
    "DeepSeek, a new agent, integrated using Agent Client Protocol",
    "Agent added to registry and recognized by applications",
    "DeepSeek-V4-Flash model used for agent activation"
  ],
  "editors_take": "The addition of DeepSeek as an agent reinforces the system's design architecture and expands its capabilities, while also highlighting implications for resource allocation and usage tracking.",
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}