SeaShell Cloud is the optional commercial control plane for SeaShell. It manages accounts, entitlements, release manifests, and allowlisted telemetry, while the agent keeps running on your machine with your own model keys. By design the control plane never requires repo contents, prompts, diffs, terminal output, local indexes, embeddings, model outputs, provider request bodies, file paths, filenames, or credentials.
What the control plane does
SeaShell Cloud is split into three services: a cloud API for accounts, entitlements, releases, devices, sync, and telemetry intake; a model router for optional hosted routing; and a worker for billing reconciliation, usage rollups, and release validation.
This is the commercial layer around the local agent. It answers questions like is this seat entitled, what is the current stable release, and which devices are registered. It is deliberately separate from the runtime: the local product consumes SeaShell Cloud through published API contracts only, so cloud availability never blocks local work.
What it is designed never to see
The privacy boundary is explicit. Ordinary control-plane operations must not require repo contents, prompts, diffs, terminal output, local indexes, embeddings, model outputs, provider request bodies, file paths, filenames, or credentials.
That list is a design constraint, not a policy promise. Because your source, prompts, and keys are never part of a control-plane request, there is nothing of that kind for the cloud to log, cache, train on, or leak. Privacy is preserved by what the API accepts, not by what a retention policy says will be discarded later.
Telemetry stays allowlisted
Telemetry intake accepts only an allowlisted event envelope. It rejects values that look like prompts, model output, provider bodies, or file paths before they are ever stored.
Install and usage signals move through a narrow, typed contract so product analytics never becomes a backdoor for code or content. Entitlement and usage reads are gated by token in staging; release and installer manifests expose only public, non-entitlement artifact metadata.
Frequently asked questions
- Does SeaShell Cloud see my code or prompts?
- No. The control plane is designed so ordinary operations never require repo contents, prompts, diffs, embeddings, model outputs, provider request bodies, file paths, or credentials.
- Is SeaShell Cloud required to use SeaShell?
- No. The agent runs locally with your own model keys. SeaShell Cloud is the optional commercial control plane for accounts, entitlements, releases, and telemetry.
- What is SeaShell Cloud actually for?
- Accounts and entitlements, release and installer manifests, device registration and sync, optional hosted model routing, and allowlisted telemetry and billing.
- What telemetry does it collect?
- Only an allowlisted event envelope. Values that look like prompts, model output, provider bodies, or file paths are rejected before storage.
Try SeaShell in your terminal
The terminal-native AI coding agent. Free core, single binary.
Install SeaShellRelated guides
Atlas with Gemini 2.0 Flash-Lite in 2026
Explore Atlas with Gemini 2.0 Flash-Lite in 2026. This Google model offers a 1M token context window for just $0.075 per Mtok input, ideal for bulk code analysis and subagent tasks.
Research a Third-Party API Before Integrating It with Atlas in 2026
How to research a third-party API with Atlas in 2026: websearch finds the current docs, webfetch pulls the page as markdown or text, and grep checks repo conventions.
Atlas with GPT-OSS 120B (local via Ollama) in 2026
Explore Atlas with GPT-OSS 120B (local via Ollama) in 2026. Discover its powerful offline reasoning, 131K token context, and self-hosted pricing for secure, high-performance coding.
Atlas with GPT-5.5 in 2026
Explore how Atlas integrates with OpenAI's GPT-5.5, featuring a 1.05M token context window and advanced reasoning for developers in 2026. Understand its pricing and optimal use cases.
Atlas with GPT-5.2 in 2026
Explore Atlas with GPT-5.2, OpenAI's December 2025 refresh. Discover its 400K token context, $1.75 input cost, and how it powers terminal-native AI coding in 2026.
Atlas for Blazor: Terminal-Native AI Coding for .razor Components in 2026
Atlas is a terminal-native AI coding agent for Blazor developers in 2026. Work across .razor components, render modes, and the C# and JS interop boundary safely.
Atlas with GPT-5.1 in 2026
Explore GPT-5.1's 400K context and $1.25/Mtok input pricing with Atlas in 2026. A powerful reasoning model, it integrates deeply with Atlas's agent workflow for developers.
Atlas vs Blackbox AI: Terminal AI Coding Agents in 2026
Comparing Atlas and Blackbox AI in 2026. Atlas offers terminal-native TUI, permission-gated tools, and local embeddings. Blackbox AI features /multi-agent dispatch and VS Code integration.