Integrations
Install Patronus Security for Codex, Claude Code, and DeepSeek Harness, or use an official API client.
Install the public CLI, connect a supported agent, use an official API client, or call Patronus through Remote MCP. Source and installation contracts are in the Patronus Security CLI repository.
Install the CLI first
Section titled “Install the CLI first”Follow the CLI installation contract on macOS or Linux. It verifies the release and checksum, installs the CLI, and starts onboarding.
For agent-assisted setup, use this prompt:
Set up Patronus Security using https://github.com/patronus-protect/patronus-security-cli/blob/main/INSTALL.mdApprove installation outside the project and complete browser authentication yourself.
Runtime protection
Section titled “Runtime protection”| Integration | Manual setup | Agent installation contract |
|---|---|---|
| Codex | patronus-security-scanner integration codex install | Codex INSTALL.md |
| Claude Code | patronus-security-scanner integration claude install | Claude Code INSTALL.md |
| DeepSeek Harness | patronus-security-scanner integration deepseek install | DeepSeek Harness INSTALL.md |
Verify installed integrations without reading credentials:
patronus-security-scanner integration codex statuspatronus-security-scanner integration claude statuspatronus-security-scanner integration deepseek statusOnly installed hosts need to report enabled. Restart the host or start a new agent session before testing its Patronus status command.
Verify a live session
Section titled “Verify a live session”In Codex or Claude Code, start a new chat and ask the agent to run patronus-security-scanner probe through its shell tool. The command prints only a harmless marker. A protected session returns status=probe_scanned with the scan verdict instead of the raw marker; seeing the raw marker means the result was not withheld. The probe checks the shell-result path of the current session only.
Degraded or inactive messages
Section titled “Degraded or inactive messages”Patronus fails open: when authentication is missing, usage is exhausted, the scanner cannot start, or the API times out, the tool still runs and the agent receives the original result with explicit degraded context. Treat that content as unverified. Unless a message says the content was scanned locally, it was not scanned. Run patronus-security-scanner integration <host> status and patronus-security-scanner auth status, then start a new session.
Official API clients
Section titled “Official API clients”| Language | Install | Agent installation contract |
|---|---|---|
| TypeScript | npm install @patronus-protect/api-client | TypeScript INSTALL.md |
| Python | python -m pip install patronus-api-client | Python INSTALL.md |
| Rust | cargo add patronus-api-client | Rust INSTALL.md |
Continue with the API quickstart for authentication and the first scan. The official clients reference covers file, URL, and MCP scans, errors, idempotent retries, polling, and client options.
Remote MCP
Section titled “Remote MCP”Connect compatible MCP clients directly to https://control.patronus.studio/api/mcp. Authentication uses the same Patronus account and usage allowance as the REST API. See Remote MCP setup.