Cmd. /feedback
Send feedback and diagnostics to Codex maintainers.
Key takeaways
/feedbackcollects feedback and, when requested, diagnostics or logs for maintainers.- Use it right after a reproducible CLI issue while the session context is still fresh.
- Pair it with
/debug-configwhen the issue involves config, policy, or tool availability. - Review what you are comfortable sending and remove secrets from prompts or local files before sharing repro material.
Original Command Declaration
/feedbackOfficial Summary
/feedback collects feedback and, when requested, diagnostics or logs for maintainers.
Usage
/feedbackGood Examples
- Use
/feedbackafter a reproducible CLI issue while the session context is still fresh. - Pair it with
/debug-configwhen the issue involves config, policy, or tool availability.
Similar Commands
| Command | Difference | Choose It When |
|---|---|---|
/feedback | Sends support feedback | You want to report an issue |
/debug-config | Prints local diagnostics | You need to inspect config first |
/status | Shows session state | You need quick runtime facts |
Use Cases
- Reporting TUI issues.
- Sharing diagnostic context for support.
- Capturing bug reports before leaving a failed session.
Cautions
- Review what information you are comfortable sending.
- Remove secrets from prompts or local files before sharing repro material.
Release Basis
- Judgment: first observed mention
- First evidence version:
rust-v0.50.0 - Date (UTC): 2025-10-25
- Release link: https://github.com/openai/codex/releases/tag/rust-v0.50.0
Sources
- Codex slash commands: https://developers.openai.com/codex/cli/slash-commands
- Codex CLI features: https://developers.openai.com/codex/cli/features