This file is the repository-level security entry point. Package-specific behavior and data boundaries are maintained with the package that owns them:
Never commit or submit an API key, token, full request header, unredacted configuration, plaintext credential, or unrelated private source. If a credential has been exposed, revoke or rotate it with the provider before doing anything else.
Public issues should contain only the shortest redacted evidence needed to identify the affected component and failure boundary. Do not use a public issue for a report that cannot be described without exposing a live secret or private data.
| Component | External data boundary | Local authority |
|---|---|---|
| Codex DeepSeek Subagent | The delegated assignment and returned tool context are sent to the configured DeepSeek endpoint | A trusted SubagentStart Hook briefly stages plaintext in local user state; the child defaults to read-only, but current Codex permission inheritance can affect the effective sandbox |
| Pi DSH Mimic | For model ids containing deepseek-v4-pro, the task, conversation context, and tool results are sent through the provider selected in Pi |
The extension runs with the Pi process's permissions and contributes a str_replace_editor that can create and modify files |
| MixAgents Broker | The explicit assignment, included context, file content read by the worker, and tool results may be sent to the selected route's provider | The local MCP server starts route-scoped Codex App Server runtimes; managed workers use the supplied workspace under a configured read-only or workspace-write sandbox, while App Server owns their thread history and turn effects |
A local sandbox is not a confidentiality boundary: content sent to a model crosses the configured provider boundary even when filesystem mutation is disabled.
Provider usage is billed independently from an OpenAI or ChatGPT subscription. Repository installation and offline tests must not make paid model calls. Explicit smoke tests and model runs may incur charges and must identify the provider data boundary before execution.