∞
Duo-node Logo
|
RJS-Software Labs Logo

Getting Started

Go from zero to a running Sovereign runtime in under five minutes. Two paths: Docker (recommended) or the Rust CLI binary.

Prerequisites

RequirementVersionCheck
Docker Desktop24+docker --version
Docker Composev2+docker compose version
Git2.30+git --version
Node.js20+node --version

Optional (for the Rust CLI binary):

RequirementVersionCheck
Rust1.70+rustc --version
Cargo1.70+cargo --version

Option A: Docker Sandbox (Recommended)

Everything runs inside Docker containers. Nothing is installed on your host system outside the repo directory.

  1. Clone the repository

    Download the source from the releases page
cd omnipotent

  2. Boot the runtime

    ./scripts/docker-dev.sh

    This starts the Sovereign runtime stack. You will see containers spinning up for the Kernel, Signal Bus (Redis), and Soul Journal (pgvector).

  3. Open the dashboard

    Navigate to http://127.0.0.1:18080 in your browser. The Kernel Dashboard shows agent status, memory tiers, and the Signal Bus feed.

ContainerPortPurpose
omnipotent-archon127.0.0.1:18080Kernel Dashboard + noVNC
omnipotent-archon127.0.0.1:15900Native VNC
omnipotent-busInternal onlyRedis Signal Bus
omnipotent-soul-journalInternal onlypgvector (Cold Memory)
Port overrides: Set OMNI_WEB_PORT and OMNI_VNC_PORT environment variables before running the script to change default ports.

Option B: Rust CLI Binary

If you have Rust installed, you can build and install the CLI directly.

  1. Build and install

    cd tools/omnipotent-cli
cargo install --path .

  2. Initialize a new Sector

    omnipotent init

    This bootstraps the .realm/ directory structure with default Sovereign configuration.

  3. Boot the Swarm

    omnipotent up

    The CLI wraps docker compose under the hood. Same containers, same dashboard.

First Boot Walkthrough

After the runtime is up:

  1. The Archon (PID 1) wakes first, initializing the Kernel and Signal Bus.
  2. Agents register on the bus and report their status. You will see green check marks in the dashboard as each comes online.
  3. The Oracle loads Hot Memory from .realm/state/context_index.json.
  4. The system is ready. Run omnipotent status (or check the dashboard) to confirm all agents are healthy.
API keys are optional. If you have Claude, Gemini, or other LLM API keys, set them as environment variables. Without keys, the system falls back to local model support where available.

Next Steps