Skip to main content

OpenAI Codex Setup

OpenAI Codex is the main ChatGPT-based MCP client that Automation Agent for Adobe Premiere currently supports with a low-friction guided setup.

This page is for the Codex / Claude Code mode in the Automation Agent panel, which uses the panel-managed local HTTP MCP server.

What You Need​

For the best Codex workflow, two things need to be true at the same time:

  1. the local Automation Agent MCP server is available
  2. Codex has an MCP server entry for Automation Agent
  3. the Automation Agent Codex skill is installed

Starting MCP alone is not enough. Without the MCP config, Codex cannot reach the local server. Without the skill, Codex can still talk to MCP, but it will usually make weaker assumptions about discovery, validation, and Premiere-specific authoring.

Best Setup Path​

The preferred setup path is from inside the Automation Agent panel:

  1. open the MCP Server tab
  2. start or connect MCP
  3. open the Agent Setup section
  4. use Configure MCP
  5. use Install Codex Skill
  6. restart Codex
  7. return to the panel and verify the status

Important:

  • use the panel in Codex / Claude Code mode
  • that mode uses the panel-managed HTTP MCP server
  • this is different from Claude Desktop Chat, which uses a client-launched local stdio runtime

Where The MCP Config Lives​

Codex MCP configuration is stored in:

~/.codex/config.toml

The relevant Automation Agent entry looks like:

[mcp_servers.automation_blocks]
url = "http://127.0.0.1:53125/mcp"

What The Installer Writes​

The Codex skill is installed to:

~/.codex/skills/automation-agent/

That folder should contain:

  • SKILL.md
  • agents/openai.yaml
  • references/...

If Codex Was Already Open​

Restart Codex after installing or updating the skill. Otherwise it may continue using the previous state or fail to pick up the skill at all.

If The Panel Says The Packaged Skill Is Missing​

That usually means the current plugin build does not include the generated Codex skill export yet.

In development, rebuild the product assets and the plugin package, then reopen the panel.