Monitoring
What your AI work costs, which AI processes are running, what your tabs talk to, every git worktree on this computer, and what fills the disk.
⌥⌘U opens Monitoring. Everything here is computed on your machine; nothing is uploaded.
In-app browsers#
Every in-app browser open in the window, one row each: the workspace and terminal it belongs to (or the plugin), what runs in that terminal, a small picture of its page, whether it is on screen, running out of sight, closed but kept, or unloaded, and the memory its pages use. At the top, the memory of all in-app browser pages against the limit in Settings → Browser, how many run, and how many were unloaded.
- Go to terminal selects that workspace and terminal and shows its browser (an unloaded one loads again).
- Close now closes that terminal's browser and frees its memory.
Monitoring opens on this page. The pictures are a cache: taken while the page is open for a browser without one or with one over five minutes old, and kept in a private folder of Agentty's data; a browser that closes takes its picture with it.
AI usage#
Cost, calls, cache hit rate and tokens, broken down by model, project and tool. The numbers come from the transcript files the agent CLIs already wrote on your disk.
Counting is not as simple as summing lines. Claude Code writes one JSONL line per content block, so a single API response appears several times with the same message id; those are de-duplicated by that id. Codex writes one usage record per response instead, keyed by response id. Agentty follows each format so a response is counted once.
Claude model prices are built in. For other models — the ones Codex uses, for instance — add prices in ~/.agentty/pricing.json and they are included:
{
"some-model": { "input": 1.25, "output": 10.0, "cacheRead": 0.125 }
}Prices are USD per million tokens. cacheRead, cacheWrite and cacheWrite1h are optional and default to 10%, 125% and 200% of the input rate.
These are estimates for your own orientation, computed from local files. Your provider's invoice is the real number.
Processes#
The AI processes running on your machine right now, with what started them. Useful when something is still burning tokens after you thought it stopped.
Proxy#
The proxy is now a plugin. Proxy Capture lists what your tabs and AI sessions talk to: start capture, open a tab, filter by text, tab or endpoint. Install it from Plugins → Install from Git with https://github.com/empty-user77/agentty-proxy-capture (it needs Node.js 18 or newer). Its eye icon is in the tab strip at the top right, and its panel opens docked on the right, beside the terminals.
Terminals and AI sessions opened while capture is on are routed through a proxy running on your own machine. Apply to open terminals does the same for shells that are already open.
Capture works in one of two scopes:
Terminal scope (default): the terminals opened while capture is on — AI sessions or plain shells — and the ones you applied it to. Capture stops by itself once all of them are closed.
Workspace scope (Capture all work in this workspace): every terminal of the workspace in front, open shells included, and only its connections are listed. Capture stops by itself when the workspace is closed or deleted. AI sessions that were already open have to be restarted to be captured.
HTTPS stays encrypted. Only the host, port, byte counts and timing are recorded — no certificate is installed and nothing is decrypted.
For plain HTTP, the method, path and status are recorded. Headers are recorded only when you turn on header recording, and credentials in them are shown as
***.Records live in memory, are never written to disk, and disappear when the plugin stops.
Stopping capture stops the recording. Terminals that were given the proxy keep using it so they don't lose their network.
Worktrees#
Every git worktree on this computer, grouped by project: its branch, when it was last worked on (its last commit or newest uncommitted change), uncommitted files, commits the default branch doesn't have yet, its pull request (open, merged or closed — read through the GitHub CLI you are signed in to), and its size.
Worktrees are looked for in the folders under your home folder, in Agentty's worktree folder and in the folders you have open. Projects with nothing but their own folder are left out.
Tick several and press Remove — or Select safe ones first, which picks every tree with no uncommitted changes whose commits are already merged. The dialog asks first:
- Delete their branches too removes a branch only when nothing on it would be lost: git's own check, or a pull request merged at exactly the branch's last commit (so squash merges count). Other branches stay.
- Trees with uncommitted changes are skipped unless you tick that they go too — those changes are then lost.
- The project folder itself and a tree a tab is working in can't be selected.
Disk#
How full the disk is — in use, can be cleared, free — and which folders in your home folder take the room, each opening onto its own biggest folders.
What can be cleared is only what is made again by itself:
- Project build output — per project, Remove build junk (Cargo
target,.next, Gradlebuild, SwiftPM.build, …) and Clear cache (.turbo,.parcel-cache,node_modules/.cache, pytest/mypy/Ruff caches, …). A folder only counts when its tool's project file sits next to it, and Cargo'stargetalso needs the tag Cargo writes into it. - Caches — the development tools' own caches: npm, Yarn, Bun, pip, uv, Go, the Cargo registry, Gradle, Homebrew, CocoaPods, JetBrains, and Xcode DerivedData.
- Other — the trash and log files.
Dependencies such as node_modules or ~/.m2, and anything a project needs to run, are never offered. Each removal is confirmed first and checked again right before it happens; links are never followed. The next build or install just takes a little longer.
Trash#
Delete Workspace moves a workspace to the trash instead of removing it: its terminals close and it leaves the list. Open the trash from the end of the Monitoring tabs, or with View Trash at the bottom of a workspace's menu.
Each entry shows when it was deleted, when it goes for good, its workspace path and its session paths. Tick some or all of them to restore them or delete them now; deleting asks first and can't be undone. A restored workspace comes back asleep and wakes when you open it, with its sessions resumed. Its orchestrations and board tickets come back with it.
Entries go by themselves after 7 days. Change that with Delete automatically after on this page, or Delete trash automatically after in Settings → General: a longer period also applies to what is already in the trash, a shorter one only to what you delete from then on.
A worktree or sync data you chose to delete with the workspace stays until the workspace is deleted for good. Session files are never deleted: they stay where the agent keeps them.