Security and data handling

Codius separates local coding tools from hosted inference. Repository and tool operations run in the local desktop and agent environment; model requests go to the provider selected for the task.

What stays local

The following operate on infrastructure controlled by the user:

• repository files and working directories;
• Git operations and worktrees;
• terminal commands and development processes;
• local coding-agent processes and sessions;
• embedded-browser interaction.

What a model provider receives

A selected model provider receives the prompt, relevant context, tool definitions, and output required to fulfill the request. Provider handling is also governed by that provider's contractual and security controls.

Codius inference-content retention

Codius processes prompts, responses, tool calls, tool arguments, and reasoning transiently. It does not persist that inference content in application databases, logs, analytics, traces, or error-monitoring events.

Operational records can include organization identity, model choice, token counts, timing, request identifiers, usage totals, error codes, security records, and billing data needed to operate and protect the service.

API keys

Codius organization keys use an environment-marked codius_live_… or codius_test_… format. Plaintext is shown once. Codius stores a keyed verifier for authentication rather than the reusable secret.

Keys can carry only these API scopes:

API keys never grant billing or administrator permissions.

Reporting a concern

Send a concise description, affected surface, reproduction steps, and potential impact to [email protected]. Do not include active credentials or sensitive customer content in an initial report.