Hibernation

Idle agents shut their CLI down and keep their tab; browser tabs in projects you have left unload on their own.

A workspace with a dozen agents in it holds a dozen CLIs in memory, and most of them are sitting at a prompt doing nothing. 1DevTool reclaims that on its own, without closing anything you would have to set up again.

Idle agents hibernate

An agent left idle at its prompt for half an hour shuts its CLI process down. The tab stays exactly where it was and the pane reads:

Hibernated — press any key or click to resume

Press a key or click the pane and the same session comes back — the CLI restarts and resumes the conversation it was on, the way Resume Sessions does after a restart.

Two things never hibernate:

  • An agent mid-turn. Hibernation only ever happens at an idle prompt, so nothing you are waiting on is interrupted.
  • A seat on a running team. An agent that is part of a live orchestration keeps its process — see Agent Teams.

Hibernating on purpose

You do not have to wait for the timer:

  • Right-click a terminal and choose Hibernate.
  • Right-click and choose Hibernate all idle to sweep every idle agent in one go.
  • Use Hibernate on a terminal's row in the Resource Manager when it is the pane eating your machine.
  • Press Improve performance in the Resource Manager footer to sleep tabs, hibernate idle agents and clear buffers together.

Browser tabs unload too

The embedded browser follows the same idea from the other direction. Once you leave a project, its tabs release their memory after an idle period — Settings → Browser, 15 minutes by default.

Tabs that stay loaded regardless:

  • tabs with unsaved form fields
  • tabs playing audio
  • tabs being driven by an agent through Browser Automation
  • tabs you have pinned Keep awake

Returning to a project wakes its active tab, so switching back does not leave you looking at a blank pane.

When memory runs short

If the machine is genuinely under pressure, 1DevTool goes further on its own: background polling pauses and idle tabs sleep sooner than their normal timer.

On Windows, the programs you started inside 1DevTool terminals also drop to below-normal CPU priority until the pressure clears, so typing in another pane stays responsive — builds still complete, they just share the CPU more fairly, and priority is restored when pressure is low. Processes outside those terminals are never touched.

macOS and Linux do not let an application raise a process's priority back once it has been lowered, so there is no automatic mode there; the Resource Manager's manual Lower priority covers one terminal at a time and lasts until those processes exit.

The automatic behaviour is switched under Settings → General → Diagnostics — see Freezes & Slowdowns.

Related