Cmd. /personality
Choose the response communication style for the current Codex thread.
Key takeaways
- Choose the response communication style for the current Codex thread.
- Check the input surface and availability before using the examples below.
Purpose
Choose the response communication style for the current Codex thread.
/personalityAvailability
| Field | Value |
|---|---|
| Input surface | Running CLI prompt |
| Kind | Built-in |
| Status | Conditional |
| Aliases | — |
| Documented minimum | Not specified |
| Reviewed against | 2026-09-22 · Codex CLI 0.155.1 |
Requires a model supporting personality settings; use the picker for friendly, pragmatic, or none.
Examples
/personalityWhen to use it
- Set
pragmaticfor concise engineering work. - Set
nonewhen team instructions already define the exact communication style.
Choosing related commands
| Command | Difference | Choose It When |
|---|---|---|
/personality | Changes communication style | Output tone or directness needs adjustment |
/model | Changes model behavior more broadly | Quality or capability needs a different model |
/status | Shows current state | You need to confirm settings |
Effects and persistence
Selects conversational style without changing model capability or tool permissions.
/personality changes how Codex communicates without rewriting the prompt. Current documented
styles include friendly, pragmatic, and none.
Run /personality, then choose friendly, pragmatic, or none in the picker. These are documented picker values; the reference does not specify inline arguments.
Cautions
- Codex hides this command when the active model does not support personality-specific instructions.
- Do not use personality to override safety or policy instructions.
Official sources
Complete command list · Verification scope · History for this command