roost-top 0.2__tar.gz

roost_top-0.2/.gitignore

@@ -0,0 +1,5 @@
+__pycache__/
+*.pyc
+.venv/
+dist/
+*.egg-info/

roost_top-0.2/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 George M. Howard
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

roost_top-0.2/PKG-INFO

@@ -0,0 +1,235 @@
+Metadata-Version: 2.4
+Name: roost-top
+Version: 0.2
+Summary: top for Claude Code -- live sessions, models, context, and the subagents they spawn
+Project-URL: Homepage, https://github.com/gmhoward9289-ops/roost
+Project-URL: Issues, https://github.com/gmhoward9289-ops/roost/issues
+Author-email: "George M. Howard" <dev@swamplink.com>
+License: MIT
+License-File: LICENSE
+Keywords: claude,claude-code,context,monitoring,top,tui
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Operating System :: MacOS :: MacOS X
+Classifier: Operating System :: Microsoft :: Windows
+Classifier: Operating System :: POSIX :: Linux
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.9
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: System :: Monitoring
+Requires-Python: >=3.9
+Description-Content-Type: text/markdown
+
+# roost
+
+[![ci](https://github.com/gmhoward9289-ops/roost/actions/workflows/ci.yml/badge.svg)](https://github.com/gmhoward9289-ops/roost/actions/workflows/ci.yml)
+
+`top` for Claude Code. Every live session, the model it is on, how much context
+it has burned — and, unlike anything else, **the subagents it spawned**.
+
+One file, no dependencies, Python 3.9+. Runs on macOS, Linux and Windows.
+
+```
+  WORKER    MODEL    CTX  IDLE    TASK
+NEAR LIMIT
+  demo-a1   opus-5   85%  12s     refactor the parser
+PARKED + COSTLY
+  demo-b2   opus-5   61%  4h10m   audit the build scripts
+WORKING NOW
+  demo-c3   fable-5  22%  3s      add integration tests
+STARTING
+  demo-d4   -        -    -
+
+QUIET (4)  demo-e5 . demo-f6 . demo-g7 . demo-h8
+
+8 worker(s)  |  fable-5, opus-5
+
+SUBAGENTS
+  STATE    AGENT       MODEL     CTX  IDLE   TASK
+  working  a812aca59f  opus-5    33%  2s     survey the config loaders
+  idle     adaffaba4b  sonnet-5  67%  1h22m  draft the migration notes
+
+  2 subagent(s), 1 working
+
+INFRA  ollama:11434 up qwen2.5-coder:14b (9.2 GB)   litellm:4000 up   openwebui:8080 DOWN
+```
+
+Sessions are grouped by what it costs to ignore them, not by size: `NEAR LIMIT`
+is about to stop working, `PARKED + COSTLY` bills its whole context on the next
+turn, and everything quiet collapses to a single line.
+
+## Install
+
+Homebrew (macOS and Linux):
+
+```bash
+brew install gmhoward9289-ops/tap/roost
+```
+
+Debian and Ubuntu — grab `roost_<version>_all.deb` from the
+[latest release](https://github.com/gmhoward9289-ops/roost/releases/latest):
+
+```bash
+sudo apt install ./roost_0.2_all.deb
+```
+
+There is no PPA and no apt repository; the `.deb` is a release artifact, and
+`apt install ./file.deb` resolves `python3` exactly as a repo install would.
+
+With pipx:
+
+```bash
+pipx install roost-top
+```
+
+PyPI holds the bare name `roost` in reserve — a prior project's name, retained
+after deletion — so the *package* is `roost-top`; the command it installs is
+plain `roost`. Installing straight from the repo skips the index entirely:
+
+```bash
+pipx install git+https://github.com/gmhoward9289-ops/roost
+```
+
+Or just take the file. It is one script, stdlib only, no dependencies:
+
+```bash
+curl -o roost https://raw.githubusercontent.com/gmhoward9289-ops/roost/main/roost.py
+chmod +x roost && ./roost
+```
+
+Windows: save it as `roost.py` and run it — `.PY` is in `PATHEXT`, so `roost.py`
+works from anywhere on `PATH`. There is no Windows package; the single file is
+the install.
+
+The man page (`man roost`) ships with the Homebrew and `.deb` installs. A pipx
+install puts it under the venv's own `share/man`, which is not on the default
+`MANPATH`; read it in place with
+`man "$(pipx environment --value PIPX_LOCAL_VENVS)/roost-top/share/man/man1/roost.1"`.
+
+## Use
+
+```
+roost              live, refreshing every second
+roost -w 5         slower refresh
+roost -1           one frame, then exit
+roost --json       joined records, for piping
+```
+
+While running: `space` refresh now · `a` advice panel · `s` subagents panel · `q` quit
+
+## Acting on a session
+
+> **Experimental.** Interactive mode carries an `EXPERIMENTAL` marker in the
+> top-right corner, and it means it — `x` ends a real process. Reading the
+> dashboard has never been the risky half.
+
+`j`/`k` (or the arrow keys) raise a cursor. Raising it expands the `QUIET`
+group, because a session idle for hours is exactly what a sweep is looking for
+and it is unreachable while collapsed.
+
+| key | does |
+| --- | --- |
+| `j` `k` `↓` `↑` | move the cursor |
+| `x` | stop the selected session — confirms first, and only `y` proceeds |
+| `y` | copy its sessionId, for `claude --resume <id>` |
+| `esc` | drop the cursor, re-collapse `QUIET` |
+
+`x` ends a process. It does not compact, save, or otherwise negotiate with the
+session — **there is no local control channel into a running Claude Code
+session**, so nothing gentler is available from outside it. On Unix that is a
+`SIGTERM` and the session exits on its own terms; on Windows there is no
+cross-process equivalent, so it is a `TerminateProcess` hard kill. Transcripts
+are written a turn at a time, so at most an in-flight turn is lost.
+
+Both keys act on the row object that was on screen when you pressed them, never
+on an index re-resolved afterwards. Rows reorder between frames as sessions go
+quiet, and an index that outlived its frame would eventually stop the wrong one.
+
+roost refuses to stop its own process or its parent — run it from inside the
+session it is pointed at and the cursor can land on the row that owns your
+terminal.
+
+Only one panel is open at a time: `a` and `s` flip between ADVICE and SUBAGENTS
+rather than stacking. With two dozen sessions on screen a stacked second panel
+lands below the bottom of the terminal, which is indistinguishable from the key
+not working. For the same reason the frame now says `... N more line(s) below`
+instead of quietly truncating.
+
+## What it logs
+
+Every session stopped with `x` appends one JSON line to
+`~/.claude/logs/roost.jsonl` — same shape and the same 5000-line cap as the hook
+logs beside it:
+
+```json
+{"ts":"2026-07-31T00:22:57-0400","action":"stop","ok":true,"host":"COOPER",
+ "name":"models-ca","pid":4321,"session_id":"abc-123","model":"claude-opus-5",
+ "ctx_tokens":484030,"idle_secs":92500}
+```
+
+The session's **task text is deliberately not recorded.** It is free-form prose
+out of a transcript, and an audit trail of what was stopped should not become a
+copy of what was being worked on.
+
+Because each record carries the context that session was holding, the log
+answers afterwards what a sweep actually reclaimed rather than just how many
+rows you closed. `--no-log` records nothing. A log that cannot be written is
+ignored rather than raised — losing the log is survivable, losing the display
+is not.
+
+## Why subagents are the interesting part
+
+Subagents have **no process of their own** — they run as sidechains inside the
+parent's process. Every pid-based view is structurally blind to them.
+
+They do each get a transcript, one directory deeper than the session transcripts:
+
+```
+~/.claude/projects/<slug>/<sessionId>/subagents/agent-<id>.jsonl
+```
+
+The short task description ("Scout source URLs") lives only in the *parent's*
+`toolUseResult`, keyed by `agentId`. roost joins the two, and falls back to the
+opening words of the subagent's own first message when the parent's record has
+scrolled out of reach.
+
+## Where the numbers come from
+
+Three local, read-only sources. Nothing is sent anywhere; there is no network
+call except a localhost probe of the infra ports.
+
+| source | gives |
+| --- | --- |
+| `~/.claude/sessions/<pid>.json` | live sessions: pid, sessionId, launch cwd, name |
+| `~/.claude/projects/*/<sid>.jsonl` | model in use, token usage |
+| `127.0.0.1` ports | ollama / litellm / openwebui |
+
+**Context** is the last assistant turn's `input_tokens + cache_read_input_tokens
++ cache_creation_input_tokens`. Cross-checked against an independent tool on the
+same session: 77% vs 77.29%.
+
+**The context window is inferred, not recorded.** Nothing on disk states which
+window a session opened with, and a session on the 1M window will read 480k+
+cache tokens in a single call — scoring that against 200k yields a nonsense
+"242%". roost picks the smallest standard tier the usage fits and prints it in
+the `WIN` column, so the assumption is visible rather than silent. If a new tier
+ships, `WINDOW_TIERS` is the one line to edit.
+
+## Caveats
+
+- It reads an **undocumented on-disk format** that can change without warning.
+  That is the whole foundation; treat breakage as expected, not exceptional.
+- The window inference above is a heuristic.
+- The `ADVICE` panel's thresholds are tuned to one person's usage. Read
+  `EXPENSIVE_TOKENS` and friends before trusting the advice.
+- Daily-driven on macOS and Windows. CI runs the suite and a smoke frame on
+  Linux, and it detects live sessions there — but nobody lives on it yet.
+  Field reports welcome.
+
+## License
+
+MIT — see [LICENSE](LICENSE). Contact: dev@swamplink.com
+
+Built in a Digital Swamp. From my swamp to yours.

roost_top-0.2/README.md

@@ -0,0 +1,211 @@
+# roost
+
+[![ci](https://github.com/gmhoward9289-ops/roost/actions/workflows/ci.yml/badge.svg)](https://github.com/gmhoward9289-ops/roost/actions/workflows/ci.yml)
+
+`top` for Claude Code. Every live session, the model it is on, how much context
+it has burned — and, unlike anything else, **the subagents it spawned**.
+
+One file, no dependencies, Python 3.9+. Runs on macOS, Linux and Windows.
+
+```
+  WORKER    MODEL    CTX  IDLE    TASK
+NEAR LIMIT
+  demo-a1   opus-5   85%  12s     refactor the parser
+PARKED + COSTLY
+  demo-b2   opus-5   61%  4h10m   audit the build scripts
+WORKING NOW
+  demo-c3   fable-5  22%  3s      add integration tests
+STARTING
+  demo-d4   -        -    -
+
+QUIET (4)  demo-e5 . demo-f6 . demo-g7 . demo-h8
+
+8 worker(s)  |  fable-5, opus-5
+
+SUBAGENTS
+  STATE    AGENT       MODEL     CTX  IDLE   TASK
+  working  a812aca59f  opus-5    33%  2s     survey the config loaders
+  idle     adaffaba4b  sonnet-5  67%  1h22m  draft the migration notes
+
+  2 subagent(s), 1 working
+
+INFRA  ollama:11434 up qwen2.5-coder:14b (9.2 GB)   litellm:4000 up   openwebui:8080 DOWN
+```
+
+Sessions are grouped by what it costs to ignore them, not by size: `NEAR LIMIT`
+is about to stop working, `PARKED + COSTLY` bills its whole context on the next
+turn, and everything quiet collapses to a single line.
+
+## Install
+
+Homebrew (macOS and Linux):
+
+```bash
+brew install gmhoward9289-ops/tap/roost
+```
+
+Debian and Ubuntu — grab `roost_<version>_all.deb` from the
+[latest release](https://github.com/gmhoward9289-ops/roost/releases/latest):
+
+```bash
+sudo apt install ./roost_0.2_all.deb
+```
+
+There is no PPA and no apt repository; the `.deb` is a release artifact, and
+`apt install ./file.deb` resolves `python3` exactly as a repo install would.
+
+With pipx:
+
+```bash
+pipx install roost-top
+```
+
+PyPI holds the bare name `roost` in reserve — a prior project's name, retained
+after deletion — so the *package* is `roost-top`; the command it installs is
+plain `roost`. Installing straight from the repo skips the index entirely:
+
+```bash
+pipx install git+https://github.com/gmhoward9289-ops/roost
+```
+
+Or just take the file. It is one script, stdlib only, no dependencies:
+
+```bash
+curl -o roost https://raw.githubusercontent.com/gmhoward9289-ops/roost/main/roost.py
+chmod +x roost && ./roost
+```
+
+Windows: save it as `roost.py` and run it — `.PY` is in `PATHEXT`, so `roost.py`
+works from anywhere on `PATH`. There is no Windows package; the single file is
+the install.
+
+The man page (`man roost`) ships with the Homebrew and `.deb` installs. A pipx
+install puts it under the venv's own `share/man`, which is not on the default
+`MANPATH`; read it in place with
+`man "$(pipx environment --value PIPX_LOCAL_VENVS)/roost-top/share/man/man1/roost.1"`.
+
+## Use
+
+```
+roost              live, refreshing every second
+roost -w 5         slower refresh
+roost -1           one frame, then exit
+roost --json       joined records, for piping
+```
+
+While running: `space` refresh now · `a` advice panel · `s` subagents panel · `q` quit
+
+## Acting on a session
+
+> **Experimental.** Interactive mode carries an `EXPERIMENTAL` marker in the
+> top-right corner, and it means it — `x` ends a real process. Reading the
+> dashboard has never been the risky half.
+
+`j`/`k` (or the arrow keys) raise a cursor. Raising it expands the `QUIET`
+group, because a session idle for hours is exactly what a sweep is looking for
+and it is unreachable while collapsed.
+
+| key | does |
+| --- | --- |
+| `j` `k` `↓` `↑` | move the cursor |
+| `x` | stop the selected session — confirms first, and only `y` proceeds |
+| `y` | copy its sessionId, for `claude --resume <id>` |
+| `esc` | drop the cursor, re-collapse `QUIET` |
+
+`x` ends a process. It does not compact, save, or otherwise negotiate with the
+session — **there is no local control channel into a running Claude Code
+session**, so nothing gentler is available from outside it. On Unix that is a
+`SIGTERM` and the session exits on its own terms; on Windows there is no
+cross-process equivalent, so it is a `TerminateProcess` hard kill. Transcripts
+are written a turn at a time, so at most an in-flight turn is lost.
+
+Both keys act on the row object that was on screen when you pressed them, never
+on an index re-resolved afterwards. Rows reorder between frames as sessions go
+quiet, and an index that outlived its frame would eventually stop the wrong one.
+
+roost refuses to stop its own process or its parent — run it from inside the
+session it is pointed at and the cursor can land on the row that owns your
+terminal.
+
+Only one panel is open at a time: `a` and `s` flip between ADVICE and SUBAGENTS
+rather than stacking. With two dozen sessions on screen a stacked second panel
+lands below the bottom of the terminal, which is indistinguishable from the key
+not working. For the same reason the frame now says `... N more line(s) below`
+instead of quietly truncating.
+
+## What it logs
+
+Every session stopped with `x` appends one JSON line to
+`~/.claude/logs/roost.jsonl` — same shape and the same 5000-line cap as the hook
+logs beside it:
+
+```json
+{"ts":"2026-07-31T00:22:57-0400","action":"stop","ok":true,"host":"COOPER",
+ "name":"models-ca","pid":4321,"session_id":"abc-123","model":"claude-opus-5",
+ "ctx_tokens":484030,"idle_secs":92500}
+```
+
+The session's **task text is deliberately not recorded.** It is free-form prose
+out of a transcript, and an audit trail of what was stopped should not become a
+copy of what was being worked on.
+
+Because each record carries the context that session was holding, the log
+answers afterwards what a sweep actually reclaimed rather than just how many
+rows you closed. `--no-log` records nothing. A log that cannot be written is
+ignored rather than raised — losing the log is survivable, losing the display
+is not.
+
+## Why subagents are the interesting part
+
+Subagents have **no process of their own** — they run as sidechains inside the
+parent's process. Every pid-based view is structurally blind to them.
+
+They do each get a transcript, one directory deeper than the session transcripts:
+
+```
+~/.claude/projects/<slug>/<sessionId>/subagents/agent-<id>.jsonl
+```
+
+The short task description ("Scout source URLs") lives only in the *parent's*
+`toolUseResult`, keyed by `agentId`. roost joins the two, and falls back to the
+opening words of the subagent's own first message when the parent's record has
+scrolled out of reach.
+
+## Where the numbers come from
+
+Three local, read-only sources. Nothing is sent anywhere; there is no network
+call except a localhost probe of the infra ports.
+
+| source | gives |
+| --- | --- |
+| `~/.claude/sessions/<pid>.json` | live sessions: pid, sessionId, launch cwd, name |
+| `~/.claude/projects/*/<sid>.jsonl` | model in use, token usage |
+| `127.0.0.1` ports | ollama / litellm / openwebui |
+
+**Context** is the last assistant turn's `input_tokens + cache_read_input_tokens
++ cache_creation_input_tokens`. Cross-checked against an independent tool on the
+same session: 77% vs 77.29%.
+
+**The context window is inferred, not recorded.** Nothing on disk states which
+window a session opened with, and a session on the 1M window will read 480k+
+cache tokens in a single call — scoring that against 200k yields a nonsense
+"242%". roost picks the smallest standard tier the usage fits and prints it in
+the `WIN` column, so the assumption is visible rather than silent. If a new tier
+ships, `WINDOW_TIERS` is the one line to edit.
+
+## Caveats
+
+- It reads an **undocumented on-disk format** that can change without warning.
+  That is the whole foundation; treat breakage as expected, not exceptional.
+- The window inference above is a heuristic.
+- The `ADVICE` panel's thresholds are tuned to one person's usage. Read
+  `EXPENSIVE_TOKENS` and friends before trusting the advice.
+- Daily-driven on macOS and Windows. CI runs the suite and a smoke frame on
+  Linux, and it detects live sessions there — but nobody lives on it yet.
+  Field reports welcome.
+
+## License
+
+MIT — see [LICENSE](LICENSE). Contact: dev@swamplink.com
+
+Built in a Digital Swamp. From my swamp to yours.

roost_top-0.2/packaging/build-deb.sh

@@ -0,0 +1,52 @@
+#!/bin/sh
+# Build a .deb for roost. Usage: packaging/build-deb.sh [version]
+#
+# Deliberately a plain dpkg-deb tree rather than a debian/ source package: roost
+# is one architecture-independent script with no build step and no dependencies
+# beyond python3 itself, so debhelper would add ceremony and no correctness.
+# The result is meant to be attached to a GitHub release and installed with
+#   sudo apt install ./roost_<version>_all.deb
+# which resolves python3 the same way an apt repo would. There is no PPA.
+set -eu
+
+ROOT=$(cd "$(dirname "$0")/.." && pwd)
+VERSION=${1:-$(sed -n 's/^__version__ = "\(.*\)"/\1/p' "$ROOT/roost.py")}
+[ -n "$VERSION" ] || { echo "could not determine version" >&2; exit 1; }
+
+BUILD=$(mktemp -d)
+trap 'rm -rf "$BUILD"' EXIT
+PKG="$BUILD/roost_${VERSION}_all"
+
+mkdir -p "$PKG/DEBIAN" "$PKG/usr/bin" "$PKG/usr/share/man/man1" \
+         "$PKG/usr/share/doc/roost"
+
+# Installed as `roost`, not `roost.py`: the shebang and the executable bit are
+# what make it a command, and the .py suffix only matters on Windows.
+install -m 0755 "$ROOT/roost.py" "$PKG/usr/bin/roost"
+gzip -9nc "$ROOT/roost.1" > "$PKG/usr/share/man/man1/roost.1.gz"
+chmod 0644 "$PKG/usr/share/man/man1/roost.1.gz"
+install -m 0644 "$ROOT/LICENSE" "$PKG/usr/share/doc/roost/copyright"
+
+cat > "$PKG/DEBIAN/control" <<EOF
+Package: roost
+Version: $VERSION
+Section: utils
+Priority: optional
+Architecture: all
+Depends: python3 (>= 3.9)
+Maintainer: George M. Howard <dev@swamplink.com>
+Homepage: https://github.com/gmhoward9289-ops/roost
+Description: top for Claude Code
+ Shows every live Claude Code session on the machine, the model each is
+ running, how much of its context window it has consumed, and the subagents
+ it has spawned -- which have no process of their own and are invisible to
+ any pid-based view.
+ .
+ Reads only local Claude Code state and probes localhost inference ports.
+ It sends nothing anywhere.
+EOF
+
+dpkg-deb --build --root-owner-group "$PKG" > /dev/null
+mkdir -p "$ROOT/dist"
+mv "$BUILD/roost_${VERSION}_all.deb" "$ROOT/dist/"
+echo "dist/roost_${VERSION}_all.deb"

roost_top-0.2/packaging/roost.rb

@@ -0,0 +1,38 @@
+# Homebrew formula for roost.
+#
+# This is the master copy; it is consumed by copying it to Formula/roost.rb in
+# the tap repo (gmhoward9289-ops/homebrew-tap), which is what `brew install`
+# reads. It lives here so the formula is versioned alongside the code it builds.
+#
+# homebrew-core is not an option yet -- it requires notability thresholds
+# (stars/forks/watchers) that this project has not met.
+#
+# After tagging a release, refresh the checksum with:
+#   curl -sL https://github.com/gmhoward9289-ops/roost/archive/refs/tags/v0.2.tar.gz | shasum -a 256
+class Roost < Formula
+  include Language::Python::Shebang
+
+  desc "top for Claude Code: live sessions, context use, and their subagents"
+  homepage "https://github.com/gmhoward9289-ops/roost"
+  url "https://github.com/gmhoward9289-ops/roost/archive/refs/tags/v0.2.tar.gz"
+  sha256 "d7c5c1fec7438a25c4c412ebf716c0e40a70513dcd3bc330cdb3df6c25592402"
+  license "MIT"
+
+  depends_on "python@3.13"
+
+  def install
+    bin.install "roost.py" => "roost"
+    # The shipped shebang is `/usr/bin/env python3`, which would resolve to
+    # whatever python happens to be first on PATH -- including a virtualenv the
+    # user activated for something else. Pin it to the formula's interpreter.
+    rewrite_shebang detected_python_shebang(use_python_from_path: false), bin/"roost"
+    man1.install "roost.1"
+  end
+
+  test do
+    assert_match "roost #{version}", shell_output("#{bin}/roost --version")
+    # -1 renders a frame and exits; with no Claude Code sessions present it
+    # still has to produce the empty-state line rather than fail.
+    assert_match(/roost|session/i, shell_output("#{bin}/roost -1 --no-color"))
+  end
+end

roost_top-0.2/pyproject.toml

@@ -0,0 +1,56 @@
+[build-system]
+requires = ["hatchling"]
+build-backend = "hatchling.build"
+
+[project]
+# PyPI holds the bare name "roost" in reserve (a prior project's name, retained
+# after deletion), so the distribution is roost-top. The command, the module,
+# the repo, the formula and the .deb are all still plain roost.
+name = "roost-top"
+dynamic = ["version"]
+description = "top for Claude Code -- live sessions, models, context, and the subagents they spawn"
+readme = "README.md"
+requires-python = ">=3.9"
+license = { text = "MIT" }
+authors = [{ name = "George M. Howard", email = "dev@swamplink.com" }]
+keywords = ["claude", "claude-code", "tui", "top", "monitoring", "context"]
+classifiers = [
+    "Development Status :: 3 - Alpha",
+    "Environment :: Console",
+    "Intended Audience :: Developers",
+    "License :: OSI Approved :: MIT License",
+    "Operating System :: MacOS :: MacOS X",
+    "Operating System :: Microsoft :: Windows",
+    "Operating System :: POSIX :: Linux",
+    "Programming Language :: Python :: 3",
+    "Programming Language :: Python :: 3.9",
+    "Programming Language :: Python :: 3.13",
+    "Topic :: System :: Monitoring",
+]
+# No dependencies, and there will not be any: roost has to run on whatever
+# Python is already on the box, including a bare system 3.9 on macOS.
+dependencies = []
+
+[project.urls]
+Homepage = "https://github.com/gmhoward9289-ops/roost"
+Issues = "https://github.com/gmhoward9289-ops/roost/issues"
+
+[project.scripts]
+roost = "roost:main"
+
+# One source of truth for the version: __version__ in roost.py, which is also
+# what `roost --version` prints and what the man page header carries.
+[tool.hatch.version]
+path = "roost.py"
+
+[tool.hatch.build.targets.wheel]
+only-include = ["roost.py"]
+
+# Installs to <prefix>/share/man/man1. pipx and venv installs put that outside
+# the default MANPATH, so `man roost` works after a system or Homebrew install
+# but may need MANPATH help inside a venv -- see README.
+[tool.hatch.build.targets.wheel.shared-data]
+"roost.1" = "share/man/man1/roost.1"
+
+[tool.hatch.build.targets.sdist]
+include = ["roost.py", "roost.1", "README.md", "LICENSE", "tests/", "packaging/"]