A release spent making the app stop eating your machine

**See what is actually using your machine** — the Resource Manager splits memory and CPU into **1DevTool**, the **terminals** you started, and **other apps**, and the three add up to what your OS reports.

**The panel names the split your OS hides** — Task Manager nests shells, `node` and `claude` under the 1DevTool row and Activity Monitor spreads the app across “Helper (Renderer)” rows; each bucket carries a one-line explanation of what it really contains.

**Expand a bucket to see what is behind the number** — the individual terminals and processes, each with its own CPU and RSS, named the way its tab is.

**An attention strip for the terminal that is the problem** — a pane pinning the CPU or flooding output gets a row naming the reason (“62% CPU”, “8.4 MB/s output · throttled”) with **Reveal** to jump straight to it.

**Act on it without leaving the panel** — behind the row’s **⋯**: **Pause output**, **Lower priority**, **Hibernate**, or **Close**.

**Copy diagnostic report** — one click puts a Markdown summary of the buckets, top consumers, GPU rendering status and recent stalls on your clipboard, ready to paste into a bug report.

**The machine, in plain numbers** — **RAM used**, **Available**, **Swap**, **CPU load** against your real core count, **WebGL** rendering status, and a **Busiest other apps** list so an expensive browser is named rather than blamed on us.

**When the app freezes, it tells you why** — if the window stops responding a red dot appears in the status bar, instead of leaving you guessing whether the app died.

**A short toast once it comes back** — *“1DevTool paused 6.2 s while system CPU was 98% — top: claude, node”*, so a freeze is attributable instead of mysterious.

**Recent stalls this session** — listed in the Resource Manager and under **Settings → General → Diagnostics**, alongside the stall threshold and an opt-in for sending stall reports.

**Switching layouts no longer rebuilds every terminal** — grid, columns, rows, single, vertical tabs, chat and vibe keep the panes you already had open instead of flashing **Opening terminal** on each one.

**Jumping back to a recent terminal is instant** — a pane you just left is still there, with its scroll position and selection, instead of replaying from scratch.

**More terminals stay sharp at once** — GPU rendering covers a larger set of panes, and a pane that is off screen gives its slot back so a busy workspace does not fall over to a blurry fallback.

**A flood of output in one pane no longer freezes typing in another** — that terminal’s output is batched and the pane says so, while every other pane stays at full speed. Nothing is dropped: the full output is there when the flood ends.

**A workspace with dozens of terminals stays responsive** — idle CPU and memory stay flat instead of climbing as you keep adding agents.

**Terminal history is bounded by memory, not just line count** — a very wide pane keeps fewer rows for the same memory, and widening a pane never throws away history already on screen.

**Other projects’ browser tabs unload while you are away** — after you leave a project its browser tabs release their memory once idle (**Settings → Browser**, 15 minutes by default). Tabs with unsaved fields, playing audio, driven by an agent or pinned **Keep awake** stay loaded, and returning wakes the active tab.

**Idle agents can hibernate** — an agent sitting at its prompt for half an hour shuts its CLI down and keeps the tab, showing *“Hibernated — press any key or click to resume”*. Never mid-turn, never a seat on a running team. Right-click for **Hibernate** or **Hibernate all idle**.

**Huge HTTP responses stay out of your project file** — a 20 MB response body no longer bloats the saved workspace; it lives in a bounded on-disk cache and loads on demand when you open the JSON view or copy it.

**When the machine runs out of memory, 1DevTool gets out of the way** — background polling pauses, idle browser tabs sleep sooner, and terminal processes drop to a lower CPU priority so typing stays responsive. Switch it off under **Settings → General → Diagnostics**.

**The app is less than half the size** — a macOS install drops from 709 MB to 360 MB, with roughly a third of the files it used to ship, so downloads and updates finish quicker.

**Browser automation uses the Chrome or Edge you already have**, with a clear message telling you what to install if neither is there.

**Searching prompt history and opening the app no longer block the window** — database work and startup checks moved off the thread that draws the UI.

**Mission Control no longer steals the composer** — when it auto-reveals beside Agent Input it borrows only the width the map needs, and gives the rest back the moment you switch panels or drag the splitter.

**Diagrams match the rest of the workspace** — Mermaid charts in the markdown preview and graph editor use a quieter palette, and loud author colours are toned down so nodes stay readable in both themes.