Cmd. /cd

Purpose

Track the 0.149.0 working-directory commands and verify their live behavior in the installed slash-command help.

/cd <path>

Availability

This entry is absent from the current command table or tracked separately through releases. Check the evidence and installed build.

Examples

/cd ../shared

When to use it

1. Inspect /cd in the installed slash picker before moving a live monorepo task.
2. Inspect /pwd and /cwd separately and record the reported cwd before resuming or queueing work.

Choosing related commands

Effects and persistence

Changes the session's working directory. From 0.160.0, moving to a folder without a saved trust decision asks for folder trust and offers "Keep current directory" to cancel. Check the resulting path and project settings.

The 0.149.0 release note says /cd, /pwd, and /cwd manage the working directory. It does not document each command's exact syntax, output, or alias relationship, and the current Developer Commands reference has not caught up. In a 0.149.0+ build, open the slash-command picker and follow its inline signature before moving a live task.

Cautions

• Prefer an absolute path when ambiguity matters; the current reference does not publish relative-path resolution details.
• Moving directories does not bypass trust or managed deny-read policy.
• From 0.160.0, moving to a folder without a saved trust decision asks for folder trust; choosing "Keep current directory" cancels the move. Codex rechecks running tasks and background terminals before switching and enforces the destination's permission requirements.
• On 0.151.0+, regression tests should confirm the same deny-read and writable-root boundaries before and after /cd.
• A new project's AGENTS.md becomes an instruction source only after the project is trusted.
• Do not automate against a presumed /pwd or /cwd output format until the reference documents it.

Official sources

• Changelog
• Developer Commands
• Rust V0.160.0

Complete command list · Verification scope · History for this command