Add support for all of the Codex’s built-in slash commands

[pygarap]

Codex’s built-in slash commands, during an interactive session:

Command	Purpose
/model	choose what model and reasoning effort to use
/approvals	choose what Codex can do without approval
/review	review my current changes and find issues
/new	start a new chat during a conversation
/init	create an AGENTS.md file with instructions for Codex
/compact	summarize conversation to prevent hitting the context limit
/diff	show git diff (including untracked files)
/mention	mention a file
/status	show current session configuration and token usage
/mcp	list configured MCP tools
/logout	log out of Codex
/quit	exit Codex
/feedback	send logs to maintainers

---

[benbrandt]

Hi @pygarap thanks for the list, here's the current thinking:

• /model: there is a model selector in zed. We will stabilize this api for other clients
• /approvals: isn't this achievable with the mode selector?
• /review should work (we introduced various flavors to achieve the same behavior)
• /new : cmd + n to create a new thread
• /init: supported
• /compact: supported
• /diff: you can view your git diff in the built in diff editor
• /mention: built-in to zed with the @mentions
• /status: not currently supported
• /mcp: not currently supported
• /logout: supported
• /quit: not sure why you need this as the ACP client should quit the program
• /feedback: not supported

Basically we tried to implement the ones we could at the moment that didn't have an analog when running inside another client. Hope that helps.

[codehd7]

Hello Ben, /status would be useful to ensure I'm connected to the right account, i.e. my employer has a legal setup where I can use AI on confidential code but only when logged into that account. So I'd like to be able to verify that with /status.

[n4dinuh]

Hello there @benbrandt!

When invoking the /compact command I obtain the following:

{"jsonrpc":"2.0","id":8,"method":"session/prompt","params":{"sessionId":"<session-id>","prompt":[{"type":"text","text":"/compact"}]}}
{"jsonrpc":"2.0","id":8,"result":{"stopReason":"end_turn"}}

The <session_id> here is just a placeholder btw.

There is no indication of:

• Whether compaction actually occurred (e.g. "Context compacted" as in the CLI, or a summary)
• How much context was freed up (also here the /status would have been helpful)

Is this expected behavior? Since /status isn't currently supported, is there another way to verify the compaction occurred?

[benbrandt]

Hi this is the (currently) expected behavior. If it didn't work you'd see an error. We are working on better ways to report status updates like this in the future.