Codex CLI for bug bounty
Codex CLI takes a custom model provider from one block in ~/.codex/config.toml. It calls the Responses API, so the provider must serve /responses.
Setup
model = "kimi-k3.1-pro-uncensored"model_provider = "silkcompute" [model_providers.silkcompute]name = "Silk Compute"base_url = "https://api.silkcompute.com"env_key = "SILK_API_KEY"wire_api = "responses"Source: Codex CLI docs. Read November 18, 2026.
Steps
- Edit the user config
A project-level .codex/config.toml cannot set providers.
- Keep wire_api = "responses"
The reference lists it as the only supported value.
- Export the key
env_key names the variable Codex reads.
- Run codex
It starts on the model you set.
Use it in a hunt
| Job | Ask |
|---|---|
| Draft a report | Turn notes/finding-3.md into a Bugcrowd submission with overview, walkthrough, evidence and demonstrated impact. |
| Check a draft | List every claim in reports/draft.md that notes/finding-3.md does not support. |
| Tidy notes | Group the endpoints in notes/ by host and write one file per host. |
Provider guide: Silk Compute Codex CLI setup.