Overview
Summer Cloud is in research preview — early and evolving fast, so the command surface and limits below may change. See the Summer Cloud guide for the full picture.
summer cloud command group syncs Summer Engine projects with Summer Cloud: content-addressed sync for the whole project tree, including big binary assets, with version history and local checkpoints. Run any command without a global install:
summer login (the cloud token lives at ~/.summer/cloud-token). All subcommands accept these shared options:
The engine does not need to be running. If it is, the CLI coordinates with it automatically: it asks the engine to save dirty scenes before a push and rescans changed files after a pull.
summer cloud init
Enable Summer Cloud for a project.summer-cloud.json at the project root with the project’s cloud ID. That file is the only cloud artifact that belongs in Git. Running it again on an already-bound project is a safe no-op.
summer cloud status
Show sync status for the project.summer cloud push
Push local project changes to Summer Cloud.
What it does: Hashes the tracked tree, asks the API which blobs are missing, uploads only those, and commits a new manifest version. If the cloud also has changes, it pulls them first so the pushed version reflects a converged tree. If another machine commits while the push is in flight, the push automatically re-diffs against the new head and retries.
If
summer-cloud.json contains a pinnedVersion (read-only checkout for CI), push refuses with an explanatory error.
summer cloud pull
Pull Summer Cloud changes into the local project.
What it does: Downloads needed blobs to a staging area, verifies the sha256 of every downloaded file, writes a local checkpoint before touching any existing file, then applies changes with atomic renames. An interrupted pull is safe: rerunning it resumes and converges.
Bootstrap: the first sync on a machine where both the local tree and the cloud have files (for example, right after a Git clone of a cloud-enabled project) stops and asks you to choose.
merge converges files with identical content automatically and treats the rest as normal conflicts; keep-cloud checkpoints divergent local files before replacing them; keep-local makes your tree the next cloud version.
summer cloud restore
Restore a retained cloud version, or roll the local tree back to a pre-sync checkpoint.
Note on checkpoint restore: it restores file contents but does not delete files a later sync added; the command lists those extra files so you can remove them yourself.
summer cloud checkpoints
List local pre-sync checkpoints.summer cloud restore --checkpoint accepts. The last 20 checkpoints are kept per project.
summer cloud conflicts
Inspect and recover conflict sets.
What it does: When concurrent edits collide, the cloud version wins the path and the losing local bytes are preserved under
.summer/local/cloud/conflicts/. conflicts lists those sets; conflicts restore writes a preserved file back into the project. Run summer cloud push afterwards to make it the new canonical version.
MCP Tools
Every subcommand has a 1:1 MCP tool (summer_cloud_init, summer_cloud_status, summer_cloud_push, summer_cloud_pull, summer_cloud_restore, summer_cloud_checkpoints, summer_cloud_conflicts) so agents can run the same operations. See the Tools Reference.
Next Steps
Summer Cloud Guide
What syncs, how conflicts work, storage plans, and .summercloudignore
CLI Reference
All other summer commands: setup, doctor, run, create, and more
Need help or have questions? Reach out to our founders at founders@summerengine.com or join our community on Discord for fast responses.