Duo-node Logo
|
RJS-Software Labs Logo
v1.0.0

Get Omnipotent

Download the pre-built binary for Apple Silicon, build from source, or grab the latest release.

macOS

Apple Silicon (arm64)

Pre-built binary for M1/M2/M3/M4. Extract, add to PATH, and run omnipotent init.

Download .tar.gzv1.0.0

Linux

x86_64 + ARM64

Standalone binary. Extract, add to PATH, and run omnipotent init.

Source Build

Rust + Cargo

Clone the repository and build from source using the Rust toolchain.

git clone https://github.com/RJS-SOFTWARE-LABS/omnipotent.git cd omnipotent/tools/omnipotent-cli cargo install --path . omnipotent init omnipotent up omnipotent tutorial
View Source on GitHub

Documentation

Everything you need to get started.

Questions

Frequently Asked

No. Omnipotent is an Agentic Runtime — a living workflow modeled after OS architecture. It runs on top of your existing OS using Docker containers. Think of it as a team of AI specialists that live on your hardware, with their own nervous system, memory, and coordination protocols.
Docker 24+ and Rust/Cargo on macOS, Linux, or Windows (via WSL2). As little as 5 GB RAM works in Minimal mode; 12 GB+ unlocks the full stack. No paid subscriptions, no specific editor, no cloud dependency.
Those are tools — they live in your editor with no persistent memory. Omnipotent is a runtime with 12 specialized agent roles, tiered memory that compounds over time, and self-correcting protocols (including the Void Mirror retrospective). It doesn't assist you — it works alongside you.
Only if you explicitly move it through the Airlock. The Diplomat agent syncs alliance (team) data via git, but it has no access to your sovereign (private) plans. Local-first by design.
The core runtime is free to use — bring your own LLM API keys. Pro and Scale tiers add managed memory, priority support, and federation features. The Mana budget system tracks token costs so you always know what you're spending.
Yes. The Federation Protocol lets you share plans and collaborate through a git-based commons repo, while keeping private work strictly local. Branch locking and worktree isolation prevent conflicts.