Administer and secure Colossus¶

Colossus treats model calls, filesystem access, processes, network traffic, durable state, and extensions as separate operational concerns. A provider being connected does not grant it access to a repository, and an approval does not widen the sandbox.

Start with the operational layer that matches your job:

• Colossus home and workspace resolution for per-user state, configuration selection, and repository instructions.
• Configuration recipes for a safe, inspectable baseline.
• Providers and routing for hosted or local models.
• Access and approvals for tool visibility and effect decisions.
• Policy and OPA for local or remote authorization.
• Sandbox for filesystem, process, and network containment.
• Storage and worker for the canonical journal and multi-client use.
• Audit, telemetry, and recovery for evidence and incidents.
• Offline operation for isolated environments.
• Troubleshooting for a symptom-first diagnostic path.

The Reference section owns exact fields, action names, schemas, limits, and command surfaces. These operator pages explain how to combine those contracts safely.