Stable release· Major · Confirmed
Stable 0.144.5 strengthens dangerous-command detection
The patch catches more forced `rm` forms and gives clearer rejection reasons when a dangerous command is denied.
The safety check now also runs in danger-full-access mode and recognizes additional destructive shell spellings. Rejected commands return a more specific explanation to the model.
Stable release context: 1 official tag was published that UTC day (rust-v0.144.5). The full comparison contains 2 commits and 6 changed files.
Evidence
Stable 0.144.5 expands dangerous-command detection to more forced `rm` forms.Why it matters: Destructive commands are less likely to slip past the literal shell classifier because of alternate flag spellings.
Direct evidence · Confirmed
Supporting sources
- [release/0.144] fix(core) expand is_dangerous_command (#33455) commit · Official
- rust-v0.144.4 to rust-v0.144.5 comparison tag-compare · Official
Conflicting sources
No conflicting sources recorded.
Availability
Availability note: these sources establish repository and CLI release activity. They do not, by themselves, prove that the same changes were live in Codex Desktop.
Availability by surface
| Surface | Status | Claim-level evidence |
|---|---|---|
| CLI | Stable · Documented · General |
|
| Desktop | Unknown · Unknown · Unknown |
|
| IDE | Unknown | No central-claim assertion recorded. |
| Cloud | Unknown | No central-claim assertion recorded. |
| Mobile | Unknown | No central-claim assertion recorded. |