Skip to content

Tools

Game mode

Free the machine for a game in one step — freeze the dev servers you pick, stop what you choose, keep Pip quiet — and restore what can come back when you are done.


What game mode does#

A day of development leaves a lot running: dev servers, containers, a WSL virtual machine, agents. Game mode sets that aside while you play. You choose what steps aside, Pip freezes or stops it in one go, and exiting brings back everything that was frozen and restarts the containers that were stopped.

Nothing happens until you have seen the list and pressed Start game mode. Even with nothing to free, game mode still keeps Pip itself quiet while you play.

Starting game mode#

Three ways in, all of which open the same preview:

The tray menu
Game mode…, in the menu bar on macOS and the tray on Windows.
The keyboard
Press G while Pip is focused. It is an in-app key, not a global hotkey, so it does nothing while a game has focus.
Settings
Settings → Game mode → Review game mode.

To change the key, open Settings → Game mode → Keyboard shortcut and press any letter from A to Z, without modifiers. Letters the app already uses elsewhere are refused. Clear turns the shortcut off, and Settings still reaches game mode.

Game mode needs an active licence.

Choosing what steps aside#

The preview lists what is running in three groups — Servers, Agents and, on Windows, WSL — with an estimate of the memory your picks free. Each server row does one of two things:

Freeze
Comes back on exit. The server and every process it started are paused where they stand, and on Windows their memory is handed back to the system. Nothing is lost; it picks up where it left off.
Stop
Does not come back. The server is stopped the way Kill stops it, and you start it again yourself when you need it.

The preview starts with sensible picks, which you can change:

  • Dev servers that can be frozen are ticked to freeze. One that cannot be frozen is left unticked — stopping it is your call.
  • Docker containers are ticked to stop, and restart on exit. Containers are stopped rather than paused, so anything a container kept only in memory is gone when it comes back.
  • Servers running inside WSL are ticked to stop, and do not come back.
  • Agents are never ticked for you. Ending one stops its process; the conversation can be resumed later from Agents. An agent that is busy or waiting on you is marked, because ending it loses the work in progress.

Anything that will not come back is listed first and never folded away, and the footer names it again: Not restored on exit: …

Shut down WSL

On Windows, Shut down WSL stops the whole WSL virtual machine and returns its memory — every distro and every shell open in one, not only the servers listed. Containers that run in WSL restart on exit; WSL itself starts again the next time you use it. It is off by default when Docker Desktop runs in WSL, since its engine stops with it.

While you play#

A frozen server is marked Frozen on its row in Servers. It keeps its port, so nothing else can take it, but it does not answer — a browser tab pointed at it waits until you exit. Killing a frozen server from Servers works as usual.

Pip itself steps back too:

  • Desktop notifications are off — agents and git alike. They are not saved up and shown afterwards.
  • With the window closed, Pip checks on servers, agents, memory and the network less often. Open the window and everything is live again at once.
  • Game detection pauses, since you are already playing.

Exiting game mode#

Choose Exit game mode from the tray, press your game mode key, or use the row in Settings. The exit dialog shows what Comes back — frozen servers resume, stopped containers restart — and what Stays off. Press Exit and restore.

Frozen servers are resumed first, then each container is started on its own Docker engine. Pip only resumes a process it can prove is the one it froze: if a server exited, or its process id now belongs to something else, it is left alone.

If something cannot be restored, game mode stays on and the dialog says what failed and why, so you can try again. When retrying will not help, Forget the rest turns game mode off and stops Pip keeping track of what is left — end a process still frozen from Task Manager or Activity Monitor, and start a container yourself.

Game detection#

Pip can notice a game starting and offer game mode. It looks for games installed through Steam and a list of popular games outside it, and ignores launchers, anti-cheat, updaters and tools such as Wallpaper Engine or OBS.

Detection only ever suggests. It never freezes or stops anything by itself, and game mode does not end when the game closes — exit it when you are ready to get back to work. Each game session is offered once; a game that was already running when you turned detection on is not.

Three switches under Settings → Game mode, all on by default:

Detect games
Look for running games on this device. The other two switches need it.
Desktop notifications
A notification when a game starts, with Review game mode to open the preview.
In-app suggestions
The same offer inside the window, when Pip is open.

Quitting, restarts and crashes#

Quitting Pip resumes every frozen server, so nothing stays paused without Pip there to wake it. Stopped containers are not restarted on quit: game mode is still on when Pip next opens, and exiting it then restarts them.

Pip records each step before it takes it, so a restart or a crash does not lose track of what it froze or stopped. If the record cannot be written, game mode does not start at all.

Removing Pip

Exit game mode before uninstalling. Pip refuses to remove its data while game mode still has servers or containers to restore. How to uninstall.

What cannot be frozen#

Elevated processes
A server started as an administrator or another user cannot be frozen or stopped, because Pip does not run elevated. The preview and the result say so.
Servers run straight from a shell, on macOS
Freezing a process a terminal shell started directly would hand the terminal back to the shell for good, so those rows can only be stopped.
Pip and the system
Pip never touches itself, the operating system's own processes, or apps that serve an agent, such as an editor hosting Codex.

Did this page not answer it? Tell us what you were looking for — that is how Pip's documentation gets written.