Nebula requires Rust 1.89 or newer. The CLI is built from source until the first validated public release tag.

• →Rust 1.89 or newer
• →Cargo (included with Rust)
• →Optional: Postgres for registry production validation
• →Optional: S3-compatible object storage for blob persistence

There are no published binary installers yet, so building from source is the only supported install path. Clone the repository and install the `neb` binary onto your `PATH` with Cargo. Note that the repository is currently private — you'll need collaborator access to clone it.

git clone https://github.com/HelixHEX/Nebula.git
cd Nebula
cargo install --path crates/nebula-cli

# Verify it worked
neb --help

If you're developing Nebula rather than just using the CLI, build and run in place instead so you don't need to reinstall on every change.

cargo build --workspace
cargo run -p nebula-cli -- init
cargo run -p nebula-cli -- status

Initialize creates the local `.nebula` metadata directory with all required subdirectories for refs, workspaces, objects, policies, environments, integrations, and secrets.

neb init
neb status
neb diff

The save command scans the working tree, computes content hashes, and records a canonical snapshot with an associated changeset.

neb save --message "Initial implementation draft"

Workspaces isolate work from the main branch. Create one to work on a feature or fix without affecting shared state.

neb workspace create auth-fix --from main
neb workspace list
neb workspace switch auth-fix

Proposals are reviewable protocol objects. They group changesets and track review state before composition into a ref.

neb propose --target main --title "Fix auth redirect"
neb proposal list
neb proposal status <proposal-id>
neb merge <proposal-id>

Nebula supports local file-backed sync bundles. Network registry sync is the next transport layer.

neb remote add origin file:///tmp/acme-app.nebula.json
neb push
neb pull origin
neb clone file:///tmp/acme-app.nebula.json