iiinova — where your digital self keeps evolving

Multiplayer @multiplayer.app · 18/08/2026

Big news: Multiplayer is joining FilingRamp 🎉 Four years ago we set out to help teams work better on distributed systems. Along the way we grew to thousands of users and found success building alongside the FilingRamp team. Together, we're bringing real AI to the InsurTech space.

100

Multiplayer @multiplayer.app · 10/08/2026

Myth: connecting your agent to your APM closes the debugging loop. Reality: the agent inherits every structural limitation of the data underneath it. Our CTO @tomjohnson3.bsky.social explains it best in this article 👇

110

Multiplayer @multiplayer.app · 06/08/2026

When something breaks on mobile, Multiplayer captures it and sends your coding agent the exact runtime data it needs to fix it automatically.

000

Multiplayer @multiplayer.app · 04/08/2026

What data is your AI agent actually working from?

000

Multiplayer @multiplayer.app · 03/08/2026

If only your coding agent could generate PRs from unsampled, pre-correlated, full-stack data… oh wait, it can 😏

000

Multiplayer @multiplayer.app · 30/07/2026

The best support ticket is the one that never gets filed …

100

Multiplayer @multiplayer.app · 27/07/2026

Issues are our answer to noisy alerts and duplicate PRs. We aggressively correlate data per session. We then aggressively deduplicate and group sessions into issues. The same bug appearing across a hundred user sessions becomes one issue. ✨

001

Multiplayer @multiplayer.app · 23/07/2026

Your terminal shows the debugging sessions you're running. The web dashboard tab shows every debugging session anyone on the team ran, today or three weeks ago.

000

Multiplayer @multiplayer.app · 20/07/2026

Why trust our word for it when you can watch the debugging agent catch and fix a bug yourself? One command. 👇

001

Multiplayer @multiplayer.app · 13/07/2026

One npm install. Try a demo. Setup existing project. Arrow keys, Enter. That’s it. That’s all you need to do to get full-stack, unsampled, runtime data into your coding agent.

000

Multiplayer @multiplayer.app · 08/07/2026

Targeted runtime visibility without managing your own infrastructure OR targeted runtime visibility with full control. No wrong choice, only great options 😉

000

Multiplayer @multiplayer.app · 07/07/2026

Dev: What kind of game is Multiplayer? Me: The kind were you squash bugs in prod. 😇 Check the live demo today. Just one command line: npm install -g @multiplayer-app/cli && multiplayer

010

Multiplayer @multiplayer.app · 30/06/2026

Multiplayer monitors your internal apps continuously and fixes bugs before your teammates notice them, automatically, with no manual debugging required.

The reality of internal tool debugging is scattered bug reports, vague repro steps, long resolution times and inefficient workflows

Multiplayer is a debugging agent that give you runtime visibility without missing any data

100

Multiplayer @multiplayer.app · 26/06/2026

“Full runtime context” that's sampled, missing request/response content and headers, and stops at service boundaries, isn't full runtime context.

100

Multiplayer @multiplayer.app · 24/06/2026

New Relic observes systems. Multiplayer fixes bugs. Unsampled, full-stack runtime data for your coding agent without the Ops-focused overhead and vendor lock-in.

100

Multiplayer @multiplayer.app · 20/06/2026

Sampled, incomplete data means plausible-looking PRs that fail in production. Multiplayer feeds your coding agent full-stack, unsampled runtime data so fixes actually work.

100

Multiplayer @multiplayer.app · 17/06/2026

Why Multiplayer's architecture is unique: → Session-based data collection → Local-first architecture that only sends data for new issues → Un-sampled, full-stack data → Automatic data correlation → Intelligent issue grouping, triage and deduplication → Release context and metadata included

000

Multiplayer @multiplayer.app · 11/06/2026

With Multiplayer there’s no proprietary agent lock-in, no bloated telemetry bills, just the runtime data your coding agent needs.

100

Multiplayer @multiplayer.app · 10/06/2026

Yes, there's a lot going on under the hood. No, you don't have to care about any of it. One copy/paste in your terminal and Multiplayer handles the rest: data gathering, triage, deduplication, coding agent prompting, PR creation. You just review and merge.

000

Multiplayer @multiplayer.app · 09/06/2026

AI agents generate code that breaks in prod. Use Multiplayer with your favorite coding agent to fix application bugs automatically with full-stack, unsampled runtime data.

010

Multiplayer @multiplayer.app · 08/06/2026

Session-based runtime data collection for coding agents. One copy/paste in your terminal, and you're done: npm install -g @multiplayer-app/cli && multiplayer

000

Multiplayer @multiplayer.app · 05/06/2026

Watching the debugging agent fix my bugs

000

Multiplayer @multiplayer.app · 04/06/2026

Multiplayer produces fewer, better PRs: local-first, full-stack, deduplicated, un-sampled, … better data for any coding agent (or developer).

100

Multiplayer @multiplayer.app · 03/06/2026

We capture the actual runtime context you (and your coding agent) need: • User clicks • Session metadata • Network requests • Console messages • Error rate metrics and errors (not sampled!) • Stack traces, spans, and logs (not sampled!) • Req/res headers and content from deep in your system

000

Multiplayer @multiplayer.app · 01/06/2026

Watching the debugging agent fix bugs in real-time. One copy/paste in your terminal, and you can too: npm install -g @multiplayer-app/cli && multiplayer

000

