Skip to content

Apple has approved code signing for our macOS app, and we’re still securing it for Windows. In the meantime, follow the Windows guide to open Pip.

Game mode

Work’s still running. It’s game night.

Dev servers, containers and a WSL virtual machine don’t stop just because you have. Game mode freezes or stops the ones you pick in one step, keeps Pip quiet while you play, and brings them back when you’re done.

macOS and WindowsPay once, updates included

Seven servers still running. The game wants the memory.

Shutting everything down by hand means remembering what to start again later. Game mode does it from one screen: dev servers freeze in place and keep their ports, Docker containers stop and are restarted on exit, and on Windows the WSL virtual machine can shut down to return its memory.

Nothing happens until you’ve seen the list. Pip picks sensible defaults — servers that can freeze are set to freeze, agents are left alone — and names anything that won’t come back before you press Start game mode. While you play, Pip’s own notifications stay off.

Freeze what comes back. Name what doesn’t.Pip for Windows · Preview data
chosen row by row
Freeze or stop
frozen servers and stopped containers
Restored
no Pip notifications while you play
Quiet

See what you get back.

The preview lists your servers, WSL and agents with an estimate of the memory your picks free, and names anything that won’t be restored on exit.

Pick up exactly where you were.

A frozen server pauses with its whole process tree and resumes on exit, with nothing restarted and nothing lost. On Windows its memory goes back to the system while it waits.

Get a nudge when a game starts.

Pip can notice a Steam game or a popular title starting and offer game mode. It only ever suggests — it never freezes or stops anything by itself.

From work to game and back again.

  1. Open game mode.

    Choose Game mode… from the tray, press G in Pip, or accept the suggestion when Pip notices a game starting.

  2. Review the picks, then start.

    Choose whether each server freezes or stops, whether WSL shuts down, and which agents end. Press Start game mode when the list looks right.

  3. Exit when you’re done.

    Choose Exit game mode. Frozen servers resume, stopped containers restart, and Pip tells you about anything it couldn’t restore.

What game mode will and won’t touch.

Freezing, stopping and shutting down WSL each work differently. These are the details worth knowing before you start a game with work still open.

What is the difference between freezing and stopping?
Freezing pauses a dev server and every process it started, then resumes it on exit as if nothing happened. It keeps its port, but doesn’t answer until you exit. Stopping ends the server the way Kill does, and you start it again yourself. Docker containers are stopped rather than paused, and Pip restarts them on exit; anything a container kept only in memory is gone. Servers inside WSL can only be stopped, and don’t come back.
Will game mode stop my work without asking?
No. Game mode only starts from its preview, after you’ve seen what it will do and pressed Start game mode. Game detection can offer it when a game starts, but never freezes or stops anything itself, and game mode doesn’t end when the game closes — you exit it when you’re ready. Agents are never picked for you; an agent that is busy is marked, because ending it loses the work in progress.
What happens if I quit Pip while game mode is on?
Pip resumes every frozen server as it quits, so nothing stays paused without it. Stopped containers wait: game mode is still on when Pip next opens, and exiting then restarts them. Pip records each step before it takes it, so a restart or crash doesn’t lose track of what it froze or stopped.

Play now. Pick your work back up later.

Every Pip tool. $29 USD, once. One machine at a time.