Cmd. /apps
Browse apps and connectors, then insert app mentions into the prompt.
Key takeaways
- Browse apps and connectors, then insert app mentions into the prompt.
- Check the input surface and availability before using the examples below.
Purpose
Browse apps and connectors, then insert app mentions into the prompt.
/appsAvailability
| Field | Value |
|---|---|
| Input surface | Running CLI prompt |
| Kind | Built-in |
| Status | Current reference |
| Aliases | — |
| 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
/appsWhen to use it
- Use
/appsbefore asking Codex to work with a connector so the app mention is explicit. - Pair
/appswith/permissionswhen the connector exposes actions with side effects.
Choosing related commands
| Command | Difference | Choose It When |
|---|---|---|
/apps | Browses connectors/apps | You need to reference an app in a prompt |
/plugins | Manages plugin bundles | You need skills, apps, MCP, or hooks packaged together |
/mcp | Lists MCP tools | You need to inspect the actual tool surface |
Effects and persistence
Browses and manages available apps. App connection and approval of individual tool actions remain distinct.
/apps browses connected apps and inserts them into the composer as app mentions such as
$app-slug.
Cautions
- An app mention is not a substitute for reviewing tool permissions.
- Connector availability can differ by account, workspace, and installed plugin state.
Official sources
Complete command list · Verification scope · History for this command