Documentation Overview

Cella docs

Run agents over time on a remote machine, or use governed Cells for daily development. Start with the CLI and explore the design and current build status.

On this page

Getting started

Start here

Try the CLI. Inspect it. Get oriented.

Use the Debian CLI bootstrap or build from source, verify the binary, and check runtime prerequisites.

Prefer to see the command surface first? Open the CLI reference. For concrete tasks, browse the examples.

Understand the components

A Cell is a controlled execution environment with a continuing identity. Reuse a project Cell deliberately, or create a narrower Cell for a task. The Agent Cell edits a private candidate; a separate Service Cell runs the application. cellad coordinates their authority. Wall contains execution, Gateway executes authorized external operations, and Relay carries scoped Channel traffic.

Read the complete component guide

New to a name? The glossary defines every product term, including Channel, Connection, and Link, with examples and links to the feature contract.

Cells & generations

Cell reuse, long-running agents, focused tasks, and immutable generations.

Gateway & Connections

Exact external Effects without handing provider credentials to the agent.

Channels & Relay

Connect an admitted agent to a named service endpoint through a bounded grant.

Services & secrets

Sealed runtime revisions, approved secret bindings, data grants, and analysis jobs.

Continue with CLI and cellad, Wall and isolation, evidence and Change Capsules, or Link, Engine, and Cloud. For persistent service state, read Data, snapshots, and artifacts.

The complete feature catalog

Every feature from the product catalog, with examples and explicit implementation limits. Browse individual features or read the full guide in one place.

Browse all 22 featuresContainment · durable work · evidence · human operation · Engine and service Read the complete guideConnections, policy, repository transactions, handoff, Capsules, governance, Link, and adoption Follow one WorkstreamHow the components work together from private ingress to reviewed delivery

Research & comparisons

What current developer tools already provide, where Cella overlaps, and what its intended architecture still needs to prove.

VS Code agent controls and CellaSandboxing, permissions, credential masking, enterprise controls, and session handoff · checked October 10, 2026

Go deeper

Debian operator runbookHost installation, enrollment, and offline candidate ordering Canonical command registryImplemented, approved, planned, and deferred command contracts Wall security modelThreats, trust assumptions, and qualification requirements Evidence signingProducer identity, integrity, key custody, and explicit gaps

Read the status labels

Implemented: Present in the current code. Some commands still require administrator-provisioned services.
Development candidate: A bounded implementation path that still needs host validation and qualification.
Approved / planned: A product or architecture contract that is not a released command or complete workflow.

The website’s workflow illustration describes product direction. A successful CLI build or health check does not establish a protected runtime.

Current implementation boundary