Manage a Session

Rename a Session, choose its model, control when it sleeps, and delete or restore it. Each of these is the Session’s Creator’s to do: others in the Session see the result.

Rename it

1. Press the pencil beside the title in the Session’s header, or on its row in the sidebar.

2. Type the name, up to 80 characters, and press Enter. Esc cancels.

A Session without a name shows its Work branch. Clear the name to go back to it.

Choose the model and effort

Two buttons under the prompt box show the Session’s model and effort, such as Sonnet 5.5 and High. The effort button says Effort while no level is set, and Claude Code picks one. It’s one setting for the Session.

1. Press the model button and pick a model. Default is Claude Code’s own default.

2. Press the effort button and slide to Low, Medium, High, Extra or Max. With the keyboard, use the arrow keys and press Enter. Use the default goes back to no level.

A model that takes no effort level has no effort button.

The change applies from the next Turn. The Runner restarts Claude Code in the same conversation, and the next prompt waits until it’s back. Restarting interrupts running subagents, so the web UI asks first while any run.

Sleep and wake

A Session goes to sleep after 15 minutes, by default, when nothing is happening: no Turn or subagent running, no prompt queued, no open question, and nobody in it. Sleeping stops Claude Code and the Sandbox. The Workspace, the conversation and the Sandbox’s disks are kept.

• Sleep now, in the header, puts it to sleep at once.
• Your next prompt wakes it, as does Wake now on its banner. Claude Code resumes the same conversation, with node_modules, caches and Docker’s data as they were.

Keep it awake

To keep a Session running while nobody is in it, such as for a dev server or a long command, turn on Keep awake in its header. The sidebar marks the Session with a sun for everyone.

Turn Keep awake off, or press Sleep now, to let it sleep again.

When its Runner goes offline

A Session whose Runner is offline is Frozen. You can read it, and new prompts wait in its queue. When the Runner is back, the Session carries on, and runs the waiting prompts.

Delete and restore it

Delete Session, the bin in the header, archives the Session. Its Sandbox is destroyed. Its Workspace and conversation are kept for 30 days by default, then deleted.

To restore it, press Undo in the toast, or Restore on it in Archived Sessions, in the sidebar. A restored Session starts Asleep. Your next prompt wakes it in a fresh Sandbox, without the old node_modules or Docker data.

Purge it to free disk

A Runner running low on disk doesn’t have to wait 30 days. In Archived Sessions, press Purge on an Archived Session, or tick several and press Purge selected. Anyone with access to the Repo can, not just the Session’s Creator. The confirmation names each Session: once purged, it can’t be restored, and its Workspace goes with any work it never pushed. A Runner that is offline frees the disk when it reconnects.

To see what is worth purging, the list shows how much of its Runner’s disk each Archived Session takes: its directory with the Workspace, and its disk volumes, as actually used rather than the sizes they are allowed to grow to. Tick several and the list shows the total they free, and so does the confirmation. A Session whose Runner is offline shows its size as unknown, and the total says it is at least what is known.

Next steps

Session lifecycleEach state, and what sleep, wake and archive keep.

Work with subagentsWhat happens to running agents when a Session sleeps.

A Session doesn't go to sleepFind what keeps a Session awake.