Sessions

A session is a single Claude Code or Codex conversation. ServerCC automatically discovers and indexes all past sessions for each workspace, so you can resume any previous conversation at any time.

Session Picker

When you tap a workspace, the Session Picker opens, listing all previous Claude Code/Codex sessions sorted by last modified date (newest first).

Session Information

Each session in the list displays:

  • First prompt — The first message you sent to Claude in that session
  • Summary — An AI-generated summary of the conversation
  • Message count — Total number of messages exchanged
  • Last modified — When the session was last active
  • Git branch — The branch that was checked out during the session (for Git workspaces)

bg Sessions

Sessions started through Claude Code's Agent View (or with claude --bg) also appear in the history, marked with a bg badge that is color-coded by state — working, done, or failed. Tap one and choose Resume bg Session to reattach to the still-running instance. See Agent View & bg Sessions for the full story.

Tip

Sessions are loaded in pages of 12. Scroll to the bottom and tap Load More to see older sessions.

Creating a New Session

Tap the New Session button at the top of the session picker. This starts a fresh Claude Code session by running claude in the workspace directory. You'll be taken directly to the terminal.

Resuming a Session

Tap any existing session in the list to resume it. ServerCC runs claude --resume <sessionId> to restore the conversation context. Claude will remember the previous messages and continue from where you left off.

Note

Resuming a session after a server reconnect may lose some context, as Claude Code's -c flag has limitations on how much context it can restore.

Deleting Sessions

Swipe left on any session in the list to reveal the Delete button. This removes the session data from the server's ~/.claude/projects/ directory.

How Sessions Are Stored

Claude Code stores sessions on the server in ~/.claude/projects/, organized by workspace path. ServerCC discovers sessions through a three-tier approach:

  1. Session index — Fast lookup via sessions-index.json (primary)
  2. Directory scan — Scans project directories if the index is missing (fallback)
  3. JSONL reconstruction — Rebuilds session list from individual .jsonl files (last resort)

This means sessions created by Claude Code on desktop or other clients are also visible in ServerCC, and vice versa.

Sessions in the Terminal

While in the terminal, you can switch sessions without leaving the view — tap the Sessions button in the bottom toolbar to open the session picker as a sheet.

See also: Background & Parallel Running for how sessions persist when you leave the terminal.