Skip to main content

Welcome

đź‘‹ Welcome to Multiplayer!

Multiplayer is a full stack session recorder that captures everything you need to develop new features, fix bugs, and work with AI coding tools. Multiplayer collects front-end screens, user actions, backend traces, metrics, logs and full request/response content and headers - all auto-correlated in a single session.

Multiplayer full stack session recordings overview

Explore Multiplayer​

The fastest way to get started is to install the Multiplayer browser extension from the Chrome Web Store (Chrome, Firefox, and Edge supported).

👀 If this is the first time you’ve heard about us, you may want to see full stack session recordings in action. You can do that in our free sandbox: sandbox.multiplayer.app

⏳ Our sandbox comes preloaded with session recordings from a real demo app (“Multiplayer Time Travel”) we built to generate authentic data and show how Multiplayer works in practice. You can explore the demo at demo.multiplayer.app and record a full stack session replay that appears instantly in the sandbox.

🪾 When you’re ready to go deeper, you can fork the demo app repo and experiment locally. This is a great way to understand how Multiplayer integrates into a real application, while still in a controlled environment.

🚀 If you’re ready to trial Multiplayer with your own app, you can follow the Multiplayer configuration steps. You can start a free trial at any time: go.multiplayer.app

We support multiple install methods aside the browser extension — in-app widget, CLI libraries, and mobile — so you can choose the approach that best fits your stack.

⏰ Multiplayer is versatile by design, with multiple ways to customize how you capture session replays and how much detail gets recorded automatically. In this choose-your-own-adventure setup, most teams are fully configured in just a few hours and can get started the same day.

If it’s taking longer or you hit a blocker contact us.

Quick start overview​

To fully configure Multiplayer full stack session recordings follow the configuration guide.

Here’s an overview of the three steps needed and various customization options:

Recording modes​

You can record full stack session recordings in 3 modes:

(1) On-demand Capture full stack session recordings on demand with a browser extension, in-app widget, or SDK. Developers, QA, product, support, and even external partners can instantly record and share issues, explore system behavior, and collaborate with sketches and annotations to fix bugs or design new features.

(2) Continuous Record all sessions automatically in the background, so reproducing issues is never required. Multiplayer saves recordings the moment bugs or anomalies occur making it effortless to capture elusive, hard-to-reproduce problems.

(3) Remote (coming soon - contact us if you’re interested in early beta). Silently capture user sessions without any manual steps or bug reports. Multiplayer detects and records issues even when users don’t notice or don’t report them, giving your team complete context to resolve problems faster and avoid unclear, incomplete tickets.

All recording modes support all full stack session recording features. In particular:

  • Full stack automatic correlation (when you connect your backend services)
  • Recording annotations
  • MCP-ready full stack context
  • Auto-generated, interactive test scripts

ℹ️ For a detailed step-by-step overview guide, please refer to: Full stack session recording features.

Multiplayer + AI workflows​

(1) AI-ready annotated recordings Turn session recordings into actionable development plans to share with your team or your AI coding assistant. Select traces, API calls, or user interactions, and annotate directly on screenshots: whether it’s sketching over a button, specifying new API routes, or listing the reqs of new features. Every bug fix or feature request comes with precise, context-rich instructions.

(2) MCP-ready full stack context Feed your copilots and AI IDEs the complete system context they need: user actions, traces, logs, requests, responses, header data, plus team annotations. No missing data, no guesswork. Your AI tools can generate accurate fixes, tests, and features with minimal prompting.

ℹ️ For a detailed overview guide, please refer to: Multiplayer MCP server.

Use cases​

Fix bugs faster: With full stack session recordings you automatically have everything you need to identify, understand, and fix bugs. From ephemeral, intermittent, hard-to-reproduce bugs, to difficult root cause analysis (RCA), to user reported issues.

Feed the right data to your AI IDE: Stream rich, auto-correlated and annotated session data into your AI tools. Give your AI assistants the complete and precise information they need to be more accurate, responsive, and useful in real-world development workflows.

Build new features with confidence: Multiplayer shows you immediately and effortlessly how your system behaves end-to-end. Record a session, observe real-world behavior in production, and make changes without fear of breaking something downstream.

Capture every issue, from customer apps to internal tools: Whether it’s a customer in production or an employee using an internal app, Multiplayer captures every issue with complete context. No incomplete reports, no non-reproducible bugs, just full stack recordings that make every problem actionable and fixable.

Understand why your tests are failing: Multiplayer complements E2E testing tools by showing you exactly what happened and providing missing critical information to understand why a test failed.

Share complete bug reports, effortlessly: Break down silos inside and outside your organization by sharing full stack session recordings instead of incomplete tickets. Whether it’s QA, product, support, or external partners, everyone works from the same precise context to resolve issues faster.

What’s next?​