AgentGridAgentGrid Docs
Core Concepts

System tray and daemon

The tray icon that stays after you close the window, and the background daemon that keeps workers running.

AgentGrid installs a system tray icon (notification area on Windows, panel indicator on Linux) so the app has a home when the main window is closed. It's also the front door to the background daemon. On macOS there's no menu bar icon; the same menu is on AgentGrid's Dock icon.

The tray menu

Right-click the tray icon to open the menu. On macOS, right-click AgentGrid's Dock icon:

  • Show AgentGrid — brings the main window forward, creating it if you'd closed it.
  • Hide Window — appears only when the window is currently visible.
  • Daemon: … — a status row (see below). Only shown when the daemon is enabled.
  • Quit Daemon — gracefully stops the background daemon. Enabled only when the client is connected to it.
  • Export diagnostics… — saves a diagnostics bundle you can send us, even when you aren't signed in. See Logs and diagnostics.
  • Quit AgentGrid — closes the app. If the daemon is running the label becomes Quit AgentGrid (daemon keeps running) so you know your workers survive.

On Windows, left-clicking the tray icon also surfaces the main window directly. On Windows and Linux, the icon follows the system's light or dark theme.

The background daemon

Long-running workers used to die the moment you quit the app. The daemon is a background process that owns PTYs and worker child processes independently of the main window, so you can close (or crash) AgentGrid without losing your agents' work. After a crash, the next launch reattaches every terminal whose pane is in a saved layout, and ends the ones it can never reattach, such as a pane created after the last save, so they stop holding ports and memory. Anything it isn't sure about is kept. On Mac, background jobs an agent started and left running, such as pnpm dev & or nohup, also end the next time AgentGrid or the daemon starts, including services an agent started such as a local database. Apps, terminal sessions in tmux, screen or zellij, and container hosts such as Colima are left running.

The daemon is on by default and starts automatically with the app, so the tray menu shows the daemon rows and the "daemon keeps running" quit label. To turn it off, clear Settings → Advanced → Keep workers and terminals running in the background and restart AgentGrid when asked. If the background service can't start, that setting says so and shows where its log is. Connecting another computer under Settings → Devices needs the daemon on, on both computers.

The status row reports one of:

  • Daemon: connected · port <port> · pid <pid> — the app is talking to a live daemon.
  • Daemon: connecting… — handshake in progress.
  • Daemon: running (pid <pid>) · not connected — a detached daemon from a previous run is still alive but the current app hasn't adopted it yet.
  • Daemon: not running — no daemon process is up.

Use Quit Daemon when you want to stop everything cleanly; use Quit AgentGrid (with the "daemon keeps running" suffix) when you just want the window gone but the agents to keep churning.

Next

  • Agents and workers — what actually runs inside a worker pane.
  • Panes — the canvas surface every agent runs in.

On this page

Ask AI

Ask a question about AgentGrid. Answers come from these docs, with links to the pages they use.

AI answers can be wrong. Check the linked pages.