System Architecture
Learn how the CLI, December Cloud, and sandboxes work together.
This page helps you understand where December runs and how its parts work together.
System overview
You can use December in two places: in your terminal with the CLI, or in the browser with December Cloud. December has three parts:
The CLI
Runs on your computer and works on your local files.
December Cloud
Keeps your account and sessions, and runs the agent for web sessions.
Sandbox
A cloud Linux machine that runs your code and your app preview.
The CLI
The CLI runs on your computer, in your project folder. December reads and edits your files directly. It runs commands in your local shell.
The CLI sends your prompts to the model that you connect with /login. That can be your own keys, a plan, or your December account. December Cloud is involved only if you sign in with your December account.
December Cloud
December Cloud is the web app at app.trydecember.com. For each session, December Cloud starts a sandbox. If you connect a GitHub repository, December clones it into the sandbox.
In a web session, the agent runs on December Cloud servers. The agent sends each command and file edit to the sandbox. The sandbox runs them and sends back the result.
December Cloud saves each step of a session to its database. If a server stops during a session, another server can continue the session from the last saved step.
Sandboxes
A sandbox is a cloud Linux machine for one session. Your code, your dev server, and your shell commands run in the sandbox, not on your computer.
When your app listens on a port, December shows it in the preview. For more information, see Live Sandboxed Previews.
Each user can have 3 active sandboxes. If you start a fourth, December pauses the sandbox that you used least recently. December can resume a paused sandbox later.