Urgent.News

What's breaking now, across thousands of outlets.

Tech

Two things nobody was watching

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…

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.

OpenSpec 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.

Secondly, 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.

In 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.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

The silent retry bug killing ASP.NET Core reliability (and how idempotency keys save you)

The Silent Retry Bug: Why Your Resilient .NET System Is Actually Fragile If you’ve spent any time working with distributed systems in C# and ASP.NET Core, you know the drill: network calls fail…

  • Distributed systems in ASP.NET Core experience network issues like timeouts.
  • Conventional retry policies from Polly can cause data inconsistency.
  • Idempotency Keys prevent duplicate-state problem by ensuring state-changing requests are unique.

Build an Admin Dashboard in React

An admin dashboard is mostly three things: a row of numbers that matter, a chart that shows the trend, and a table of recent activity.

  • Admin dashboard built with React using KPI cards, revenue chart, and recent activity table
  • Each KPI card displays label, value, change, and trend with color-coded indicators
  • Revenue chart shows monthly online and store revenue with automatic legend generation

Log Collector & Dashboard for Elixir.

A Simple Log Collector for Elixir I’ve just released a small log collection stack for Elixir applications. The idea is simple: store application logs in ClickHouse and provide a lightweight dashboard…

  • Elixir developer creates log collection system
  • Uses ClickHouse for fast log storage and querying
  • Dashboard offers search and filtering features

More from Tuesday 6 October →