Nucleus 0.4.0-alpha

Install Nucleus

Your hardware. Your cloud.

Let Claude or Codex install it for you

Give these instructions to your coding agent to install the current Nucleus alpha.

Download agent instructions (.md)

Alpha 0.4 adds an explicitly configured CPU model worker for approved text models. Positronic, powered by Nucleus, provides model controls, shared organization documents, and scoped API and MCP access. Enrollment, resource telemetry, and node pairing remain available.

These packages run on Linux and WSL2. Go and Python are not required to run the included binary.

Choose your Linux architecture

Run uname -m in your Linux or WSL2 terminal to check.

x86_64

Linux AMD64

For 64-bit Intel and AMD machines, including WSL2 on x86_64.

Download AMD64 0.4.0-alpha · .tar.gz archive

aarch64 / arm64

Linux ARM64

For 64-bit ARM Linux machines.

Download ARM64 0.4.0-alpha · .tar.gz archive

Download the checksums

Save your archive and SHA256SUMS in the same directory. The first command below checks the archive. Continue when it reports OK.

Download SHA256SUMS

Verify, extract, and initialize

Run the matching commands from the directory containing your downloads. On Windows, use a WSL2 terminal.

AMD64 commands 
sha256sum --check --ignore-missing SHA256SUMS
tar -xzf nucleus-0.4.0-alpha-linux-amd64.tar.gz
./nucleus-0.4.0-alpha-linux-amd64/bin/nucleus init --name workstation
./nucleus-0.4.0-alpha-linux-amd64/bin/nucleus help
ARM64 commands 
sha256sum --check --ignore-missing SHA256SUMS
tar -xzf nucleus-0.4.0-alpha-linux-arm64.tar.gz
./nucleus-0.4.0-alpha-linux-arm64/bin/nucleus init --name workstation
./nucleus-0.4.0-alpha-linux-arm64/bin/nucleus help

Initialization creates a persistent identity for this installation. It does not join another machine automatically.

Connect to Positronic

Positronic is the paid managed service powered by Nucleus. For optional managed enrollment, use the installed CLI from a shell where nucleus is on your PATH.

Manage your organization at positronic.app/dashboard. The CLI address below remains the supported enrollment endpoint.

1. Request enrollment

nucleus cloud connect --url https://nucleus.parallax.link/dashboard

Open the approval link, sign in with Nexus, and choose your organization. An owner or administrator must compare the machine fingerprint shown in the browser with the CLI before approving.

2. Send resource telemetry

nucleus cloud run

After approval, keep this command running in the foreground. It does not install a background service.

For connection details and an optional systemd service, read the hosted installation guide.

Configure a model worker

Model serving requires a locally configured CPU runtime and approval for the catalog’s exact model artifact. Enrollment and telemetry alone do not start model serving.

Give the versioned agent instructions to your coding agent, or follow the hosted worker guide. Review the model license and provenance before approving an installation. Both paid Positronic plans include model serving and shared organization context; dedicated server charges are separate.

Connect across networks with NEBULA

NEBULA 0.6 preview is a standalone CLI for Linux and WSL2. Manage machine identities and fabric membership, connect across networks, and read your hosted organizations and clusters. Kubernetes provisioning is not included in this preview.

Download checksums · Read the CLI guide · Open NEBULA

To connect across networks, pair your machines, enroll them in the same paid Positronic organization, and enable relay access for each machine. Start the owner first, then its members. From the extracted NEBULA folder:

./bin/nebula network connect --no-open

Keep this running separately from hosted telemetry or model workers. Your machines make outbound HTTPS connections; they need no public listener or root account.

Connect two machines

Pair your nodes

Use the same build on both machines and initialize each with a distinct name. Transfer pairing documents through a trusted channel.

Read the pairing instructions
  1. The owner creates an invitation with its private LAN endpoint.
  2. The joining machine returns a signed request.
  3. The owner inspects the request, confirms the node identity, and accepts it.
  4. The joining machine accepts the returned grant.

The owner uses an explicit private IPv4 address. Members connect outbound over mutually authenticated TLS; each resource map is available on that machine’s loopback interface.