Multiplayer
@multiplayer.app
Full stack session recording. End-to-end visibility in a single click. Capture once, use for debugging, testing, support, feature development ...
Try it for free: multiplayer.app
Try it for free: multiplayer.app
Pinned
Tried cooking up some code with Julia Child and promptly broke the recipe (ahem, application).
Thankfully, Multiplayer had the whole thing recorded: every click, trace, payload and header from deep inside the system.👇
Thankfully, Multiplayer had the whole thing recorded: every click, trace, payload and header from deep inside the system.👇
November 11, 2025 at 10:44 AM
Tried cooking up some code with Julia Child and promptly broke the recipe (ahem, application).
Thankfully, Multiplayer had the whole thing recorded: every click, trace, payload and header from deep inside the system.👇
Thankfully, Multiplayer had the whole thing recorded: every click, trace, payload and header from deep inside the system.👇
What a “hot-potato” hand off looks like in tech support:
November 10, 2025 at 8:26 AM
What a “hot-potato” hand off looks like in tech support:
Most MCP servers give your AI IDEs access to *some* context, usually APM data or frontend-only replays. That’s useful, but incomplete.
Without the *full stack* context, your AI agents are left guessing, and hallucinations creep in. 👇
Without the *full stack* context, your AI agents are left guessing, and hallucinations creep in. 👇
November 7, 2025 at 12:06 PM
Most MCP servers give your AI IDEs access to *some* context, usually APM data or frontend-only replays. That’s useful, but incomplete.
Without the *full stack* context, your AI agents are left guessing, and hallucinations creep in. 👇
Without the *full stack* context, your AI agents are left guessing, and hallucinations creep in. 👇
1. Open VS Code
2. Go to Extensions view (Ctrl+Shift+X or Cmd+Shift+X)
3. Search for "Multiplayer"
4. Click Install
5. Debug in minutes instead of days
2. Go to Extensions view (Ctrl+Shift+X or Cmd+Shift+X)
3. Search for "Multiplayer"
4. Click Install
5. Debug in minutes instead of days
November 6, 2025 at 4:01 PM
1. Open VS Code
2. Go to Extensions view (Ctrl+Shift+X or Cmd+Shift+X)
3. Search for "Multiplayer"
4. Click Install
5. Debug in minutes instead of days
2. Go to Extensions view (Ctrl+Shift+X or Cmd+Shift+X)
3. Search for "Multiplayer"
4. Click Install
5. Debug in minutes instead of days
...and that’s how we burn half a day for one happy user. Does the support workflow behind your five-star reviews look like this? 👇
November 5, 2025 at 3:25 PM
...and that’s how we burn half a day for one happy user. Does the support workflow behind your five-star reviews look like this? 👇
Every engineer has their own “it worked on my machine” story.
We can't wait to hear Faris' journey with the app he built when the pandemic hit to "WOD With Me" (work out of the day)... and how full-stack session recordings can make debugging way less painful! 😆
We can't wait to hear Faris' journey with the app he built when the pandemic hit to "WOD With Me" (work out of the day)... and how full-stack session recordings can make debugging way less painful! 😆
👇 @farisaziz12.bsky.social describes the pain of customer support perfectly.
It’s always exciting to see Multiplayer show up in real-world stories like this, as part of how engineers actually solve problems. Seeing it used to cut through the “screenshot chaos” is exactly why we built it.
It’s always exciting to see Multiplayer show up in real-world stories like this, as part of how engineers actually solve problems. Seeing it used to cut through the “screenshot chaos” is exactly why we built it.
November 3, 2025 at 11:07 AM
Every engineer has their own “it worked on my machine” story.
We can't wait to hear Faris' journey with the app he built when the pandemic hit to "WOD With Me" (work out of the day)... and how full-stack session recordings can make debugging way less painful! 😆
We can't wait to hear Faris' journey with the app he built when the pandemic hit to "WOD With Me" (work out of the day)... and how full-stack session recordings can make debugging way less painful! 😆
Multiplayer transforms the chaos of support tickets. Eliminate manual work, hot potato hand-offs and grepping through log files. 👇
October 31, 2025 at 4:35 PM
Multiplayer transforms the chaos of support tickets. Eliminate manual work, hot potato hand-offs and grepping through log files. 👇
Multiplayer removes the anguish from customer support ticketing and bug fixing.
What anguish you ask? This one 👇
What anguish you ask? This one 👇
October 30, 2025 at 2:08 PM
Multiplayer removes the anguish from customer support ticketing and bug fixing.
What anguish you ask? This one 👇
What anguish you ask? This one 👇
Multiplayer is scientifically* proven to reduce your TWUBAF**
*Peer-reviewed by engineers who’ve had enough
**Time Wasted in Unnecessary Back-and-Forth
*Peer-reviewed by engineers who’ve had enough
**Time Wasted in Unnecessary Back-and-Forth
October 29, 2025 at 3:26 PM
Multiplayer is scientifically* proven to reduce your TWUBAF**
*Peer-reviewed by engineers who’ve had enough
**Time Wasted in Unnecessary Back-and-Forth
*Peer-reviewed by engineers who’ve had enough
**Time Wasted in Unnecessary Back-and-Forth
Stop sending screenshots, start sharing full stack session replays.
October 27, 2025 at 3:45 PM
Stop sending screenshots, start sharing full stack session replays.
When we say “supercharge your AI,” it’s not marketing-speak.
We mean giving it *everything in one prompt*: Frontend screens. User actions. Backend traces. Logs. Requests/Responses. Headers. Sketches. Requirements…
All correlated, all contextual, all ready for your AI tool to actually do its job.
We mean giving it *everything in one prompt*: Frontend screens. User actions. Backend traces. Logs. Requests/Responses. Headers. Sketches. Requirements…
All correlated, all contextual, all ready for your AI tool to actually do its job.
October 25, 2025 at 3:25 PM
When we say “supercharge your AI,” it’s not marketing-speak.
We mean giving it *everything in one prompt*: Frontend screens. User actions. Backend traces. Logs. Requests/Responses. Headers. Sketches. Requirements…
All correlated, all contextual, all ready for your AI tool to actually do its job.
We mean giving it *everything in one prompt*: Frontend screens. User actions. Backend traces. Logs. Requests/Responses. Headers. Sketches. Requirements…
All correlated, all contextual, all ready for your AI tool to actually do its job.
Engineering teams are (rightly) sensitive to anything that could slow performance down.
Especially when traditional recording tools take the same brute-force approach: capture everything. Here’s how we do it: 🧵
Especially when traditional recording tools take the same brute-force approach: capture everything. Here’s how we do it: 🧵
October 24, 2025 at 12:19 PM
Engineering teams are (rightly) sensitive to anything that could slow performance down.
Especially when traditional recording tools take the same brute-force approach: capture everything. Here’s how we do it: 🧵
Especially when traditional recording tools take the same brute-force approach: capture everything. Here’s how we do it: 🧵
Debugging AI workslop with AI only works if you give it the right data.
October 23, 2025 at 3:31 PM
Debugging AI workslop with AI only works if you give it the right data.
Just finished a chat with Doc Brown. He kept yelling about the “flux capacitor” but I’m pretty sure it was an error in the code. 😅
It just takes one perfectly captured full stack session recording to figure it all out. 👇
It just takes one perfectly captured full stack session recording to figure it all out. 👇
October 22, 2025 at 11:23 AM
Just finished a chat with Doc Brown. He kept yelling about the “flux capacitor” but I’m pretty sure it was an error in the code. 😅
It just takes one perfectly captured full stack session recording to figure it all out. 👇
It just takes one perfectly captured full stack session recording to figure it all out. 👇
How to bring your live system into your AI IDE during MCP demo night.
📅 Tomorrow, Wed, Oct 22 @ 6 PM
📍 MongoDB HQ – New York
📅 Tomorrow, Wed, Oct 22 @ 6 PM
📍 MongoDB HQ – New York
October 21, 2025 at 8:08 AM
How to bring your live system into your AI IDE during MCP demo night.
📅 Tomorrow, Wed, Oct 22 @ 6 PM
📍 MongoDB HQ – New York
📅 Tomorrow, Wed, Oct 22 @ 6 PM
📍 MongoDB HQ – New York
QA: Can you show me how to reproduce it?
Dev: Absolutely.
Multiplayer: 🤦
Dev: Absolutely.
Multiplayer: 🤦
October 20, 2025 at 2:34 PM
QA: Can you show me how to reproduce it?
Dev: Absolutely.
Multiplayer: 🤦
Dev: Absolutely.
Multiplayer: 🤦
👀 You can programmatically save a specific full-stack session recording, when the auto-save attribute is attached to a span.
See here for the "how-to": www.multiplayer.app/docs/session...
See here for the "how-to": www.multiplayer.app/docs/session...
October 18, 2025 at 2:15 PM
👀 You can programmatically save a specific full-stack session recording, when the auto-save attribute is attached to a span.
See here for the "how-to": www.multiplayer.app/docs/session...
See here for the "how-to": www.multiplayer.app/docs/session...
A few session replay tools let you blur sensitive data, sketch on a screenshot, or add notes through third-party integrations.
But what they *don’t* let you do is connect those annotations to the actual system data. 👀🧵
But what they *don’t* let you do is connect those annotations to the actual system data. 👀🧵
October 17, 2025 at 2:15 PM
A few session replay tools let you blur sensitive data, sketch on a screenshot, or add notes through third-party integrations.
But what they *don’t* let you do is connect those annotations to the actual system data. 👀🧵
But what they *don’t* let you do is connect those annotations to the actual system data. 👀🧵
Yes, a Multiplayer full-stack session recording + Claude Code would have definitely caught that 😇
Claude Code error or human error?
From the latest Anthropic blog post: variable names don’t match (red)…misspelling of urgent (blue) … unnecessary second check (second yellow line)
From the latest Anthropic blog post: variable names don’t match (red)…misspelling of urgent (blue) … unnecessary second check (second yellow line)
October 16, 2025 at 5:29 PM
Yes, a Multiplayer full-stack session recording + Claude Code would have definitely caught that 😇
Pikachu would tell you: “Catch a bug. Not a Pokémon.” … we think.
Turns out Pikachu’s biggest weakness isn’t ground-type attacks. It’s backend latency. I watched the whole thing unfold in the session replay.
Turns out Pikachu’s biggest weakness isn’t ground-type attacks. It’s backend latency. I watched the whole thing unfold in the session replay.
October 16, 2025 at 2:15 PM
Pikachu would tell you: “Catch a bug. Not a Pokémon.” … we think.
Turns out Pikachu’s biggest weakness isn’t ground-type attacks. It’s backend latency. I watched the whole thing unfold in the session replay.
Turns out Pikachu’s biggest weakness isn’t ground-type attacks. It’s backend latency. I watched the whole thing unfold in the session replay.
AI: ‘Bug fixed.’
Production: 💀
Senior engineer: opens Multiplayer session replay in silence, to send to the AI.
Production: 💀
Senior engineer: opens Multiplayer session replay in silence, to send to the AI.
October 15, 2025 at 4:07 PM
AI: ‘Bug fixed.’
Production: 💀
Senior engineer: opens Multiplayer session replay in silence, to send to the AI.
Production: 💀
Senior engineer: opens Multiplayer session replay in silence, to send to the AI.
🧵 What is an “AI Engineer,” really?
It’s one of the hottest job titles of 2025 but also one of the most misunderstood. Let’s unpack what the role actually means (and why it matters).
It’s one of the hottest job titles of 2025 but also one of the most misunderstood. Let’s unpack what the role actually means (and why it matters).
October 13, 2025 at 6:01 PM
🧵 What is an “AI Engineer,” really?
It’s one of the hottest job titles of 2025 but also one of the most misunderstood. Let’s unpack what the role actually means (and why it matters).
It’s one of the hottest job titles of 2025 but also one of the most misunderstood. Let’s unpack what the role actually means (and why it matters).
Why record *everything* when 90% of it doesn’t matter?
October 9, 2025 at 12:43 PM
Why record *everything* when 90% of it doesn’t matter?
Most session replay tools force a tradeoff:
🎥 Record on demand → you miss what happens outside the window.
📼 Record everything → you drown in noise and costs.
We took a different approach 🧵
🎥 Record on demand → you miss what happens outside the window.
📼 Record everything → you drown in noise and costs.
We took a different approach 🧵
October 8, 2025 at 11:47 AM
Most session replay tools force a tradeoff:
🎥 Record on demand → you miss what happens outside the window.
📼 Record everything → you drown in noise and costs.
We took a different approach 🧵
🎥 Record on demand → you miss what happens outside the window.
📼 Record everything → you drown in noise and costs.
We took a different approach 🧵
Sometimes the frontend data isn’t enough.
Sometimes (okay, always) you also want to know what happened in the backend.
Sometimes (okay, always) you also want to know what happened in the backend.
October 7, 2025 at 4:38 PM
Sometimes the frontend data isn’t enough.
Sometimes (okay, always) you also want to know what happened in the backend.
Sometimes (okay, always) you also want to know what happened in the backend.