Feature

Notifications

Agent notifications are on by default (Settings → Notifications). SplitNest tells you when an agent needs you (a permission, a question, sign-in, or anything else it waits for), finishes, or stops with an error.

An in-app notice reading that Claude Code finished, with a Show button

Where you see it

  • Nothing for the tab you are looking at.
  • An in-app notice at the bottom right with a Show button when SplitNest is in front but another tab, workspace or Settings is shown.
  • A Windows notification when SplitNest is minimized or behind another program. Clicking it, also later from Notification Center, brings SplitNest back and shows that exact tab.

For "needs you" the taskbar button also flashes, and a small amber dot stays on it until you have seen the tab.

What it says, and what it does not

The text is SplitNest's own words, for example Claude Code needs permission, followed by the workspace and the name you gave the tab (car-rental · Backend), or else the agent's name.

The agent's session title and message can contain your prompt, so they are left out unless you turn on Include what the agent wrote. That setting is off by default.

When it fires

  • A notice goes away when the agent continues or you open the tab.
  • Finished comes from the agent's own report (Claude Code and Codex both report it at the end of a turn) and is skipped if the agent starts working again within 1.5 seconds.
  • Estimated states (a bell) do not notify unless you turn that on.
  • More than three Windows notifications within 10 seconds become one summary.
  • SplitNest removes its notifications from Notification Center when it quits.

Only real agents can raise a Windows notification

In PowerShell tabs only agents SplitNest found running in the tab can raise a Windows notification; a program that merely prints a status report naming an agent cannot. WSL tabs cannot be checked that way, so there the agent's report is enough.

The Start menu entry

Windows needs a Start menu entry to show an app's notifications, so the first notification adds SplitNest to the Start menu. Windows does not display the very notification that registers an app, so SplitNest shows that first one a second time 3 seconds later. Send a test notification in Settings shows whether Windows accepts them; if no banner appears, check Do Not Disturb and SplitNest's entry in Windows Settings → System → Notifications.

Notifications in the user guide →

Try it. SplitNest is free and open source for Windows 11.