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 · 29/07/2026

The token optimization advice everyone is missing: An agent is only as good as the environment it operates in. And traditional observability wasn't designed for agents with its sampled data, aggregated metrics and siloed context that stops at system boundaries. 👇

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

Reposted by Multiplayer

Steph Johnson @bkstephj1.bsky.social · 15/07/2026

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?'

111

Reposted by Multiplayer

Tom Johnson @tomjohnson3.bsky.social · 14/07/2026

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.

011

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 · 03/07/2026

Token optimization is the new tokenmaxxing.

100

Multiplayer @multiplayer.app · 01/07/2026

When we started building Multiplayer's debugging agent, we made the same mistake almost everyone makes. We gave our coding agent access to observability data and expected it to figure out what was relevant. It didn't. 👀

100

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 · 25/06/2026

We know what you're thinking. 'Unsampled' usually means 'we sample less than Datadog.' 'Full-stack' usually means 'we link out to your APM for the backend data.' 'Pre-correlated' usually means 'we correlated what we had, which wasn't much.' Multiplayer is different 🧵

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 · 22/06/2026

Yes, we collect unsampled traces. No, they're not repackaged from your existing APM. Yes, that includes request/response content and headers. No, we don't fill gaps with guesses. There are no gaps.

000

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 · 16/06/2026

The Jellyfish data makes the point cleanly: you can't fix a data problem with more compute. If more tokens and better models produce the same PR quality as before, the bottleneck was not the compute.

010

Multiplayer @multiplayer.app · 15/06/2026

How do you capture unknown-unknowns without blanket coverage, all the time? Answer: with session-based collection with broad triggers (any error, any anomaly). You're not deciding in advance what to instrument; you're automatically storing only failure events.

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

Wouldn’t it be nice to never have to worry about this again? This is the exact type of problem we built the debugging agent to solve. 👀

010

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 · 02/06/2026

Targeted capture beats constant collection. Change my mind.

100

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 · 25/05/2026

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

010

Reposted by Multiplayer

Tom Johnson @tomjohnson3.bsky.social · 21/05/2026

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.bsky.social ☕️

021

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 · 14/05/2026

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

110

Multiplayer @multiplayer.app · 13/05/2026

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.

010

Multiplayer @multiplayer.app · 16/04/2026

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

000

Multiplayer @multiplayer.app · 15/04/2026

Decision fatigue is real in cloud-native development and most of it hits before you write a single line of code. 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.

010

Multiplayer @multiplayer.app · 14/04/2026

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.

000

Multiplayer @multiplayer.app · 08/04/2026

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

000

Multiplayer @multiplayer.app · 07/04/2026

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

010