Multiplayer @multiplayer.app · 29/05/2026

One line. That’s it. All you need to start saving hours of debugging time.

000

Multiplayer @multiplayer.app · 28/05/2026

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

010

Multiplayer @multiplayer.app · 27/05/2026

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.

020

Multiplayer @multiplayer.app · 18/05/2026

Proud to see our Director of Community and DevRel and on stage at @cloudnativedaysitaly.org 💜 The cognitive cost of too much choice is 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.

020

Multiplayer @multiplayer.app · 18/03/2026

📅 Today, Wed, 18 MAR 2026 🕘 10:00 AM PDT | 1:00 PM EDT | 6:00 PM CET A panel on agentic observability with @tomjohnson3.bsky.social, @rustyrazorblade.com orblade.com, @michele.dash0.com, and @renice.bsky.social Hosted by @dash0.com and @leaddev.com Save your spot: leaddev.com/event/a-blue...

022

Multiplayer @multiplayer.app · 17/03/2026

Our CTO #Thomas Johnson will be joining @rustyrazorblade.com, @michele.dash0.com, and @renice.bsky.social for a panel on agentic observability, hosted by @dash0.com and @leaddev.com 📅 Tomorrow, WED, 18 MAR 2026 🕘 9:00 AM PST | 12:00 PM EST | 6:00 PM CET

210

Multiplayer @multiplayer.app · 10/03/2026

Same vibe: teams spending hours tuning sampling rates, retention policies, and log filters, instead spending a few minutes setting up full stack session recordings. 👀

000

Multiplayer @multiplayer.app · 06/03/2026

Modern session recording tools have evolved beyond user analytics to become essential debugging and development platforms that capture complete request/response payloads, distributed traces, and frontend-backend correlations.

210

Multiplayer @multiplayer.app · 26/02/2026

The real question isn't "can you capture external API data?" It's "do you capture it reliably, or does it require manual discipline (that often breaks down)?" With custom logging, you CAN technically capture everything. BUT...

100

Multiplayer @multiplayer.app · 25/02/2026

By the time you find out about an intermittent bug, the context is gone (sampled away or never captured)… or is it? 😇 Maybe you just don’t have the right tool to automatically record the full-stack, session-based context when the bug occurs.

000

Multiplayer @multiplayer.app · 23/02/2026

Fixing the debugging data problem requires rethinking what you collect and when you collect it. www.multiplayer.app/blog/why-obs...

000

Multiplayer @multiplayer.app · 20/02/2026

With Multiplayer, you get: ✅ 100% traces (no missing data or outrageous bills) ✅ Full request/response payloads and headers ✅ Internal AND external API calls ✅ User steps and frontend data (annotatable) ✅ Full-stack data correlated by session (no manual stitching)

000

Multiplayer @multiplayer.app · 18/02/2026

Complexity is a choice.

000

Multiplayer @multiplayer.app · 17/02/2026

Get started *for free* and in just a few minutes: multiplayer.app/docs

000

Multiplayer @multiplayer.app · 17/02/2026

Here’s how Multiplayer fits into it 👇 Our session-based correlation includes: ✓ Frontend actions ✓ Backend requests (un-sampled) ✓ External API calls ✓ Full req/res payloads ✓ One timeline

100

Multiplayer @multiplayer.app · 17/02/2026

Distributed tracing, APM platforms, and error monitoring have all improved correlation in their domains. But the full end-to-end correlation is still an emerging category 👇

100

Multiplayer @multiplayer.app · 17/02/2026

Instead of: Here are logs from 6 tools, figure it out. You get: Here's everything that happened in this user's session, already correlated. Here's how. 🧵

100

Multiplayer @multiplayer.app · 13/02/2026

What is spec-driven development? The approach: Write comprehensive specs → detailed technical plans → task breakdowns → then let AI generate code. Sound familiar? We used to call this Big Design Up Front (BDUF). We spent decades running away from it. 🧵

100

Multiplayer @multiplayer.app · 10/02/2026

Something feels backwards here.

000

Multiplayer @multiplayer.app · 29/01/2026

The difference between 'works fine' and 'production is down' is usually smaller than you think.

010

Multiplayer @multiplayer.app · 28/01/2026

GitHub Copilot can scaffold your payment integration in 30 seconds. But when customers report "checkout is broken ❌," you're spending 60 minutes manually correlating: • Browser DevTools for frontend data • Backend logs • Stripe's dashboard for API responses • Sentry for error traces ...

110

Multiplayer @multiplayer.app · 27/01/2026

"We need better observability" Adds 47 console.log() statements "We need to see API responses" Screenshots Postman for the 10th time "We need request headers" Digs through network tab while user waits OR... you could just use a full stack session recording with automatic request/response capture.

010

Multiplayer @multiplayer.app · 21/01/2026

Turns out it's a lot easier when you can just... see what happened.

010

Multiplayer @multiplayer.app · 20/01/2026

🎁 The best gift you can give your engineering team? Automatic visibility into request/response content AND headers from EVERY internal service call and external dependency. ❌ No more "Can you add more logs?" ✅ Just complete, correlated, end-to-end payloads, captured automatically

000

Multiplayer @multiplayer.app · 14/01/2026

Tried Multiplayer but didn’t finish setup? We want to understand why and we’ll compensate you for your time. Just book the time 👇 that works for you and tell us what we can do better. No sales pitch. Just feedback.

100