# Named Sessions import { Callout } from "nextra/components"; Named sessions let you label an ongoing piece of agent work so you can pick it up later by name. ## What a session is A session is a named, persistent wrapper around agent work inside a pane. When you name a session, Pane remembers the association between the name, the pane, and the agent state. Close Pane, reboot, come back. The session is still there, still named, still resumable. Without named sessions, you identify work by pane name and branch. That works for short tasks. For ongoing work (a multi-day feature, a recurring review loop, a long investigation) a named session gives you a stable handle that doesn't change when the underlying pane is archived and recreated. ## Creating a named session Name a session when creating a pane through the UI. The pane name doubles as the session name. Pick a name that describes the ongoing work, not just the branch: `auth-rewrite` instead of `issue-252`. A session name, once set, stays with the pane across restarts. ## Resuming work When you reopen Pane, named sessions appear in the sidebar with their session name. You don't need to remember which pane or branch was which. The session name tells you. If a pane was archived but the session still has work to do, creating a new pane with the same session name picks up where the previous one left off. ## When to use sessions - **Multi-day features**: name the session once, come back to it across days. - **Recurring workflows**: a session named `daily-review` or `deploy-check` that you reuse. - **Handoffs**: tell a teammate "pick up the `auth-rewrite` session" instead of "find the pane on the `fix/auth-token-refresh` branch." Named sessions were introduced in v2.4.106. Update Pane to use them.