AI · alternatives · 2026
24 alternatives to Multiplayer
We built Multiplayer because we kept running into the same problem: coding agents connected to existing observability stacks inherit all the limitations those stacks were built with. Sampled traces, aggregated metrics, context that stops at service boundaries, missing request/response content from deep within the system. The PRs they produce look plausible and fail in production (i.e. “PR slop”). Multiplayer runs locally alongside Claude Code (Codex, Copilot, and Cursor coming soon) and captures full-stack, unsampled session data across your entire system. We collect everything from…
Multiplayer is a full-stack session recording tool for developers. It captures user interactions and technical data to help teams debug issues, run tests, and develop features. The product records sessions across the… Below are 24 products that do a similar job, ranked by how close each is in meaning and then by launch-day votes. Prices are shown for the 2 we have checked on their own sites, 2 of them free or with a free tier.
- 1
Replicas▲239Hey HN! I'm Connor, creator of Replicas. I'm a heavy Codex/Claude Code user, and I wanted to hand off tasks to agents like I would to an engineer - kick something off before work, let it scaffold while I'm at lunch, even come back to a ready PR. The problem: existing alternatives use workspace VMs that are black boxes. I have no access to any of them - they can't run tests, read logs, or use tools like the Playwright MCP (which I use to verify agents actually fixed what they claim to fix). Replicas gives agents real cloud workspaces where they can: - Run your test suite and read the…
Jun 2026 · replicas.dev · its alternatives →
- 2
Hi! I’m Nathan: an ML Engineer at Mozilla.ai: I built agent-of-empires (aoe): a CLI application to help you manage all of your running Claude Code/Opencode sessions and know when they are waiting for you. - Written in rust and relies on tmux for security and reliability - Monitors state of cli sessions to tell you when an agent is running vs idle vs waiting for your input - Manage sessions by naming them, grouping them, configuring profiles for various settings I'm passionate about getting self-hosted open-weight LLMs to be valid options to compete with proprietary closed models. One…
Jan 2026 · github.com · its alternatives →
- 3
Runtimefree tier, from $99/mo▲303Sandboxed coding agents for everyone on your team
May 2026 · runtm.com · its alternatives →
- 4
BearDrive▲191The open-source shared folder for your team's AI agents
Aug 2026 · beardrive.ai · its alternatives →
- 5
mpai▲105Make existing Codex and Claude Code sessions multiplayer
Aug 2026 · godfaddaai.github.io · its alternatives →
- 6
Hey folks — here’s a small experiment I hacked together over the weekend: https://cleoselene.com/ In short, it’s a way to build multiplayer games with no client-side game logic. Everything is rendered on the server, and the game itself is written as simple Lua scripts. I built this to explore a few gamedev ideas I’ve been thinking about while working on Abstra: - Writing multiplayer games as if they were single-player (no client/server complexity) - Streaming game primitives instead of pixels, which should be much lighter - Server-side rendering makes cheating basically…
Jan 2026 · cleoselene.com · its alternatives →
- 7
AgentGrid▲77Hi HN, I’m Michael, I built AgentGrid with my friend Souren because we were tired of losing our coding sessions and couldn't keep track of what was actually being built across our many projects. Our approach was to use an infinite canvas desktop app for the TUIs we already know and love, mainly claude + codex. We drew inspiration from Figma and Railway. Overtime we added image nodes, notes, terminals, coding editors, source control, etc. I wasn't sure about it at first. It took me a month to give the first version Souren built a real try. What got me was an Apple System Update I've been…
Jul 2026 · agentgrid.sh · its alternatives →
- 8
This project (Agents Observe) started as an exploration into building automation harnesses around claude code. I needed a way to see exactly what teams of agents were doing in realtime and to filter and search their output. A few interesting learnings from building and using this: - Claude code hooks are blocking - performance degrades rapidly if you have a lot of plugins that use hooks - Hooks provide a lot more useful info than OTEL data - Claude's jsonl files provide the full picture - Lifecycle management of MCP processes started by plugins is a bit kludgy at best The biggest takeaway is…
Apr 2026 · github.com · its alternatives →
- 9
I got tired of sharing AI demos with terminal screenshots or screen recordings. Claude Code already stores full session transcripts locally as JSONL files. Those logs contain everything: prompts, tool calls, thinking blocks, and timestamps. I built a small CLI tool that converts those logs into an interactive HTML replay. You can step through the session, jump through the timeline, expand tool calls, and inspect the full conversation. The output is a single self-contained HTML file — no dependencies. You can email it, host it anywhere, embed it in a blog post, and it works on mobile. Repo:…
Mar 2026 · github.com · its alternatives →
- 10
Hi HN! We’re the team behind Fiddler, and we recently built an Agent Cache feature. It works by capturing an LLM request/response pair and, once caching is enabled, serving subsequent matching calls locally so duplicate requests never hit the provider. It’s meant to reduce three pains that show up together in agent development: token cost, feedback-loop latency, and output non-determinism. We’d love to hear your thoughts.
Aug 2026 · telerik.com · its alternatives →
- 11
- 12
Single-agent LLMs suck at long-running complex tasks. We’ve open-sourced a multi-agent orchestrator that we’ve been using to handle long-running LLM tasks. We found that single LLM agents tend to stall, loop, or generate non-compiling code, so we built a harness for agents to coordinate over shared context while work is in progress. How it works: 1. Orchestrator agent that manages task decomposition 2. Sub-agents for parallel work 3. Subscriptions to task state and progress 4. Real-time sharing of intermediate discoveries between agents We tested this on a Putnam-level math problem, but the…
Feb 2026 · github.com · its alternatives →
- 13
Production-tested architecture for autonomous Claude agents
Apr 2026 · dvdshn.com · its alternatives →
- 14
Boxes.devfree tier, from $19/mo▲112Hi HN, we’re Nick and Drew, and we’re building boxes.dev – the first cloud-only agentic dev environment (ADE) that gives every Codex and Claude Code agent its own cloud computer. We’re two engineers who previously built Gem (co-founder/CTO and first hire), and we spent the last year coding almost exclusively using Codex and Claude Code. It’s been a huge change to how we code, and it’s been exhilarating seeing the models keep getting better – but we eventually realized that developing on localhost was holding us back: - Git worktrees are clunky to set up and use for parallelizing work -…
Jun 2026 · boxes.dev · its alternatives →
- 15
Claude Code is amazing for individuals but terrible for teams. I spent the last six months building my perfect mix of MCP servers, subagents, commands and skills. Claude Code writes 100% of the code now, but sharing this with my team? Painful. 1. Blog posts and workshops don't work (and don't scale) 2. Committing tools to N repos means N PRs. A tool changes? N more PRs. 3. Same tools, different files or folders for each AI assistant; not everyone uses Claude Code It is like 1999 all over again; FTPing files up to prod and versioning with ".bak" suffixes. So I built sx. It is your team's…
May 2026 · github.com · its alternatives →
- 16
Hi HN, I'm Tony. I built Grov (https://grov.dev/) because I hit a wall with current AI coding assistants: they are "single-player." The moment I kill a terminal pane or close a chat session, the high-level reasoning and architectural decisions generated during that session are lost. If a teammate touches that same code an hour later, their agent has to re-derive everything from scratch or read many documentation files for basically any feature implemented or bug fixed. I wanted to stop writing a lot of docs for everything just to give context to my agents or have to re-explain…
Jan 2026 · github.com · its alternatives →
- 17
We were spending a lot of time re-writing the same primitives in projects we were doing getting claude + codex + other harnesses communicating in real time. Many other projects forced us into using their framework or harness or into a specific stack. So we open sourced an SDK that acts as the messaging layer without the rest of it. Still early, but we've been working on it and found it useful.
Jun 2026 · github.com · its alternatives →
- 18
A file-based protocol for multi-agent AI workflows — portable, auditable, human-in-command. Cross-agent communication and persistent shared memory across runtimes, projects, and machines. No daemons, no central server.
May 2026 · oacp.dev · its alternatives →
- 19
Multiplayer AI coding - split the work and the cost
Apr 2026 · claudesquadlanding.vercel.app · its alternatives →
- 20
Instant code collaboration in the browser
2018 · replit.com · its alternatives →
- 21
Tool-agnostic TypeScript library for observing coding agent sessions. Built-in Cursor provider, extensible to Claude Code, Codex, and OpenCode. - vtemian/agentprobe
Mar 2026 · github.com · its alternatives →
- 22WB
Hi HN — we built agentcall.dev because the coding agent you're already running in your terminal shouldn't be trapped there. The pitch: your existing Claude Code, Codex, OpenClaw, or Cursor session joins a Google Meet, Teams, or Zoom call as itself. Same session, same context, same file access. It speaks, listens, screen-shares a localhost webpage, and can code live while you all talk about what it's building. What's actually on the call: • Voice in, voice out. Two modes — collaborative (sub-second via a voice intelligence layer tuned for latency) or direct (~2s, your coding agent itself…
Apr 2026 · its alternatives →
- 23
Recall▲16One developer solves it. Every developer knows it.
Feb 2026 · recall.team · its alternatives →
- 24
Hey HN, I think session transcripts written by coding agents like Claude Code and Codex are very interesting because they offer a detailed window into how work gets shipped. You can see the sequence of decisions that resulted in the final PR, what the agent got wrong, tools used etc. So I built a cli that analyzes these sessions and provides a local dashboard that shows what each session shipped (PRs, features), how much each PR cost, and recommendations for more effective usage. Concretely, it enriches each session with: - Outcome links: merged PRs, features shipped, files changed -…
Jul 2026 · github.com · its alternatives →
Also compare
Ranked by how close each launch is in meaning, then by votes. Prices were read from each product’s own site when checked and can change. Refine with your own description →