agent-usage-manager 0.2.3__tar.gz → 0.2.4__tar.gz

{agent_usage_manager-0.2.3 → agent_usage_manager-0.2.4}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: agent-usage-manager
-Version: 0.2.3
+Version: 0.2.4
 Summary: htop for AI agents — liveness, CPU/mem/GPU usage, and a kill switch for headless agents (openclaw, hermes, ollama, vllm, claude-code).
 Project-URL: Homepage, https://github.com/minglong51/agent-usage-manager
 Project-URL: Repository, https://github.com/minglong51/agent-usage-manager
@@ -161,6 +161,15 @@ This is the important part — a web page that can kill processes needs guardrai
 
 ## Limits & known issues
 
+- **Matching is a heuristic and it over-matches.** An agent's identity usually
+  lives in its arguments (`node .../bin/codex`), and a GUI agent's real name is
+  its `.app` bundle (Kiro launches a binary called `Electron`) — so the match
+  target is the executable basename plus the first few args plus the bundle
+  name. The cost is that anything living inside an agent's `.app` (updaters,
+  crash handlers, helpers) and any process that names an agent in its first
+  args (`tmux attach -t workspace-claude`) can be misclassified as that agent.
+  `ignore:` is the escape hatch. The bundled list is not exhaustive and can't
+  be — every new agent ships new helpers under its own name.
 - **GPU column is NVIDIA-only.** Per-process GPU memory comes from
   `nvidia-smi --query-compute-apps` — NVIDIA compute processes (CUDA), in
   practice on Linux. AMD/Intel GPUs aren't read, graphics-only workloads don't
@@ -365,6 +374,15 @@ SIGTERM/SIGKILL on POSIX and TerminateProcess on Windows.
 
 ## Release notes
 
+### 0.2.4 — stop reporting non-agents
+
+- `ignore:` now covers Sparkle's `Autoupdate`/`Updater` (Codex.app's equivalent of
+  Squirrel's ShipIt), the "Codex for Chrome" extension host, and `tmux attach`
+  clients — a session named `workspace-claude` matched the claude pattern via the
+  `-t` argument.
+- Dogfooded against `ps` on a live 10-agent fleet: 22 rows → 17, with all six
+  removals confirmed as not agents and every real agent retained.
+
 ### 0.2.3 — startup fixes
 
 - The browser now opens once the port actually accepts, instead of on a fixed

{agent_usage_manager-0.2.3 → agent_usage_manager-0.2.4}/README.md

@@ -142,6 +142,15 @@ This is the important part — a web page that can kill processes needs guardrai
 
 ## Limits & known issues
 
+- **Matching is a heuristic and it over-matches.** An agent's identity usually
+  lives in its arguments (`node .../bin/codex`), and a GUI agent's real name is
+  its `.app` bundle (Kiro launches a binary called `Electron`) — so the match
+  target is the executable basename plus the first few args plus the bundle
+  name. The cost is that anything living inside an agent's `.app` (updaters,
+  crash handlers, helpers) and any process that names an agent in its first
+  args (`tmux attach -t workspace-claude`) can be misclassified as that agent.
+  `ignore:` is the escape hatch. The bundled list is not exhaustive and can't
+  be — every new agent ships new helpers under its own name.
 - **GPU column is NVIDIA-only.** Per-process GPU memory comes from
   `nvidia-smi --query-compute-apps` — NVIDIA compute processes (CUDA), in
   practice on Linux. AMD/Intel GPUs aren't read, graphics-only workloads don't
@@ -346,6 +355,15 @@ SIGTERM/SIGKILL on POSIX and TerminateProcess on Windows.
 
 ## Release notes
 
+### 0.2.4 — stop reporting non-agents
+
+- `ignore:` now covers Sparkle's `Autoupdate`/`Updater` (Codex.app's equivalent of
+  Squirrel's ShipIt), the "Codex for Chrome" extension host, and `tmux attach`
+  clients — a session named `workspace-claude` matched the claude pattern via the
+  `-t` argument.
+- Dogfooded against `ps` on a live 10-agent fleet: 22 rows → 17, with all six
+  removals confirmed as not agents and every real agent retained.
+
 ### 0.2.3 — startup fixes
 
 - The browser now opens once the port actually accepts, instead of on a fixed

{agent_usage_manager-0.2.3 → agent_usage_manager-0.2.4}/agent_usage_manager/agents.yaml

@@ -57,6 +57,10 @@ ignore:
   - crashpad      # chrome_crashpad_handler — the bundle's crash reporter
   - shipit        # Squirrel.framework auto-updater
   - kiro-cli-term # Kiro's integrated-terminal shells (zsh), not the agent
+  - autoupdate    # Sparkle's Autoupdate helper — Codex.app's ShipIt equivalent
+  - updater       # Sparkle's Updater.app; argv[1] is the app path, so it matches
+  - for chrome    # "Codex for Chrome" extension host, not the agent
+  - tmux attach   # tmux clients: `attach -t <session>` carries the agent's name
 
 # Optional: per-instance labels from tmux session names. A fleet of identical
 # agents (e.g. several claude-code bots, one per tmux session bot-*) all hit

{agent_usage_manager-0.2.3 → agent_usage_manager-0.2.4}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "agent-usage-manager"
-version = "0.2.3"
+version = "0.2.4"
 description = "htop for AI agents — liveness, CPU/mem/GPU usage, and a kill switch for headless agents (openclaw, hermes, ollama, vllm, claude-code)."
 readme = "README.md"
 license = { text = "MIT" }

{agent_usage_manager-0.2.3 → agent_usage_manager-0.2.4}/uv.lock

@@ -8,7 +8,7 @@ resolution-markers = [
 
 [[package]]
 name = "agent-usage-manager"
-version = "0.2.3"
+version = "0.2.4"
 source = { editable = "." }
 dependencies = [
     { name = "fastapi", version = "0.128.8", source = { registry = "https://pypi.org/simple" }, marker = "python_full_version < '3.10'" },