Isolated agent work
Separate workspaces and Git worktrees reduce accidental overlap between concurrent coding tasks.
Codius security
Local tools, scoped access, and explicit boundaries.
Codius separates the desktop tools that operate on your repository from the model providers that answer inference requests. Its controls are designed around least privilege, organization isolation, and minimal content retention.
Controls
Security properties you can verify.
These statements describe the current application behavior. Codius does not claim certifications or compliance attestations it has not earned.
Scoped API keys
Organization keys grant only selected model-read, inference, and usage-read scopes. They never carry billing or administrator permissions.
Secrets shown once
Codius API-key plaintext is presented only when created. The service stores a verifier rather than the reusable secret.
No inference-content logging
Prompts, outputs, tool arguments, reasoning, and API keys are not written to Codius application logs, analytics, traces, or error-monitoring events.
Organization boundaries
Membership, API keys, usage, billing, and administrative actions are checked against organization ownership and permissions.
Provider separation
Public model identifiers remain stable while model-provider credentials, routing, and economics stay inside server infrastructure.
Data flow
What stays local and what leaves the machine.
- Local
- Repository files, Git operations, worktrees, terminal commands, local agent processes, browser interaction, and desktop session state.
- Model provider
- The prompt, relevant context, tool definitions, and model output required to fulfill an inference request. The destination is the provider selected for that task.
- Codius service metadata
- Organization identity, model selection, token counts, timing, usage totals, request identifiers, error codes, security records, and billing records needed to operate the service.
- Not persisted by Codius
- Inference prompts, responses, tool calls, tool arguments, and reasoning content are processed transiently and are not persisted in Codius application databases or operational telemetry.
Responsible reporting
Report a security concern privately.
Do not include active credentials or sensitive customer data in an initial report.
Contact Codius support
Send a concise description, affected surface, reproduction steps, and potential impact to [email protected]. Reports are reviewed before public discussion.
Inspect the open-source client.
The Codius App repository is public, so local behavior and integration boundaries can be reviewed directly.