The debugging agent for developers. Try it for free: https://go.multiplayer.app/https://bsky.app/profile/multiplayer.apphttps://bsky.app/profile/multiplayer.app/post/3mteibbntks2pBig 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.18 Aug 2026 15:01 +0000at://did:plc:77jnrdckbf7tpbyk7pyckazj/app.bsky.feed.post/3mteibbntks2phttps://bsky.app/profile/multiplayer.app/post/3msq6dbkiqf2cMyth: 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 👇10 Aug 2026 13:10 +0000at://did:plc:77jnrdckbf7tpbyk7pyckazj/app.bsky.feed.post/3msq6dbkiqf2chttps://bsky.app/profile/multiplayer.app/post/3msg4cccua32sWhen something breaks on mobile, Multiplayer captures it and sends your coding agent the exact runtime data it needs to fix it automatically.06 Aug 2026 13:07 +0000at://did:plc:77jnrdckbf7tpbyk7pyckazj/app.bsky.feed.post/3msg4cccua32shttps://bsky.app/profile/multiplayer.app/post/3msb3bmtrm52uWhat data is your AI agent actually working from?04 Aug 2026 13:05 +0000at://did:plc:77jnrdckbf7tpbyk7pyckazj/app.bsky.feed.post/3msb3bmtrm52uhttps://bsky.app/profile/multiplayer.app/post/3ms6kh5ipzk2iIf only your coding agent could generate PRs from unsampled, pre-correlated, full-stack data… oh wait, it can 😏03 Aug 2026 12:59 +0000at://did:plc:77jnrdckbf7tpbyk7pyckazj/app.bsky.feed.post/3ms6kh5ipzk2ihttps://bsky.app/profile/multiplayer.app/post/3mru6dxi2es2iThe best support ticket is the one that never gets filed …30 Jul 2026 09:55 +0000at://did:plc:77jnrdckbf7tpbyk7pyckazj/app.bsky.feed.post/3mru6dxi2es2ihttps://bsky.app/profile/multiplayer.app/post/3mrrbrhvdxk27The 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. 👇29 Jul 2026 06:19 +0000at://did:plc:77jnrdckbf7tpbyk7pyckazj/app.bsky.feed.post/3mrrbrhvdxk27https://bsky.app/profile/multiplayer.app/post/3mrmrzfxml22vIssues 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. ✨27 Jul 2026 11:26 +0000at://did:plc:77jnrdckbf7tpbyk7pyckazj/app.bsky.feed.post/3mrmrzfxml22vhttps://bsky.app/profile/multiplayer.app/post/3mrcx4dqod22wYour 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.23 Jul 2026 13:31 +0000at://did:plc:77jnrdckbf7tpbyk7pyckazj/app.bsky.feed.post/3mrcx4dqod22whttps://bsky.app/profile/multiplayer.app/post/3mr3iiflqpc2eWhy trust our word for it when you can watch the debugging agent catch and fix a bug yourself? One command. 👇20 Jul 2026 14:20 +0000at://did:plc:77jnrdckbf7tpbyk7pyckazj/app.bsky.feed.post/3mr3iiflqpc2ehttps://bsky.app/profile/multiplayer.app/post/3mqjwabo4q224One 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.13 Jul 2026 14:38 +0000at://did:plc:77jnrdckbf7tpbyk7pyckazj/app.bsky.feed.post/3mqjwabo4q224https://bsky.app/profile/multiplayer.app/post/3mq5dx2uiyk2wTargeted runtime visibility without managing your own infrastructure OR targeted runtime visibility with full control. No wrong choice, only great options 😉08 Jul 2026 14:39 +0000at://did:plc:77jnrdckbf7tpbyk7pyckazj/app.bsky.feed.post/3mq5dx2uiyk2whttps://bsky.app/profile/multiplayer.app/post/3mq37yhxbxs2oDev: 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 && multiplayer07 Jul 2026 18:23 +0000at://did:plc:77jnrdckbf7tpbyk7pyckazj/app.bsky.feed.post/3mq37yhxbxs2ohttps://bsky.app/profile/multiplayer.app/post/3mpqmn6fpqc2iToken optimization is the new tokenmaxxing.03 Jul 2026 13:10 +0000at://did:plc:77jnrdckbf7tpbyk7pyckazj/app.bsky.feed.post/3mpqmn6fpqc2ihttps://bsky.app/profile/multiplayer.app/post/3mpm5dc2gb22mWhen 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. 👀01 Jul 2026 18:25 +0000at://did:plc:77jnrdckbf7tpbyk7pyckazj/app.bsky.feed.post/3mpm5dc2gb22mhttps://bsky.app/profile/multiplayer.app/post/3mpj2uu7qzk2uMultiplayer monitors your internal apps continuously and fixes bugs before your teammates notice them, automatically, with no manual debugging required.30 Jun 2026 13:04 +0000at://did:plc:77jnrdckbf7tpbyk7pyckazj/app.bsky.feed.post/3mpj2uu7qzk2uhttps://bsky.app/profile/multiplayer.app/post/3mp6zs5balq2h“Full runtime context” that's sampled, missing request/response content and headers, and stops at service boundaries, isn't full runtime context.26 Jun 2026 13:18 +0000at://did:plc:77jnrdckbf7tpbyk7pyckazj/app.bsky.feed.post/3mp6zs5balq2hhttps://bsky.app/profile/multiplayer.app/post/3mp4uaq7lhk2iWe 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 🧵25 Jun 2026 16:33 +0000at://did:plc:77jnrdckbf7tpbyk7pyckazj/app.bsky.feed.post/3mp4uaq7lhk2ihttps://bsky.app/profile/multiplayer.app/post/3mozo5vdjqs2lNew Relic observes systems. Multiplayer fixes bugs. Unsampled, full-stack runtime data for your coding agent without the Ops-focused overhead and vendor lock-in.24 Jun 2026 10:06 +0000at://did:plc:77jnrdckbf7tpbyk7pyckazj/app.bsky.feed.post/3mozo5vdjqs2lhttps://bsky.app/profile/multiplayer.app/post/3mouxstmz5i2dYes, 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.22 Jun 2026 13:16 +0000at://did:plc:77jnrdckbf7tpbyk7pyckazj/app.bsky.feed.post/3mouxstmz5i2dhttps://bsky.app/profile/multiplayer.app/post/3mopz7vqpjk2fSampled, incomplete data means plausible-looking PRs that fail in production. Multiplayer feeds your coding agent full-stack, unsampled runtime data so fixes actually work.20 Jun 2026 13:57 +0000at://did:plc:77jnrdckbf7tpbyk7pyckazj/app.bsky.feed.post/3mopz7vqpjk2fhttps://bsky.app/profile/multiplayer.app/post/3mol4i6bsp225Multiplayer is now open source. The debugging agent that connects your coding agent to production to fix application bugs automatically is publicly available under MIT. 👇 https://github.com/multiplayer-app/multiplayer18 Jun 2026 15:12 +0000at://did:plc:77jnrdckbf7tpbyk7pyckazj/app.bsky.feed.post/3mol4i6bsp225https://bsky.app/profile/multiplayer.app/post/3moihgjrk6k2bWhy 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 included17 Jun 2026 13:50 +0000at://did:plc:77jnrdckbf7tpbyk7pyckazj/app.bsky.feed.post/3moihgjrk6k2bhttps://bsky.app/profile/multiplayer.app/post/3mofvpf7f4c2pThe 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. [contains quote post or other embedded content]16 Jun 2026 13:28 +0000at://did:plc:77jnrdckbf7tpbyk7pyckazj/app.bsky.feed.post/3mofvpf7f4c2phttps://bsky.app/profile/multiplayer.app/post/3modg75awk22uHow 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.15 Jun 2026 13:45 +0000at://did:plc:77jnrdckbf7tpbyk7pyckazj/app.bsky.feed.post/3modg75awk22uhttps://bsky.app/profile/multiplayer.app/post/3mnzfrngm3f2kWith Multiplayer there’s no proprietary agent lock-in, no bloated telemetry bills, just the runtime data your coding agent needs.11 Jun 2026 14:11 +0000at://did:plc:77jnrdckbf7tpbyk7pyckazj/app.bsky.feed.post/3mnzfrngm3f2khttps://bsky.app/profile/multiplayer.app/post/3mnxgxu442c2gWouldn’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. 👀 [contains quote post or other embedded content]10 Jun 2026 19:27 +0000at://did:plc:77jnrdckbf7tpbyk7pyckazj/app.bsky.feed.post/3mnxgxu442c2ghttps://bsky.app/profile/multiplayer.app/post/3mnws6ac5bb2nYes, 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.10 Jun 2026 13:15 +0000at://did:plc:77jnrdckbf7tpbyk7pyckazj/app.bsky.feed.post/3mnws6ac5bb2n