Multiplayer

The debugging agent for developers.

[Multiplayer @trymultiplayer]

Multiplayer: the debugging agent for developers.

We connect your favorite coding agent to prod to fix application bugs automatically.

Run us locally and eliminate PR slop.

[Multiplayer @trymultiplayer]

Multiplayer captures the actual runtime context you (and your coding agent) need to understand your system and fix bugs:

• User interactions and clicks
• Session metadata
• Network requests
• Console messages
• Error rate metrics and errors per user (not sampled!)
• Stack traces, spans, and logs (not sampled!)
• Request/response headers and content from deep within your system

[Multiplayer @trymultiplayer]

Targeted capture beats constant collection.

Change my mind.

[Multiplayer @trymultiplayer]

Watching the debugging agent fix bugs in real-time.

(One copy/paste line in your terminal, and you can too 👀)

[Multiplayer @trymultiplayer]

One line.

That’s it.

All you need to start saving hours of debugging time.

[Multiplayer @trymultiplayer]

Install the Multiplayer debugging agent in your console. Run it locally. No source code access required.

[Multiplayer @trymultiplayer]

To go from bug identified to bug fixed, agents need runtime data that observability tools weren't designed to provide. This talk explores that 👀 👇

[Thomas Johnson @tomjohnson3]

Minneapolis last week. New York on June 9-10.

I'll be speaking at @DevWeekNYC a talk I've been wanting to give for a while: From Alert to Action: Redesigning Your Observability Stack for Agentic AI.

[Thomas Johnson @tomjohnson3]

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 ☕️

[Multiplayer @trymultiplayer]

Proud to see our Director of Community and DevRel and on stage at Cloud Native Days Italy 2026.

The cognitive cost of too much choice is something we think about a lot at Multiplayer. It's part of why we built our debugging agent to run locally, right next to your coding agent: less context switching, less decision fatigue, more fixing.

Great talk. 💜

[Vladi Stevanovic @vladistevanovic]

Today I had the privilege of delivering a keynote at Cloud-Native Days Italy 2026 and I'm still processing how much fun it was. 🤩

If you're curious about the research behind the talk, here are the slides with all the sources linked: https://t.co/6TqZUENqp7

[Multiplayer @trymultiplayer]

The boundary of 'what AI can do' is moving.

The debugging agent is a useful case study. The first generation of coding agents tried to fit into existing manual debugging workflows, using the same observability data humans relied on. The result was PR slop: fixes generated from sampled, aggregated, and missing data that looked plausible and failed in production.

The next generation is being built differently: session-based, full-stack, pre-correlated runtime data, with issues deduplicated before they ever reach the coding agent.

That's the workflow being redesigned around what machines actually need, and not retrofitted into what humans used to do.

[Thomas Johnson @tomjohnson3]

There's a story economists love to tell about ATMs and bank tellers.

If you're a developer, you've probably heard it cited in relation to AI tools: the technology won't replace you, it will assist you.

[Multiplayer @trymultiplayer]

Partial data frustrates human debuggers. It breaks AI ones.

AI agents need full runtime context (unsampled, correlated, complete) to understand what actually went wrong. Especially in distributed systems, where the failure rarely lives where the symptom shows up.

[Thomas Johnson @tomjohnson3]

Most engineering teams are using AI to write code faster than ever. But they are also shipping bugs with equal speed. Ultimately, the root cause is a data problem.

[Multiplayer @trymultiplayer]

This is what grepping through sampled logs feels like ...

[Programmer Humor @PR0GRAMMERHUM0R]

beenThereDoneThat

[Multiplayer @trymultiplayer]

How much of your on-call time is spent figuring out what happened vs. actually fixing it?

[Multiplayer @trymultiplayer]

Decision fatigue is real in cloud-native development and most of it hits before you write a single line of code.

Our Director of Community, @vladistevanovic will be talking about why at @CNDItaly.

The part nobody mentions: every bug that shows up resets the whole process. Even wondering 'Where do I even start?' is its own tax on top of everything else.

[Cloud Native Days Italy @CNDItaly]

⚡ KEYNOTE SPEAKER: @vladistevanovic

Director of Community & DevRel at Multiplayer
10 years working in the trenches with developers at Squarespace, MongoDB, and Prisma

🎤 Keynote talk: "The Hidden Cognitive Cost of Cloud-Native Sprawl"

Check it out: https://t.co/Vp1w6g0MYq

[Multiplayer @trymultiplayer]

It's the same problem with low-quality inputs to coding agents. An agent acting on incomplete or noisy data produces worse outputs and erodes confidence in every bug the agent flags.

You can't fix that with a better model. You fix it with better data.

[Thomas Johnson @tomjohnson3]

The Law of False Alerts: “As the rate of erroneous alerts increases, operator reliance, or belief, in subsequent warnings decreases.”

Too many alerts and people stop reading them. Too many false positives and people stop trusting them.

[Multiplayer @trymultiplayer]

If your coding agent introduced a bug today, how long before you'd know?

[Multiplayer @trymultiplayer]

Our CTO is heading to Minneapolis to say the quiet part loud. 🎤

[Thomas Johnson @tomjohnson3]

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 @trymultiplayer]

Your AI coding agent and your observability tools were designed with completely different objectives.

That's your debugging gap.

[Multiplayer @trymultiplayer]

The next production incident is already in your system.

The question is whether you'll have the full context when it surfaces.

[Multiplayer @trymultiplayer]

Quick correction:

🕐 *10:00 AM* PDT | *1:00 PM* EDT | 6:00 PM CET

[Multiplayer @trymultiplayer]

Our CTO @tomjohnson3 will be joining Jon Haddad, @mmanciop , and Amy Tobey for a panel on agentic observability, hosted by @dash0hq and @TheLeadDev

📅 Tomorrow, WED, 18 MAR 2026
🕘 9:00 AM PST | 12:00 PM EST | 6:00 PM CET