Install BugMojo in ChatGPT and Codex
One plugin package serves both surfaces: add it to Codex from our marketplace, or connect BugMojo in ChatGPT as a connector.
Codex — from the BugMojo marketplace
codex plugin marketplace add viveksinra/bugmojo
codex plugin add bugmojo
codex mcp login bugmojo # OAuth in the browserCodex clones the repository and reads the marketplace manifest at its root, the same way Claude Code reads its own. The plugin brings the shared BugMojo skills, a single MCP server pointed at the hosted endpoint, and a session-start hook that prints the working agreement.
Codex — MCP server only
codex mcp add bugmojo --url https://www.bugmojo.com/api/mcp
codex mcp login bugmojoChatGPT
Open Settings → Connectors in ChatGPT and choose to add a connector.
Enter the BugMojo MCP URL:
https://www.bugmojo.com/api/mcp— add?mode=qaif you want the run and plan tools.Complete the browser OAuth prompt ChatGPT opens.
Ask about a bug by its key, or ask what to test next. BugMojo's tools appear in the conversation.
The same package is submitted to the OpenAI plugins directory; once a listing clears review, installing from the directory is equivalent to the marketplace path above.
Teach the repo, not just the client
Codex reads AGENTS.md. Running bugmojo init writes an idempotent managed block into it — plus CLAUDE.md, .github/copilot-instructions.md and the Cursor and Gemini equivalents — so every agent that opens the repository learns the same working agreement.
npx @bugmojo/cli init --client codexThe block is delimited by markers, so re-running init updates it in place and never touches the rest of the file. It also patches playwright.config.* to add the reporter when one exists.
Headless and CI
BUGMOJO_API_KEY=bm_key_... npx -y @bugmojo/mcp-serverCommon questions
Is this one package or two?
One. Since the OpenAI plugin format unified, a single root manifest serves ChatGPT as an app and Codex as a CLI plugin, sharing the same skills.
Why install from your marketplace instead of the directory?
The marketplace path works today and needs no directory review. The directory listing is the same package, just gated on submission review.
Does the session-start hook need my credentials?
No. It prints the BugMojo working agreement, makes no network call and reads no credentials, so it is safe to install before you log in.
Can Codex work without a browser login?
Yes, for the bug-reading surface: use the API-key stdio shim. The plan and evidence tools need the hosted endpoint.
Related articles
- Install BugMojo in Claude CodeInstall the plugin, finish the browser login, and get nine skills, four subagents and three hooks inside your terminal.
- Install BugMojo in CursorOne click from the install deeplink, or a four-line mcp.json — plus a rule that only loads when you are in test code.
- Install BugMojo in GitHub CopilotOne command in VS Code, plus the API-key path the cloud coding agent needs — because it cannot do a browser login.
- MCP tool referenceKnow exactly which tools a connected AI agent can call over MCP to read a BugMojo bug and act on it.

