Pup - the AI's own browser

@@ -668,3 +668,24 @@ machine has a GPU. pup's `pup_screen_record_start` is the fallback: a Google Mee when ab's recorder is missing, refuses, or the box has no usable GPU. Recording ONE pup window's page content is a different thing and stays pup's (`pup_record_start`). Full detail in `pup-screenshots-recording`.++## Know what you are spending: every open reports the machine's RAM++`pup_open_window`, `pup_open_tab`, `pup_list_windows` and `pup_status` all return a **`memory`** block, because+pup runs on somebody's actual laptop and you are spending their RAM:++```json+"memory": { "boxTotalMb": 32189, "boxFreeMb": 5597, "boxFreePct": 17,+            "browserMb": 2249, "tabsOnThisBrowser": 21, "avgMbPerTab": 107,+            "_hint": "17% of this machine's RAM is free and each pup tab here is costing about 107 MB..." }+```++`browserMb` is the WHOLE Chrome process tree for that profile (renderers and the GPU process included), so it is+the number that actually moves when you open a page. `avgMbPerTab` prices your next tab before you open it.++**Read the hint and act on it.** Under 25 % free, budget and close what you are done with. Under 10 % free, open+nothing more until you have closed something: that is where Windows starts paging to disk and the user's whole+desktop stutters, their touchpad included. A rich page is not cheap: Adom wiki component pages with 3D viewers+measured around 200 MB each, so twenty of them is 4 GB that Chrome will not hand back while you hold the tabs+open. Close tabs with `pup_close_tab` the moment a task is done, rather than leaving a window to grow.+(Written after a thread opened twenty of them on John's laptop and drove it into thrashing, 2026-09-10.)