Crucible Preview

Documentation

Git workspaces

Create, open, clone, publish, commit, and sync Git-backed workspaces.

Equal peer provider

Git workspaces are first-class. Checked-out deterministic JSON files are the source of truth. They work offline and never require Crucible Cloud. Cloud remains Planned.

Layouts

  • Root — workspace files at the repository root.
  • Embedded — workspace under .crucible/workspace/ inside an application repository.

Create, open, clone, publish

Create a new Git workspace, open an existing Crucible layout, clone a remote, or Publish Local as Git (copies into a new Git workspace; the Local source is unchanged).

Save vs Stage vs Commit vs Push

  1. Save writes canonical workspace files — it never commits.
  2. Stage / Unstage updates the index for Crucible paths.
  3. Commit creates local history — it never pushes.
  4. Fetch / Pull / Push sync only when you ask. Pull is fast-forward-only. There is no force push and no automatic merge, rebase, or stash.

Status, diff, branches, remotes

Inspect staged and unstaged changes with unified diff, browse local history, switch and create branches, manage remotes, and review ahead/behind after fetch.

System Git

Requires system Git 2.39+. Uses your credential helpers or SSH agent. See Installing Git.

Conflicts

Resolve with external Git tools, then refresh Crucible. Unsafe Save, switch, pull, and commit stay blocked until conflicts clear.

See also Git CLI and CI.