Claude Desktop vs Claude Code Status on Windows

On Windows, Claude Desktop and Claude Code look like one product but produce three independent signals. Reading the wrong one sends you to the wrong window. This guide shows how to tell them apart and what each signal can honestly prove.

Before you start

• Agent Island for Windows installed and resident in the system tray
• Claude Code, Claude Desktop, or both in use on this machine

1. Separate the three signals

Three things move independently, and conflating them is the root of most confusion:

• The Claude Desktop window — an application surface that can be closed while its session continues
• The Claude Code session — a run in a terminal, tracked through the records it writes on disk
• Usage figures — numbers fetched from your provider account, which can fail on their own without anything being wrong locally

A quota error is not a session error. A closed window is not a finished turn.

2. Read the session row, not the window

Session state — working, your turn, paused — is derived from the session records on disk, not from whether a window is visible. That is why the row keeps updating while the terminal is minimised or buried behind other apps.

3. Know which surface owns the session

Each session carries its own identity and launch target. A Claude Desktop session restores the app; a CLI session returns you to its working-directory context. The row label tells you which one you are looking at before you click anything.

4. Use Open thread to reach the right place

When the alert fires, Open thread restores the surface that owns that specific session rather than launching the app generically.

5. Account for close-to-tray behaviour

Closing the Claude Desktop window does not necessarily end the process, and a session can stay alive after the window disappears. That gap is exactly where a status companion earns its place: the row keeps reporting even though there is nothing on screen to look at.

6. Keep usage errors in their own lane

If a usage row reports an error, that is the provider endpoint talking. Session monitoring is entirely local and keeps working while a usage refresh fails — the two paths share no dependency.

7. Run a two-minute Windows check

Start a Claude Code run, minimise the terminal, confirm the row still moves. Close the Claude Desktop window on a live session, confirm the row survives. Then let a usage refresh fail (disconnect briefly) and confirm session state is untouched. If all three hold, your setup is reading the right signals.

If it does not work