The debugging agent for developers.
World 🌍
Joined January 2023
- Tweets1.4K
- Following46
- Followers140
- Likes637
Multiplayer retweeted
Team efficiency is a different goal than individual velocity.
The developers I find most interesting right now don’t ask 'how do I ship more with AI?', instead they ask 'how do I make sure what we ship is worth keeping?'
Multiplayer retweeted
Finished doesn't mean closed.
One of my favorite things about the Multiplayer web dashboard is that you can reopen any session and keep going in the same thread the agent used the first time.
Multiplayer retweeted
I'm attending the Cloud Native Computing Foundation (CNCF) Observability Summit today in 📍Minneapolis, Minnesota.
If anyone is interesting in discussing agentic coding, debugging, or just have a coffee, find me and @BkStephJ1 ☕️
Hot take for a room full of observability practitioners:
Logs, traces, and metrics were designed for a world where humans wrote and reviewed every line of code. That world is gone.
I'm speaking at @CloudNativeFdn's Observability Summit North America in Minneapolis on May 21–22.
Multiplayer retweeted
I’m joining a @TheLeadDev panel tomorrow on agentic observability and AI-powered troubleshooting.
I’ll be speaking with:
• Michele Mancioppi (Dash0)
• Amy Tobey (Netflix)
Multiplayer retweeted
Not all session replays are built for the same job.
📊 Product analytics tools answer questions about user behavior.
🪲 Debugging tools need to answer questions about system behavior.
Not all "session replay" features are created equal. Mixpanel's frontend session replays are an add-on to a product analytics tool, for PMs.
Multiplayer's full stack session replays, on the other hand, are built for engineers asking:
“What issue did the end-user experience?”
“Why is the system behaving this way?”
“How do we fix this bug?”
Multiplayer retweeted
Now here’s where things get messy in real-world systems 👇
When you’re working with distributed systems or microservices, concurrency + parallelism issues quickly turn into a 5-tab debugging circus.
This visual says it all.
👉 And this is exactly where Multiplayer helps, it brings frontend session replay + backend traces in one unified timeline, so you can actually see how concurrent calls relate.
trymultiplayer.link/curious-…
Multiplayer retweeted
The Future of Coding Isn't Writing. It's Recording 🎥
youtube.com/shorts/Nzr4p2m-f… via @YouTube
@trymultiplayer #DevTools #debuggingtips #DevOps #techtalk #DeveloperCommunity #ProductivityTips
Multiplayer retweeted
Your #AI assistant is smart; it sees your code, but it lacks the context of a real-world runtime bug 😔
The Multiplayer MCP server shatters this limitation!
Watch the Future of Dev in Action👉 youtu.be/UA-A6xs_nWI
@trymultiplayer Fullstack Session 👉 trymultiplayer.link/rakia-sa…
Multiplayer retweeted
How many engineering hours did you burn on mystery bugs?
We're paying our best engineers to be detectives not builders.
Watch how Multiplayer kills fragmented observability & boosts developers productivity 👉 youtu.be/UA-A6xs_nWI
For more insights 👉 rakiabensassi.substack.com/
Multiplayer retweeted
→ @trymultiplayer provides full stack session recordings — capturing frontend, backend, and data context in one place. Debug faster, build features, and power your AI tools.
🔴 Live on Dev Hunt → devhunt.org/tool/multiplayer
Multiplayer retweeted
Capture a full stack session recording once, use it for debugging, testing, support, feature development, and AI prompts.
Here's everything you can do in Multiplayer 👀 👇
Multiplayer retweeted
What’s it like launching an #MCP server into the wild? My latest DirectorPlus edition via @TheLeadDev brings in Thomas Johnson, co-founder and CTO of @trymultiplayer, to discuss helpful lessons learned releasing their MCP server.
leaddev.com/ai/lessons-learn…
Multiplayer retweeted
When we build something at @trymultiplayer, we aim for insanely great quality.
For example: we’ve been building a sandbox so you can test Multiplayer without signing up for a free trial. Seems straightforward, right?
But in practice, there’s a lot to think through 👇
Multiplayer retweeted
Of course, if you're looking for a debugger, I can recommend my tool - @trymultiplayer - which includes traces in its full-stack session recordings
Multiplayer retweeted
Traditional observability: investigate the crime scene.
Multiplayer: catch the bug in the act, with the receipts.
It’s time debugging felt like part of the dev workflow—not an incident report.
Multiplayer retweeted
Debugging distributed systems is brutal. Reproducing bugs, syncing across teams, and writing tests. It all slows down engineering.
With this new Multiplayer feature, with one click you can turn a debugging session into a test script your team can run, edit, and reuse.
Multiplayer retweeted
@trymultiplayer ties it all together.
We capture deep debugging sessions: full replays that show what users saw, what APIs returned, and what services did—frame by frame.
And now, we go one step further: we can turn that debug session into a reproducible test script.
Multiplayer retweeted
Traditional approaches to documentation & debugging fail in modern, distributed systems 😤
So what now?
Join @trymultiplayer Webinar & see how to bake visibility and automation into your workflows from day one!
📅 May 20, 2025
⏰ 8 PM CEST
📍 Live: trymultiplayer.link/6w0n8Ry
Multiplayer retweeted
Did you ever spend half a day trying to understand what a microservice does… 😅
Just because nobody documented it properly?
Or worse - debugged a distributed system in production, with logs scattered across 4 tools and a shared Notion page from 2021?
Yeah, me too. I had similar problems.
That’s why I’m joining the upcoming event by Multiplayer:
“𝐔𝐧𝐥𝐨𝐜𝐤𝐢𝐧𝐠 𝐀𝐈: 𝐀𝐮𝐭𝐨-𝐝𝐨𝐜𝐮𝐦𝐞𝐧𝐭𝐚𝐭𝐢𝐨𝐧 & 𝐃𝐞𝐛𝐮𝐠𝐠𝐢𝐧𝐠 𝐟𝐨𝐫 𝐃𝐢𝐬𝐭𝐫𝐢𝐛𝐮𝐭𝐞𝐝 𝐒𝐲𝐬𝐭𝐞𝐦𝐬”
• May 20, 2025
• FREE to attend
• Online
I’ll be there as well, so we can learn together how to build systems that don’t burn us out.
If you're working with distributed systems, microservices, or just tired of chasing tribal knowledge, this is for you.
Save your seat here: trymultiplayer.link/jG16gNR/
