Supported AI Agents
ServerCC runs five coding agents on your own server over SSH — from your iPhone or iPad. Since version 1.8.0, Grok Build, OpenCode, and Kimi Code join Claude Code and Codex, with the same core workflow for every agent: install detection, one-tap launch, session history with exact resume, permission modes, and persistent tmux sessions.
| Agent | CLI | Permission modes | Notes |
|---|---|---|---|
| Claude Code | claude |
Default · AcceptEdits · Auto · Bypass | Full support, incl. Agent View, bg sessions, Skills, CLAUDE.md editing |
| Codex | codex |
Sandbox & approval modes | Skills & MCP browsers, experimental-feature toggles |
| Grok Build | grok |
Default · AcceptEdits · Auto · DontAsk · Bypass · Plan | xAI’s official CLI; sign-in card; official-CLI verification |
| OpenCode | opencode |
Auto-approve toggle | Open-source, provider-agnostic; worktree-aware history |
| Kimi Code | kimi |
Default · YOLO · Auto · Plan | Moonshot AI’s CLI; sign-in card; initial prompt not supported by its TUI |
Enable Agents
Pick the agents you use under Preferences → Agents. The default is Claude Code + Codex, so existing setups are unchanged; at least one agent always stays enabled. Server and workspace pages only render sections for enabled agents, and health checks only probe enabled agents — so agents you don’t use cost nothing.
Disabling an agent hides its sections and history but deletes nothing — re-enable it and cached sessions reappear. An agent with a live persistent or parallel session keeps its section visible even while disabled, so you can always get back to running work.
Install & Health Checks
The server detail page shows an install section per enabled agent: detected version, one-tap Install/Upgrade using each vendor’s official installer, and an optional custom binary path. Detection also looks in the common install locations (~/.local/bin, ~/.grok/bin, ~/.opencode/bin, ~/.kimi-code/bin, ~/.npm-global/bin) — so a freshly installed CLI is found even when its PATH line only lives in an interactive-shell rc file.
The community "superagent" grok-cli installs a binary that is also called grok. ServerCC verifies the version output of the official xAI CLI and treats the community CLI as not installed.
Sessions: History, Resume, Reconnect
The workspace landing page shows a history tab per enabled agent. Tap any row to resume that exact conversation — ServerCC resolves each agent’s own session store (Grok Build’s on-disk session files, OpenCode’s CLI session list, Kimi Code’s session index) and resumes by session ID, not "most recent". After a connection drop, non-persistent sessions continue the workspace’s latest conversation; tmux-backed persistent sessions reattach exactly and also work with all five agents.
OpenCode’s history is project-scoped and includes sessions started in worktrees. One limitation: session history for Grok Build and Kimi Code is read from their default home directories — a custom GROK_HOME/KIMI_CODE_HOME exported only in shell rc files is not picked up.
Permission Modes
Each workspace remembers a launch permission mode per agent, set in workspace settings. Grok Build supports Default, AcceptEdits, Auto, DontAsk, Bypass, and Plan; Kimi Code supports Default, YOLO (auto-approves regular tools, still asks for sensitive files), Auto (fully unattended), and Plan; OpenCode has an auto-approve toggle. Unattended modes show a risk confirmation before they can be enabled.
Signing In from Your Phone
When an agent prints a sign-in URL in the terminal — Grok Build’s device-auth flow (x.ai), OpenCode’s OpenAI sign-in, or Kimi Code’s device-code flow — ServerCC detects it and shows a login card: tap to open the URL in the browser, finish there, and return to the session. Note that OpenCode removed Anthropic OAuth in 1.3.0 — use an API key or another provider with OpenCode.
MCP & Skills
The MCP server browser works with all five agents — ServerCC reads and writes each agent’s own config format (Grok Build’s config.toml, OpenCode’s opencode.json, Kimi Code’s mcp.json) and preserves fields it doesn’t know about. The Skills browser currently supports Claude Code and Codex.
What Stays Claude Code-Only
- Agent View & bg sessions — the supervisor-managed parallel dashboard has no equivalent in the other CLIs
- CLAUDE.md editing from the workspace page
- macOS Keychain unlock on session start
FAQ
Can I run OpenCode on an iPhone?
Yes. OpenCode runs on your own server; ServerCC connects over SSH from your iPhone or iPad and gives you a full terminal, session history with exact resume, an auto-approve toggle, and persistent tmux sessions for OpenCode.
Does ServerCC work with the community grok-cli?
ServerCC supports the official xAI Grok CLI (Grok Build). The community "superagent" grok-cli installs a binary with the same name — ServerCC verifies the version output and treats the community CLI as not installed.
Can OpenCode sign in with my Claude (Anthropic) subscription?
No. OpenCode removed Anthropic OAuth sign-in in version 1.3.0 at Anthropic’s request. Use an API key or another provider account with OpenCode — or run Claude Code itself, which ServerCC fully supports.
Why is my initial prompt ignored when starting Kimi Code?
Kimi Code’s interactive TUI has no initial-prompt flag, so ServerCC starts the session without pre-filling the prompt — type or paste it once the TUI is up. History, exact resume, and permission modes all work normally.
See also: Quick Start to add your first server, Sessions for how history and resume work in detail, and Terminal for quick commands and multi-line input.