GET STARTED
Get the CLI.
Inspect your runtime.
Start with the open-source CLI. Build from source or use the Debian CLI-only bootstrap, then check what your machine needs to run Cella.
Prefer the docs? Open Quick StartThese steps obtain a local CLI and run read-only checks. Signed-bundle setup is implemented, but a published production-signed release is not available. The complete coding-agent workflow is still in development. No provider API key is needed.
Build the CLI
Clone Cella and build the CLI package using the repository’s pinned Rust toolchain.
git clone https://github.com/ryuux05/Cella.git
cd Cella
cargo build --locked -p cella-cliAlternative: Debian 13 x86-64 · CLI without a compiler
No Rust or C compiler is needed for this CLI-only bootstrap.
mkdir -p ~/src
git clone https://github.com/ryuux05/Cella.git ~/src/Cella
cd ~/src/Cella
./install.sh --check
./install.sh
. ~/.bashrc
cella --version
cella setup --planRun this as your ordinary user, without sudo, outside /opt/cella. The script verifies the bundled unsigned alpha CLI against its checked-in SHA-256 and installs only ~/.local/bin/cella. It installs no daemon, Wall, runtime, identities, images, or systemd units. setup --plan is read-only and should report that release installation is not authorized. This bootstrap does not enable init or shell.
Use cella instead of ./target/debug/cella in the next two steps after this alternative.
Verify the build
Check the version, build information, and available commands from the repository root.
./target/debug/cella --version
./target/debug/cella info
./target/debug/cella --helpInspect readiness
See which host and runtime prerequisites are missing. This check does not install or change anything.
./target/debug/cella doctor --wallMissing prerequisites and a nonzero exit are expected before runtime setup. This check does not certify protection.
Choose your next step.
The CLI is the starting point. Explore the commands, follow a concrete example, or work through the Debian runtime candidate.
Debian is the first runtime target. The offline candidate is a smoke-test path; the full protected agent workflow remains in development. Read implementation status →