For the complete documentation index, see llms.txt. This page is also available as Markdown.

Codex

Codex reaches Cakewalk through your workspace app — no separate Codex setup. Publish it once for the workspace, connect it in your account, and it is available in the Codex app and the Codex CLI.

Codex does not need its own Cakewalk setup. It uses the workspace app — the same hosted Cakewalk app an admin publishes for ChatGPT. Once it is published and you have connected it in your account, it is available everywhere you use that account, including the Codex app and the Codex CLI.

There is nothing Codex-specific to configure. Set up the Cakewalk workspace app once by following ChatGPT (web), and it appears in Codex automatically.

Requirements

  • A ChatGPT Business, Enterprise or Edu workspace with the Cakewalk app published by an admin (see ChatGPT (web)).

  • Your own Cakewalk account — each person connects the app individually and sees only the tools their own Cakewalk Connections expose.

  • A ChatGPT account signed in to Codex (codex login) for the CLI.

Setup

  1. An admin publishes the Cakewalk app to the workspace — one time, described on the ChatGPT (web) page.

  2. In ChatGPT (or the Codex app), open Plugins, find the Cakewalk app, and connect it. Sign in with your own Cakewalk account and approve.

  3. That's it. Because the connection is account-level, it now works in ChatGPT (web and desktop), the Codex app and the Codex CLI — no per-surface setup or extra sign-in.

Where It Appears in Codex

  • Codex app: the Cakewalk app shows under Plugins as Connected. Select it in a session and its tools are available.

  • Codex CLI: the tools are available in a codex session, exposed as codex_apps.<app-name>.…. Start a session and ask a Cakewalk shaped question, for example "Which Cakewalk tools do you have available?"

The Cakewalk app will not appear in codex mcp list. That command lists local MCP servers, and the workspace app is an account-level plugin, not a local server. This is expected — the tools still work inside a Codex session.

Verifying It Works

Start a Codex session (in the app or the CLI), select or mention the Cakewalk app, and ask it to list the tools it can use through Cakewalk. The tools your own Cakewalk Connections expose appear in the response. In Cakewalk, the connection shows on My Agents and flips to Connected after the first agent call.

Troubleshooting

  • The Cakewalk app is not in Codex at all: it has to be published by a workspace admin first, and connected once in your account (ChatGPT or the Codex app → Plugins → connect). Until you connect it in your account, Codex has nothing to use.

  • You looked in codex mcp list and it is not there: expected — the workspace app is a plugin, not a local MCP server, so it never appears in that list. Check inside a codex session instead.

  • A tool call fails with an approval error in a non-interactive run (codex exec): a Cakewalk Require approval Policy fired, and non-interactive runs cannot show the prompt. Run the request in an interactive codex session, where the inline prompt appears, or ask your Admin about the Policy on that tool.

  • You see the app but no tools: you see only the tools your own Cakewalk Connections expose. If a tool you expect is missing, connect that integration in Cakewalk.

Learn more

Last updated

Was this helpful?