Background & Parallel Running

ServerCC lets you background Claude Code/Codex sessions so they keep running while you work on other things. You can also run multiple sessions in parallel across different workspaces.

Backgrounding a Session

When you're in a terminal with Claude running, you can background the session to keep it alive:

You can also background a session by tapping the menu button (⋯) in the terminal and selecting Background Run.

The Running Tab

The Running tab at the bottom of the app shows all backgrounded Claude Code sessions. Each entry displays:

• Workspace name — Which workspace the session belongs to
• Branch name — If running in a worktree, shows the branch (e.g., "ProjectName (feature-branch)")
• Server name — Which server it's running on
• Activity state:
  • Vibing — Claude is actively working (terminal has recent output)
  • Waiting — Claude is idle, waiting for your input
• Time elapsed — How long the session has been running (e.g., "2m ago", "1h ago")

Reattaching to a Session

Tap any session in the Running tab to reattach. The terminal view opens with the full session state restored — you can see the output history and continue interacting with Claude immediately.

When reattaching:

• The terminal output, cursor position, and scroll state are preserved
• Quick action buttons update based on the current terminal state
• The file browser reloads the workspace directory

Stopping a Session

Swipe right on a session in the Running tab to reveal the Stop button. This terminates the Claude process on the server and releases the SSH connection.

Parallel Running

ServerCC supports running multiple Claude Code/Codex sessions simultaneously across different workspaces. This is one of its most powerful features — you can have Claude working on several tasks at once.

How It Works

While only one workspace can be active (visible in the terminal) at a time, you can background any number of sessions:

Example: Multi-Task Workflow

Running tab:
  ● Vibing  — backend (feature/api)     on Dev Server    3m ago
  ● Waiting — frontend (fix/header)     on Dev Server    8m ago
  ● Vibing  — data-pipeline             on ML Server    12m ago

In this example, three Claude Code sessions are running in parallel — two on the same server (in different workspaces/worktrees) and one on a different server entirely.

Switching Between Active Sessions

When you open a new workspace while another is active:

• If the previous workspace was backgrounded — it stays running, no interruption
• If the previous workspace was not backgrounded — it receives a deactivation signal and closes cleanly

Notifications when Claude Finishes

When a backgrounded session goes from active to idle — that is, the agent finishes a task and is waiting for your next message — ServerCC sends a local push notification so you can come back when there is something to look at.

Notifications fire for ServerCC-launched sessions, persistent (tmux) sessions, and Host Tmux Takeover panes you have attached to.

A notification fires at most once per background period per session — reopening the app and re-backgrounding the session resets it. To turn notifications off for a workspace, switch on Mute Notifications in the workspace settings.

Auto-Reconnect

If the SSH connection drops or the device switches networks (Wi-Fi ↔ cellular), ServerCC reconnects automatically. A status strip at the top of the screen shows the reconnect progress; tap Cancel to stop.

After a successful reconnect, the terminal restores its previous output, scroll position, cursor, and No Flicker full-screen state. Your Claude Code or Codex session resumes in place — you do not need to start a new session.

For backgrounded non-tmux sessions, you also get a notification when the connection is restored, so you know the agent is reachable again without opening the app.

See also: Connection History for browsing past connections and reviewing reconnect events.