# clip.qa for Codex: send bug reports your agent can fix Codex is built to work inside your repo. clip.qa gives it what a repo cannot show: a recording of the bug on a real device, turned into steps, screenshots and context your agent can read. ## About Codex Codex is OpenAI's coding agent. The open-source Codex CLI runs in your terminal and edits your repository. Its docs list support for MCP servers over remote HTTP and over a local process, which is how it can read a clip.qa report without any copy and paste. ## How it works ### 1. Record the bug on your own device Use the clip.qa iOS or Android app (beta, request access), or the Chrome extension (beta, request access), to screen-record the bug. No SDK goes into the app you test. ### 2. Review the AI draft clip.qa turns the recording into a report: title, severity, kind, suspected root cause, steps to reproduce, and expected vs actual behavior when the recording shows a defect, plus key-moment screenshots and device context (OS, device, memory, thermal). It is a draft, so check it before you hand it to Codex. ### 3. Send the report to Codex Connect the clip.qa MCP server to Codex and ask it for the latest report, or copy the report as Markdown and paste it into a Codex session. ### 4. Review the diff and log the attempt Codex gets the steps and context it needs to attempt a fix. You review the diff. Over MCP, your agent can also log each fix attempt (pending, succeeded or failed) with its commit or PR. ## Two ways to give Codex a clip.qa report clip.qa has written setup guides for Claude Code, Cursor and Windsurf. Codex connects through the same standard MCP details. OpenAI did not build this connection. - Remote MCP server: https://mcp.clip.qa/mcp - Local MCP server (npm): @clip-qa/mcp-server - CLI (npm): @clip-qa/cli 1. Add clip.qa as an MCP server in Codex using the remote endpoint https://mcp.clip.qa/mcp, or run the local npm package @clip-qa/mcp-server with your clip.qa API key. Follow the MCP page in the Codex docs for the exact config form. 2. Prefer the shell? Codex runs in a terminal, so the clip.qa CLI (npm @clip-qa/cli) is another route. 3. No setup at all: copy the report as Markdown from clip.qa and paste it into the Codex session. The clip.qa iOS app, Android app and Chrome extension are in beta. Request access on the apps page. ## Choose Codex on its own if - The bug reproduces from code or a failing test, with no device in the loop. - You already have the steps and logs written down. - You want a terminal agent for refactors and features, not for bug intake. ## Why clip.qa for Codex users Codex writes and edits code. clip.qa does not. clip.qa is for the moment before that: you hit a bug on your phone in an AI-built app, and typing the steps from memory loses half of them. For solo developers and small teams shipping mobile apps, the recording becomes the report. ## FAQ **Q: Does clip.qa work with Codex?** A: Codex documents MCP support for remote HTTP and local servers, so it can connect to https://mcp.clip.qa/mcp or to the @clip-qa/mcp-server package. clip.qa has setup guides for Claude Code, Cursor and Windsurf; for Codex use the generic MCP details above. You can also paste the report as Markdown. **Q: Will Codex fix the bug for me?** A: Codex gets the steps, screenshots and device context it needs to attempt a fix. It does not fix every bug, so review the diff the way you would review any pull request. **Q: Is this an OpenAI integration?** A: No. clip.qa is an independent product. Codex is built by OpenAI, and there is no partnership. The connection uses the standard MCP protocol that Codex supports. --- [Request beta access](https://clip.qa/apps) | [Back to clip.qa](https://clip.qa)