Skip to main content

atomic clone

Clone a hosted Atomic repository into a new local directory.

Synopsis​

atomic clone <SOURCE> [PATH] [OPTIONS]

Description​

clone creates a complete, independent local copy of a hosted project:

  1. Initializes a new repository in the target directory
  2. Connects to the remote and downloads its changes
  3. Inserts them into the requested view
  4. Configures the remote as origin

<SOURCE> is either a full URL or a project reference that Atomic resolves from your configuration.

Arguments​

<SOURCE>​

Either a full clone URL, or — when it contains no :// — a project reference resolved against your active server profile:

  • <project> — uses your default org and default workspace
  • <workspace>/<project> — uses the given workspace
# Project reference (resolved from config)
atomic clone hello-world
atomic clone demos/hello-world

# Full URL
atomic clone https://acme.atomic.storage/workspaces/demos/projects/hello-world/code

For a reference, the URL is built as {org_base_url}/workspaces/{workspace}/projects/{project}/code, where the org comes from the active profile's default org (falling back to the personal org of your default identity) and the workspace from the org's default workspace (set with atomic workspace set).

[PATH]​

Optional destination directory. Defaults to the project/repository name inferred from the source.

atomic clone hello-world               # → ./hello-world
atomic clone hello-world my-checkout   # → ./my-checkout

Options​

--view <VIEW>​

View to clone and check out (default: dev).

atomic clone hello-world --view main

-k, --insecure​

Skip TLS certificate verification. Use only for testing or self-signed certificates.

--timeout <SECONDS>​

Request timeout in seconds (default: 30).

--download-only​

Download changes into the change store without inserting them into a view. Useful for inspecting changes first; apply them later with atomic insert.

--into-existing​

Bootstrap Atomic inside an existing Git checkout without materializing Atomic content over the Git working tree. Requires a [PATH] pointing at the Git worktree root.

--all-views​

Also clone every other view the remote exposes, not just --view. Each additional view is created locally and populated from the remote. Because changes are content-addressed and shared across views, this mostly adds view references without re-downloading content.

Without this flag, clone fetches only the requested --view, but prints a hint listing the other views available on the remote so you know they exist.

# Clone every view, not just dev
atomic clone hello-world --all-views
Views keep their scope and parent

Each view is cloned from a view manifest carrying its full identity (name, scope, parent, ordered change log, and merkle state), applied with the same primitive as the primary view, so a draft comes back as a draft with its parent chain intact. --all-views walks each view's parent chain and applies parents before children. Requires a server that supports the ?view-manifest endpoint; servers that predate it cannot be cloned from (a hard error, not a lossy fallback).

Examples​

Clone by URL​

# From a hosted project URL (find it with `atomic project list` or `atomic view list --remote`)
atomic clone https://acme.atomic.storage/workspaces/demos/projects/hello-world/code

Clone a specific view​

atomic clone https://acme.atomic.storage/workspaces/demos/projects/hello-world/code --view main

Download without applying​

atomic clone hello-world --download-only
# then, inside the repo:
atomic insert <hash>

Clone all views​

# Reconstruct every view the remote exposes, each fully populated
atomic clone hello-world --all-views
cd hello-world
atomic view list        # shows all remote views, not just dev

Authentication​

Atomic authenticates with your configured identity (an Ed25519 key), not SSH keys or passwords. The identity is inferred from the target server, and a short-lived signed token is minted automatically. Register with a server first:

atomic identity register https://atomic.storage

See atomic identity and atomic server.

After cloning​

cd hello-world
atomic log            # inspect history
atomic status         # working copy state
atomic view list      # available local views
atomic view list --remote   # views available on the remote

By default clone pulls only the requested --view. To bring down every view the remote has, use --all-views, or inspect what's available first with atomic view list --remote.

The remote is saved as origin in .atomic/config.toml, so atomic push / atomic pull work without re-specifying the URL.

See Also​