Workspaces

A workspace is a project directory on your server where Claude Code sessions run. Each server has a default workspace created automatically, and you can create additional workspaces for different projects.

Creating a Workspace

From the server detail screen, tap the + button in the Workspaces section.

Basic Information

• Name — A name for the workspace (required)
• Description — An optional description of what the workspace is for
• Icon — Choose from 12 icons to visually identify the workspace

Custom Path

By default ServerCC creates the workspace at a path under your home directory. To put it somewhere else, type the path in the text field (for example /home/user/projects/myapp), or tap the folder button on the right to open the directory picker.

The picker opens at your home directory and lists the folders on the server over SFTP. Tap a row to descend into a subdirectory; tap a path crumb at the top to go back up. Tap Select Folder in the top right to use the current path — it will be written back into the text field.

After picking (or typing) a path, ServerCC checks whether the directory already exists. If it does not, an Auto-create directory toggle appears so you can have ServerCC mkdir it for you when you save.

Git Repository (Optional)

If Git is installed on the server, you can provide a repository URL to clone when creating the workspace. Both SSH and HTTPS URLs are supported:

git@github.com:user/repo.git
https://github.com/user/repo.git

If the clone fails, you'll have the option to retry or skip and create the workspace without cloning.

Workspace Settings

Each workspace has settings that affect how Claude Code or Codex sessions are launched. These toggles are available in the Session Picker under the Settings section.

No Flicker Mode

Enables Claude Code's full-screen TUI mode by setting CLAUDE_CODE_NO_FLICKER=1. In this mode, Claude Code renders as a full-screen terminal application with tap/mouse support, and significantly reduces screen flickering on slower connections.

Permission Mode (Claude Code)

For Claude Code, the Session Picker exposes a four-option picker that maps directly to Claude's --permission-mode flag:

• Default — Claude asks before running tools, editing files, or executing shell commands (recommended baseline).
• AcceptEdits — File edits are auto-approved; other tool invocations still prompt.
• Auto — Claude decides which actions need confirmation; most safe operations run without prompts.
• Bypass — Adds --dangerously-skip-permissions. Claude executes every tool without asking — use only in trusted environments.

The labels Default, AcceptEdits, Auto, and Bypass are shown in English across all locales to match Claude Code's own terminology.

Full Auto Mode (Codex)

For Codex, a single Full Auto Mode toggle adds --full-auto. Codex then executes every tool invocation without asking for confirmation.

Unlock Keychain for OAuth (macOS)

When connecting to macOS servers via SSH, Claude Code stores OAuth credentials in the macOS Keychain. However, SSH sessions don't automatically have Keychain access. Enable this toggle to automatically unlock the Keychain when a Claude Code session starts.

When enabled, ServerCC will:

• Prompt you to save your macOS user login password (stored in the iOS Keychain)
• Automatically run security unlock-keychain before Claude Code launches
• Input your password when the unlock prompt appears, so Claude Code can access stored OAuth credentials

Sessions, Worktrees & Background Running

Each workspace contains Claude Code sessions and can optionally use Git worktrees. See the dedicated guides for details:

• Sessions — Create, resume, and manage Claude Code conversations
• Worktrees — Work on multiple Git branches simultaneously
• Background & Parallel Running — Background sessions and run multiple instances in parallel

Deleting a Workspace

In the server detail screen, swipe left on a workspace to delete it. This removes the workspace from ServerCC but does not delete the directory on the server.