Use when calling Replay QA's REST API directly from Codex. Covers bearer-token setup, Replay recording prerequisites, project creation from Replay recordings or target URLs, polling, bug retrieval, journeys, test runs, explorations, and fix workflow discipline.
Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.
Quelldateien prüfen
Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Ein direkter Befehl überspringt den Prüf-Prompt. Prüfen Sie die Quelle, bevor Sie ihn ausführen.
Use when calling Replay QA's REST API directly from Codex. Covers bearer-token setup, Replay recording prerequisites, project creation from Replay recordings or target URLs, polling, bug retrieval, journeys, test runs, explorations, and fix workflow discipline.
Replay QA API
Use the Replay QA REST API directly when a task needs Replay QA analysis.
This skill is instructions-only: do not use Replay MCP tools, Codex apps, or plugin hooks as substitutes for Replay QA REST API calls.
Replay.io Skill Prerequisite
Before making any Replay QA API call, make sure the replayio skill in this same Codex plugin bundle has been loaded and applied for the current session.
If setup is unknown, load ../replayio/SKILL.md first and follow it before continuing. In particular, verify:
REPLAY_API_KEY is mapped from SECRET_REPLAY_API_KEY when available.
REPLAY_QA_API_KEY is mapped from SECRET_REPLAY_QA_API_KEY.
AGENT_BROWSER_EXECUTABLE_PATH points at Replay Chromium.
RECORD_ALL_CONTENT and RECORD_REPLAY_VERBOSE are set.
Any Replay recording referenced by Replay QA has uploaded or has a concrete recording UUID.
Do not proceed with project creation or polling if this prerequisite is unknown. Load and apply the replayio skill first, then return to this skill.
Authentication
Replay QA API tokens are bearer tokens that start with lqa_. Generate one in Replay QA Settings and store it as SECRET_REPLAY_QA_API_KEY when the host supports project secrets. Map it before calling the API:
Use this when you already have an uploaded Replay recording UUID. When recording_id is present, target_url is not required.
Required input:
name: clear project or scenario name.
recording_id: Replay recording UUID.
instructions: include the raw test source URL when possible and the exact failure message or stack.
webhook_url: optional.
curl -sS -X POST "$REPLAY_QA_API_BASE/projects" \
-H "Authorization: Bearer $REPLAY_QA_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"name": "S01 - checkout total does not update",
"recording_id": "00000000-0000-0000-0000-000000000000",
"instructions": "Analyze this Replay recording of a failing automated test.\n\nTest source:\nhttps://raw.githubusercontent.com/org/repo/refs/heads/branch/tests/checkout.spec.ts\n\nError:\nExpected checkout total to update after clicking Confirm Checkout.\n\nExplain the root cause and the code change that should fix it."
}'
Save the returned project id and project url if present. If only an id is returned, the overview URL is:
https://qa.replay.io/p/:projectId/overview
Create A Project For Live App Exploration
Use this when Replay QA should explore an app URL instead of analyzing one recording.
curl -sS -X POST "$REPLAY_QA_API_BASE/projects" \
-H "Authorization: Bearer $REPLAY_QA_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"name": "Todo app smoke exploration",
"target_url": "https://example.com",
"instructions": "Explore the main user flows and report correctness, polish, and UX bugs."
}'
Optional fields supported by the API include webhook_url, backend_recording_url, backend_log_url, logins, and design_document. Only include credentials when the user explicitly provided them for this app.
Poll Project Status
Poll every 30 seconds until the project reports completion. Status can be returned either at the top level or under project.status, so inspect the response shape instead of assuming one field.
