Configuring Multiplayer
TL;DR
The quickest and easiest way to get started is with just one copy/paste command into your terminal:
npm install -g @multiplayer-app/cli && multiplayer
However, you can also proceed with a manual setup to customize Multiplayer to your specific tech stack and internal workflows. You can cutomize your:
- Deployment (hosted or self-hosted)
- Client setup (browser extension, client library with in-app widget, SDK)
- Backend setup
- Recording modes
Supported applications
Multiplayer can be configured on the following applications:
- Type: Web and mobile
- Language: JavaScript, Node.js, Python, Java, .NET, Go, Ruby (with more to come!)
- Framework: Any
- Architecture: On-prem, cloud native, serverless, or hybrid
- Environment: Production, staging, or development
ℹ️ All our guides are optimized for the Cloud deployment with our Multiplayer platform. If you're interested in the self-hosted option, please review the open source documentation.
Overview
Here’s an overview of the main steps to manually configure Multiplayer and the various customization options:
(1) Account setup
Login into your Multiplayer account. If you don't already have one, create a free trial at go.multiplayer.app.
(2) Client setup
Choose how you want to capture the full stack session recording:
- Install the debugging agent CLI
- Install our Chrome browser extension
- Install our JavaScript client library and set up the in-app widget
- Install our React Native client library for mobile apps
(3) Backend setup
Connect your backend services for deeper insights. Multiplayer leverages OpenTelemetry for collecting telemetry data. If your services don't already use it, you'll first need to install the OpenTelemetry libraries.
- Route traces and logs to Multiplayer. You have 2 options:
- Capture request / response content and headers. You have 2 options:
(4) Record sessions
Recordings can be recorded using three recording modes:
| Capture mode | Capture method | Overview | Output | Issue types |
|---|---|---|---|---|
| Automatic | Debugging agent CLI | Automatically capture and resolve bugs in your application | Recording > Issue > PR | • All application errors and exceptions (frontend and backend) |
| On-demand | Browser-extension, in-app widget | Manually start/stop recordings to capture bugs or unexpected behaviors | Recording > Issue | • Unexpected behaviors |
| • End-user issue reports | ||||
| • Manually reproduced application errors and exceptions (frontend and backend) | ||||
| Continuous | Browser-extension, in-app widget | 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 | Recording > Issue | • Unexpected behaviors |
| • End-user issue reports | ||||
| • Application (frontend and backend) errors and exceptions experienced while continuous mode is enabled or manually reproduced |
(5) Feed recordings to your AI tool
Use the Multiplayer debugging agent CLI to automatically feed your AI tool full-stack, unsampled, runtime data about issues within your application and generate high-quality PRs.
Alternatively, feed your IDE and AI tools the complete system context via our MCP server.
We support:
You can download and try our VS code extension from these marketplaces:
- Visual Studio Marketplace: multiplayer-vscode-extension
- Open VSX registry: multiplayer-vscode-extension
(6) Advanced customizations and CLI apps
Language specific libraries support any type of application and give full control to power users. Use your CLI to capture recordings across environments, get deeper integrations, CI/CD use cases, or backend-triggered sessions.
If your preferred language is not supported, contact us.
You did it! What’s next?
🚀 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! 💜