# Security

## Supported version

Security fixes are applied to the latest release on the default branch.

## Runtime boundary

- The managed proxy is hard-locked to `127.0.0.1`.
- `DEEPSEEK_API_KEY` is resolved by DeepSeek Harness and passed only through the child-process environment.
- Do not add API keys to `turbo-agent.yaml`, repository files, or issue reports.
- The settings write endpoint requires a same-origin JSON request and caps request bodies at 16 KiB.
- TurboAgent request traces may contain prompts, model responses, tool arguments, and inline image data. Treat `%USERPROFILE%\.dsh\turbo-agent\.turbo-agent\` as sensitive local data.
- Vision images are sent once per candidate and again to the verifier; choose candidate counts with both data handling and API usage in mind.
- Do not expose port `18888` through a public reverse proxy.

## Reporting

Report vulnerabilities privately through GitHub Security Advisories after the repository is published. Do not include credentials or private trajectories.