Workflow examples
Multiplayer records what happens across your entire stack, end-to-end, and ties it all together in a single, shared session replay.
Each session captures what users saw, what the system did, and how the data moved through your services (even within your middleware and internal service calls). This gives every team the same source of truth when diagnosing, debugging, or explaining a technical issue.
Multiplayer integrates with your existing tools. You can keep using your current coding agents, helpdesk, observability, and ticketing systems (e.g. Zendesk, Intercom, Jira, etc.). Multiplayer simply adds full-stack context behind every issue.
Example: How Engineering teams work with Multiplayer
(1) A developer is alerted that a new PR is ready to review
The Multiplayer debugging agent that sits between your production runtime and your coding agent and runs in the background while you work.
It watches for errors and exceptions, gathers the data needed to understand them, and hands a curated version of that data to the coding agent you already work with, so it can produce an accurate fix.
Developers are notified when a new PR is ready to review and can review & merge it as any other.
(2) A developer notices (or is alerted about) a bug A developer encounters an issue while working and, to quickly understand the undelying system behaviour, they record a session recording using one these options:
(2) The developer captures the bug with a session recording In addition to multiple capture methods, developers can also choose between different capture modes:
→ Automatic: Automatically capture and resolve bugs in your application → On-demand: Manually start/stop recordings to capture bugs or unexpected behaviors → Continuous (rolling buffer): Manually enable/disable a rolling capture of your work. Recordings for errors and exceptions are auto-saved. You can also manually save recordings for your last 2 minutes of work
(3) Engineering teams review and annotate the recording Once captured, the recording appears in the Multiplayer web dashboard, where teams can inspect both frontend and backend data all correlated within a single timeline, including traces, logs, requests/responses content and headers from deep within the system.
Developers and QA can annotate sessions, highlight anomalies, and add notes to individual data points (APIs, errors, spans, traces, etc.) for discussion or handoff.
(4) Developer uses the recording to fix the bug Developers can:
- Reproduce the issue locally using the session data
- Feed the full session context to their IDE or AI coding assistant via the debugging agent CLI or Multiplayer MCP server
- Or manually investigate and code a fix using the recording and correlated telemetry
Each approach starts from the same shared session, reducing time spent gathering or verifying context.
(5) Visibility across all sessions Through the Multiplayer web dashboard, developers aren’t limited to their own recordings.
They can see all debugging sessions, recordings, and issues captured across the entire application. whether triggered automatically or manually.
This visibility allows them to:
- Spot recurring errors or performance patterns
- Identify potential problems proactively
- Leverage Multiplayer’s issues, which clusters similar sessions to help surface systemic issues earlier
Example: how Technical Support teams work with Multiplayer
(0) Bugs are proactively caught and resolved
By using the Multiplayer debugging agent, technical teams can proactively catch and resolve bugs in their application (in any environment) before they reach their end-users.
(1) End-user encounters a problem
A user experiences a bug or unexpected behaviour in your application.
They manually report it to the Technical Support team using the Multiplayer in-app widget or browser extension.
(2) End-user records a full-stack session When opening the Multiplayer in-app widget or browser extension, the end-user can choose between two recording modes:
- On-demand recording: Manually start and stop a session to capture exactly what matters.
- Continuous recording: Keep a rolling record of recent activity. Multiplayer automatically saves sessions that contain frontend or backend errors and exceptions, or the user can manually save one at any time.
(3) Technical Support reviews the recording A complete session recording often provides all the information needed to resolve an issue directly.
The Support team can review what the user saw, what the system did, and identify the cause without escalation.
✅ Ticket resolved — Support and users are happy.
(4) Technical Support shares the recording with Engineering In the cases of:
- Bugs
- Unexpected behaviours
- Inefficient or undesirable system responses
And escalation to Engineering is needed, and the support agent adds the user’s Multiplayer session recording link directly into the ticketing system (e.g. Zendesk, Intercom, Jira) or shares it via Slack or Teams.
ℹ️ Before sharing, the agent can annotate the recording, highlight suspicious behaviour, or add comments to specific data points (APIs, spans, traces).
All of this context remains in a single link, attached to the original ticket.
(5) Engineering reviews the recording and fixes the issue The recording link contains everything Engineering needs to fully understand the problem: user actions, UI state, visible errors, and system-level telemetry. Multiplayer automatically includes backend traces, logs, and request/response data linked to the session.
Frontend developers, backend developers, and QA can all collaborate in one view to determine the root cause and fix. Or they can feed it directly to their coding agents to generate a fix using the debugging agent CLI or Multiplayer MCP server
(6) The issue is resolved faster Engineering doesn’t need to gather missing context or ask Support for more data. It’s all already captured. They can move straight to diagnosing and fixing the issue.
Support stays in the loop, Engineering stays focused, and the user gets a clear, timely resolution.
Next steps
🚀 If you’re ready to trial Multiplayer with your own app, you can follow the steps in the quickstart.
📌 If you have any questions shoot us an email! 💜