Working with sessions

In the app: new session, choose a directory (for example ~/code/storefront), and it opens. One session is one Claude Code working in one directory. Sessions in different directories do not interfere with each other.

Every session is in one of three groups, in this order:

• Waiting on you: stopped on a question or a permission request. These come first.
• Just finished: done, and the result is ready for review.
• Running: working. Nothing needed from you.

Because of this ordering, the sessions that cannot continue without you are always at the top.

Sessions live on the machine that runs them, not in the client. Losing the network, switching devices or quitting the client does not end a session. When you come back, you are in the same session with its context intact.

One limit: while the computer that runs a session is asleep, the session pauses and waits. It does not keep editing on its own. This is why most people run sessions on a machine that stays on. Keeping Claude Code running when the laptop is closed.

When a session finishes, or stops to wait for an answer, you get a push notification. You do not need to keep the board open, and you do not need to guess whether a session is still running.

Risky actions such as deleting files, committing, or installing packages are sent to you as a question. They are never answered on your behalf. If a session goes in a direction you do not want, one switch turns off every automatic reply at once. How Claude Code permission prompts work.

The subscription sets how many sessions run at the same time. Opening one past the limit is refused at that moment. Sessions already running are not affected.

On your own machine the limit is that machine's memory, not the subscription. What the subscription limits there is how many machines you can register.