Agent View & bg Sessions

Agent View is Claude Code's built-in dashboard for running multiple Claude Code instances in parallel on the same project. A supervisor process on your host manages every instance — much like tmux — so they keep working even after you close ServerCC, lose Wi-Fi, or switch apps. ServerCC supports opening the Agent View dashboard and jumping back into any of these bg sessions from the session history.

Requirements

Agent View requires Claude Code 2.1.141 or newer on the server — the entry row is disabled with a hint on older versions. The feature is Claude Code only (Codex has no equivalent).

Opening Agent View

On the workspace landing page, tap Open Agent View (Beta). ServerCC launches the dashboard (claude agents) scoped to the workspace, where you can:

  • Spin up parallel instances — start as many Claude Code sessions as you need on one workspace
  • Automatic worktree isolation — when an instance writes, a dedicated Git worktree is created automatically, so each instance edits its own copy and sessions never step on each other
  • Drive it with the shortcut row — a dedicated key row above the keyboard offers Space (peek at the agent under the cursor), → (open it), Close, and Pin

The first time you open Agent View, ServerCC shows a short in-app guide — you can reopen it anytime from the ? button in the toolbar.

bg Sessions in the History

Every Agent View instance shows up as a regular row in the workspace's Claude Code session history, marked with a lowercase bg badge. The badge is color-coded by the supervisor's view of the session:

  • ● bg · working — The instance is actively working
  • ● bg · done — The task finished
  • ● bg · failed — The instance hit an error

Tap a bg row and choose Resume bg Session to re-enter it — ServerCC attaches to the still-running instance (claude attach), with the full conversation exactly where it left off. Sessions that moved into an auto-created worktree show the worktree name as their branch.

How It Relates to tmux Persistent Sessions

bg sessions are independent of tmux. Persistent sessions keep a session alive by running it inside tmux; bg sessions are owned by Claude Code's own supervisor daemon. Both survive the app closing — in the Running list they carry different tags (tmux vs bg / agent view), and on an SSH reconnect ServerCC reattaches to bg sessions automatically.

Tip

To review what each parallel instance changed, open Git Diff — its worktree picker lets you flip between the diffs of every Agent View worktree.

See also: Persistent Sessions for the tmux-based way to keep work running, Background & Parallel for in-app backgrounding, and Worktrees for manual branch isolation.