Lightnews — Scholar-powered news

Multiplayer

@multiplayer.app

55 followers 180 following 560 posts

Full stack session recording. End-to-end visibility in a single click. Capture once, use for debugging, testing, support, feature development ... Try it for free: multiplayer.app

Posts Media Videos Starter Packs

Pinned

Multiplayer @multiplayer.app · 13d

Full stack session recordings: record. code. fix. repeat.

Multiplayer @multiplayer.app · 4h

Full article on how we approach continuous recording: www.multiplayer.app/blog/continu...

Continuous session recording, reimagined

Record sessions in the background: Multiplayer saves recordings the moment bugs or anomalies occur, making it effortless to capture elusive, hard-to-reproduce problems.

www.multiplayer.app

Multiplayer @multiplayer.app · 4h

Also… Remote recording is now in beta. Silently enable recording of user experiences, ensuring nothing gets lost in translation from vague bug reports.

Multiplayer @multiplayer.app · 4h

You can also enable continuous recording which keeps a lightweight rolling buffer that auto-saves frontend + backend exceptions and errors the moment they appear.

No repro steps. No missed bugs.

Multiplayer @multiplayer.app · 4h

Yes, you can absolutely capture on-demand session replays.

Manually start / stop to capture the exact reproduction steps

BUT…

Multiplayer @multiplayer.app · 4h

Most session replay tools force a tradeoff:

🎥 Record on demand → you miss what happens outside the window.
📼 Record everything → you drown in noise and costs.

We took a different approach 🧵

Multiplayer @multiplayer.app · 23h

Sometimes the frontend data isn’t enough.

Sometimes (okay, always) you also want to know what happened in the backend.

Multiplayer @multiplayer.app · 2d

“Is this the real bug? Or it’s just fantasy?” 👈 Strong start to my chat with Freddie Mercury about our latest bug.

Luckily, Multiplayer caught the whole performance: frontend, backend, and the error’s big solo.

Multiplayer @multiplayer.app · 4d

Full guide: www.multiplayer.app/docs/configu...

Multiplayer API Key | Multiplayer Documentation | Setup Guides for Full-Stack Session Recordings & More

The Multiplayer API key authenticates your application when sending session recording data to Multiplayer. Without it, we can’t associate your frontend or backend data with your project. The API key e...

www.multiplayer.app

Multiplayer @multiplayer.app · 4d

The Multiplayer API key authenticates your application when sending session recording data to Multiplayer.

The API key ensures that session recordings, traces, logs, and other data are securely tied to your account.

Multiplayer @multiplayer.app · 4d

👀 Did you know that with Multiplayer you can:

👉 Use a single API authentication key for both frontend and backend data,

OR

👉 Generate separate API authentication keys for frontend and backend if you want stricter separation or different access scopes

Multiplayer @multiplayer.app · 5d

(3) Notebook: add the API requests that reproduce the flow + assertions for expected outcomes.

(4) AI via MCP: “Generate a patch to satisfy this recording’s notes”

(5) Run the notebook to validate the fix; attach results to the PR.

(6) Keep the recording + notebook as living documentation.

Multiplayer @multiplayer.app · 5d

Here’s an example of a concrete SDD workflow with Multiplayer:

(1) Capture a session where the bug or desired behavior appears.

(2) Annotate the exact UI state, API call, and trace span with requirements.

Multiplayer @multiplayer.app · 5d

Specs don’t have to be static documents anymore.

With Multiplayer, they can be:

✅ Captured from real behavior
✅ Annotated with requirements
✅ Run as executable notebooks
✅ Fed directly into AI tools for accurate fixes & features

Multiplayer @multiplayer.app · 5d

A full stack session recording + annotations fits perfectly with this shift:

✔️ Frontend screens + backend traces
✔️ Requests/responses + headers
✔️ Notes, sketches, requirements

Executable with Notebooks, shareable with your team, and consumable by AI through our MCP server.

Multiplayer @multiplayer.app · 5d

So why the renewed attention now?

Because AI needs structured context.

A good spec → fewer hallucinations, more accurate code, tests, and features.

Without it, copilots and agents are left guessing.

Multiplayer @multiplayer.app · 5d

Spec-driven development flips the script:

‣ The spec is the source of truth
‣ It’s machine-readable and executable
‣ From one spec, you can generate docs, SDKs, tests, and implementations

Think OpenAPI, gRPC protos, GraphQL SDL.

Multiplayer @multiplayer.app · 5d

Traditionally, specs were an afterthought.

Teams wrote them once, then let them drift while “the real work” happened in code.

Code became the source of truth. Specs became stale PDFs or wikis.

Multiplayer @multiplayer.app · 5d

Spec-driven development is making a comeback.

Why? Because AI-assisted coding has changed the game.

Let’s break it down 👇

Multiplayer @multiplayer.app · 6d

With zero sampling, you don’t rely on luck. You get:

✔️ Confidence that the trace you need is there

✔️ Precision debugging across the full stack

✔️ AI-ready context: feed your IDE/copilot full correlated data + annotations

Multiplayer @multiplayer.app · 6d

You can also enrich your session recordings with request/response content and headers.

So your replays carry not only what happened, but how and why.

Multiplayer @multiplayer.app · 6d

How to do it differently:

‣ We create a unique trace context for every session
‣ We override sampling at root so all spans are kept
‣ As requests flow across services, every span preserves “sampled = true”
‣ We correlate all that backend data with frontend UI actions in a unified timeline

Multiplayer @multiplayer.app · 6d

Replay tools usually stop at the browser.

If they capture backend data at all, they inherit the sampling behavior of your APM tool or require fragile, manual setups.

The result: fragmented context and painful debugging across tools.

Multiplayer @multiplayer.app · 6d

🔍 The sampling problem

APM tools ingest everything, but to control cost they sample aggressively.

That’s okay for system health and trend monitoring, but when you’re debugging a user issue, you may miss the exact trace you needed.

Multiplayer @multiplayer.app · 6d

Most tools sample your telemetry, leaving gaps when you desperately need precise data.

Here’s how 👇 to get * unsampled * backend traces, and then stitch them to your frontend sessions.

Multiplayer @multiplayer.app · 7d

For us that’s meant designing MCP tools that help developers fix bugs and build features faster by feeding AI copilots the right context: from full-stack traces to annotated session data.

If you’re experimenting with MCP, think small, scope tightly, and expand based on how users actually work.