... still there. Now the problem is not the original issue anymore. The problem is that you no longer know whether the tool is looking at reality. This happens a lot in developer environments. A local server was stopped. A watcher process exited. A project issue was fixed. A repository was refreshed. A warning no longer applies. But the UI still acts like the old state is current. For tools that monitor developer machines, freshness matters as much as detection ... ... enough to surface a problem once. The product also needs to understand when that problem has changed, disappeared, or been resolved. That is something we have been improving in Room Service. Smart Advisor, Projects, Dev Ports, Build Watchers

... reasons. Sometimes the reason is obvious. You are compiling something large. Running Docker. Building an app. You know what is happening. But often, the expensive process is just sitting there quietly in the background. A watcher keeps running. A local server never stopped. A build tool keeps rebuilding. A forgotten project is still doing work. Activity Monitor can show the process. But it rarely explains the developer context around it. Which project is this tied to? Did I start this ... ... this expected? Is this process still useful? For developers, high CPU usage is rarely just a process. It is usually connected to a project, local server, build tool, or workflow that was left behind. That idea became Build Watchers

... Room Service 0.9.0 moves the product further in a direction I care a lot about: helping developers understand and manage what is happening on their machines. The biggest addition is Build Watcher monitoring. Project-backed watch and build tools can now surface in Room Service even when they are not attached to a local port. That means CPU and RAM-heavy processes from things like frontend watchers

... limited version on the App Store or go direct and build the product properly I chose direct distribution. That decision changed a lot. What got better: full control over what the app can access features like Dev Ports, Build Watchers, deeper system visibility just work faster iteration without review cycles more flexibility in how the product evolves What got harder: distribution becomes manual no built-in discovery like the App Store payments, licensing, updates all become your problem you have ...

... really struggle with cleaning. They struggle with understanding what s happening on their machines. A few things became very clear over time: 1. Cleaning is not the problem, visibility is. Most issues come from things running in the background: watchers, build tools, local servers. They don t crash your system. They slowly degrade it. 2. One-click clean is not trusted. People don t want magic. They want to see what s happening before touching anything. 3. Developer storage ... ... workflow. 4. Most tools ignore runtime problems. CPU, RAM, active processes, local servers That s where things actually break, but cleaners rarely touch this layer. 5. The product started changing because of this. Features like Dev Ports, Build Watchers