{
  "id": 12283117,
  "title": "Two things nobody was watching",
  "url": "https://urgent.news/2026/10/06/two-things-nobody-was-watching",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-10-06T02:34:25.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/someone_somewhere_05cad9e/two-things-nobody-was-watching-5b2e"
  },
  "original_language": "en",
  "account": "Two overlooked issues impacted the functionality of OpenSpec Workbench in recent updates. The first issue involved a cleanup process that prematurely stopped, leaving behind a large file – a half-finished removal that left behind a 54-megabyte download of Visual Studio Code under the repository's packages. The second issue was the failure to read a crucial number from DeepSeek's CLI, which reported usage without providing any details on spending or token limits.\n\nOpenSpec Workbench addressed these problems with two changes. Firstly, the meaning of \"ours\" in the cleanup rule was modified. Now, a shell named after a change already known by the repository, without its own .git directory, would be cleared, regardless of its contents. This change also resulted in the periodic sweep cleaning up such shells on every pass, and notifying the user of what was removed and what was still pending.\n\nSecondly, the DeepSeek CLI's usage data was found to be arriving but not being read. This information, sent over the Agent Client Protocol, indicated the amount of model window tokens being used in a session. By implementing this change, OpenSpec Workbench now provides real-time context on resource usage, enabling users to manage their spending more effectively.\n\nIn summary, OpenSpec Workbench resolved two long-standing issues: a lingering cleanup process and the inadequacy of tracking DeepSeek CLI usage. These fixes enhance the tool's reliability and provide better insights into resource allocation.",
  "summary": "First published on openspec-ui.dev . OpenSpec Workbench's whole pitch is watching an agent while it works. Two small fixes this week are about the product not watching itself closely enough - one where cleanup quietly stopped, one where a number was arriving the whole time and nothing was reading it. The leftover that survived being asked twice A working directory is removed in two steps: git…",
  "key_points": [
    "Cleanup process stopped prematurely, leaving 54 MB Visual Studio Code file",
    "DeepSeek CLI failed to read crucial usage number",
    "OpenSpec Workbench fixed both issues with new changes"
  ],
  "editors_take": "OpenSpec Workbench's fixes for overlooked issues enhance its reliability and provide users with better insights into resource allocation, enabling more effective spending management.",
  "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."
}