How it works

The premise

A memory viewer for the terminal, built on the same interface as disktree. Every process is grouped under the one that started it, and each group’s size includes everything beneath it, so a browser and its dozens of helpers show as one line you can open. Mark any number of processes and ask them to close, or force-kill them, behind a confirmation that shows where each one sits in the tree.

It’s careful about what it ends. It never ends the terminal it runs in or anything above it, and it checks each process’s start time first, so a stale view can’t end an unrelated process that reused a PID. Sizes are resident memory, the same figure as Task Manager’s working set or Activity Monitor’s Real Mem. It runs on Windows, macOS and Linux.

What’s included

Processes grouped under their parents, with each group sized by everything it started

Mark several processes, then ask them to close or force-kill them, after a confirmation that shows each one’s place in the tree

Won’t end its own terminal, and checks start times so a reused PID is never the wrong target

Refreshes in place after a kill without losing your position

How it’s built

ramtree is built on Rust and TUI.

The repository is 100% Rust by volume.

It carries 2 commits since Oct 2026, most recently changed in Oct 2026.

How the work is done

Every project here starts as a written spec, and the spec stays the source of truth once there’s code. The repository keeps a build plan with current status, an append-only decision log of where the code departed from the plan, and a handoff document that describes where things stand, including the unfinished parts.

That’s how one person keeps this many projects moving, and it’s what this page is written from.

Current state

Shipping. Released and usable today.

The source is public, so you can check anything on this page against it.