Skip to content

OpenAI Codex

OpenAI Codex

For OpenAI Codex, the cleanest path today is the Agent Skills install. It keeps the workflow agent-native and does not require the MCP connector flow.

If you are doing this from a Paperclip company, use Set up Agent Analytics for your Paperclip company for the company-skill path. Use this page when you need the raw Codex install flow itself.

  • npx available in the environment Codex uses
  • Access to the Google or GitHub sign-in you want to connect when Codex opens browser approval
Section titled “Recommended: install the Agent Analytics skill”
Terminal window
npx skills add Agent-Analytics/agent-analytics-skill

If the installer asks which skill to install, choose agent-analytics for setup and reporting. Choose agent-analytics-autoresearch when you want Codex to run a structured growth loop for experiment candidates.

Then ask Codex:

Set up Agent Analytics for this project. Install it here if needed. Open the browser for me or give me a login link, then wait. I will sign in with Google or GitHub, approve it, and paste back any finish code if you need it. Then create the project, add tracking and key events, and verify the first event.

The skill teaches Codex how to set up tracking, query analytics, inspect project health, and run experiments from the same conversation loop. Browser approval creates or connects the account during setup, so you do not need to prepare an API key first.

Ask Codex:

  • List my Agent Analytics projects
  • How is my-site doing this week?
  • Create an experiment for the signup CTA on my-site

If you have not created your first real project yet, continue with First Project in 5 Minutes.

  • If the skill installs but the setup pauses on approval, complete the browser sign-in and paste back any finish code if Codex asks for it.
  • If you intentionally use the advanced/manual API-key path, check that AGENT_ANALYTICS_API_KEY is present in the environment the agent actually runs in.
  • If npx is unavailable, install the required Node.js runtime first or use the direct API route temporarily.
  • If you need endpoint-level debugging, use the API reference and test with curl.