This page is not yet translated. Showing English version.

Resource Manager

Click the memory reading in the status bar for a per-process breakdown of 1DevTool and every terminal, with live CPU sparklines.

Four agents running at once is four CLIs, four PTYs, and however much scrollback each has accumulated. Resource Manager turns the single number in the status bar into a list you can act on.

Click the memory reading in the status bar to open it.

The Resource Manager popover listing three terminals with per-process CPU and RSS, plus system memory, swap and CPU load

What the list shows

The header carries the totals โ€” combined CPU and summed RSS across everything 1DevTool is responsible for. Below it, two groups:

  • Terminals โ€” every terminal, named the way its tab is. cursor full at 111% CPU is a specific tab you can go and look at, not an anonymous process id in Activity Monitor.
  • 1DevTool โ€” the app's own processes, broken out as Main, Renderer and GPU, so an expensive app and an expensive agent never look the same. Anything else lands under Other.

Each row draws a live CPU sparkline while the panel is open, holding about a minute of history. Each sparkline self-scales to its own recent peak, so an idle terminal still reads as idle rather than being flattened by a busy neighbour.

On platforms that cannot report per-process figures, the panel says so directly โ€” Per-terminal CPU/RSS isn't available on this platform โ€” instead of showing zeros.

System memory

Underneath the process list:

  • Used / total, with a bar
  • Available
  • Swap used / total
  • CPU Load against your core count

When the machine has started paging to disk, the panel says it in plain words โ€” Your system is paging to disk. Close unused apps or terminals to reduce lag โ€” rather than leaving you to infer it from the swap figure.

Clear terminal buffers

The ๐Ÿ—‘ control in the header releases cached scrollback across your terminals and re-samples immediately, so you see whether it actually helped instead of guessing.

It clears buffered scrollback only. Your sessions keep running and nothing about the agents' state changes โ€” see Session Persistence for what survives a restart.

Use โ†ป Refresh now to take a fresh sample at any time.

Related

  • Terminal Tips โ€” getting more out of a busy terminal grid
  • AI Usage โ€” what your agents are spending, as opposed to what they are using
  • Batch Terminals โ€” opening many agents at once, deliberately
  • Layout Modes โ€” fitting several terminals on one screen