Cmd. /stop
Stop all background terminals owned by the current Codex session.
Key takeaways
- Stop all background terminals owned by the current Codex session.
- Check the input surface and availability before using the examples below.
Purpose
Stop all background terminals owned by the current Codex session.
/stopAvailability
| Field | Value |
|---|---|
| Input surface | Running CLI prompt |
| Kind | Built-in |
| Status | Current reference |
| Aliases | /clean |
| Documented minimum | Not specified |
| Reviewed against | 2026-09-22 · Codex CLI 0.155.1 |
The installed command menu and account or organization settings determine availability.
Examples
/stopWhen to use it
- Run
/psfirst, then/stopwhen a watcher or long test is no longer needed. - Use
/stopbefore leaving a session that started background work.
Choosing related commands
| Command | Difference | Choose It When |
|---|---|---|
/stop | Cancels background terminal work | Session-owned commands should stop |
/ps | Lists background terminal work | You need to inspect before stopping |
/exit | Exits the CLI | You are done with the session itself |
Effects and persistence
Stops active background work in the current session.
/stop stops all background terminals for the current session. /clean remains available as an
alias.
Cautions
/stoptargets Codex background terminal work. It does not guarantee cleanup of unrelated external processes.- Inspect with
/psbefore stopping when there is any doubt.
Official sources
Complete command list · Verification scope · History for this command