Loading video...

Video Failed to Load

Go Home

Most AI coding tools focus on helping one developer work faster. Reason is taking a different approach. The idea of a multiplayer coding agent is interesting because software development rarely happens in isolation. Reason lets AI agents and humans work together, split tasks, debug issues and verify solutions instead...

10,892 views • 4 days ago •via X (Twitter)

34 Comments

Kiều B2's profile picture
Kiều B24 days ago

@reasonmachines Collaborative AI coding will enhance development efficiency

useetek's profile picture
useetek4 days ago

@reasonmachines There's a good reason to look at this before forming a strong opinion.

Sapient's profile picture
Sapient4 days ago

@reasonmachines ai is def the future

Senius's profile picture
Senius4 days ago

@reasonmachines A lot depends on how we see things

🚢Behrooz Alinezhad's profile picture
🚢Behrooz Alinezhad4 days ago

@reasonmachines Collaborative AI agents could make coding much more efficient.

Lingg's profile picture
Lingg4 days ago

@reasonmachines Collaborative coding agents will redefine how developers work

Kim Vault's profile picture
Kim Vault4 days ago

@reasonmachines how many people are on the reasonmachines team

Pham Toi's profile picture
Pham Toi4 days ago

@reasonmachines AI tools improve collaboration together.

dens club's profile picture
dens club4 days ago

@reasonmachines same burden in every product means the layer missed

MUBBY's profile picture
MUBBY4 days ago

@reasonmachines I like this post because there is something to learn from it

Arjantit's profile picture
Arjantit4 days ago

@reasonmachines 👀

HANNAH🔥KRYPT's profile picture
HANNAH🔥KRYPT4 days ago

@reasonmachines reasonmachines is building multiplayer coding agents where humans + AIs collaborate in parallel with shared context to split, debug and verify work, not just autocomplete faster.

Mookie's profile picture
Mookie4 days ago

@reasonmachines You’re so right brother

P.Linh♡'s profile picture
P.Linh♡4 days ago

@reasonmachines Parallel collaboration truly speeds up development.

Arix's profile picture
Arix4 days ago

@reasonmachines Different approach makes it batter

sasak's profile picture
sasak4 days ago

@reasonmachines multiplayer agents beat a single agent for debugging issues

Fawaz 🪶's profile picture
Fawaz 🪶4 days ago

@reasonmachines Multiplayer coding could be a big shift if agents can actually share context and verify each other’s work

Maureen Archibong | 0% trading fee on coinup's profile picture
Maureen Archibong | 0% trading fee on coinup4 days ago

@reasonmachines Having multiple agents work on different parts of a project could save a lot of time, especially when debugging gets messy. 👀

Duck Daily 🦆's profile picture
Duck Daily 🦆4 days ago

@reasonmachines reasonmachines shows multiplayer coding could speed up projects dramatically

Northstar | Web3 🌊's profile picture
Northstar | Web3 🌊4 days ago

@reasonmachines Shared context across sessions could still be out of date if a developer changes a dependency after a session ends. In that case, the AI might generate code that compiles locally but fails on the CI server due to the mismatched version.

Macro Bombastic's profile picture
Macro Bombastic4 days ago

@reasonmachines multiplayer agents make sense tbh, solo coding is kinda overrated

Đường Phát's profile picture
Đường Phát4 days ago

@reasonmachines team coding with reasonmachines boosts productivity and reduces bugs

𝐁𝐞𝐧𝐳 's profile picture
𝐁𝐞𝐧𝐳 4 days ago

@reasonmachines this how teams really move together

Faisal's profile picture
Faisal4 days ago

@reasonmachines Multiplayer makes way more sense than another solo copilot. The messy part of real projects is the handoff between people, not the typing speed

Loc Capital's profile picture
Loc Capital4 days ago

@reasonmachines but multiple agents could actually slow down debugging

𝗘𝗹𝗹𝗮's profile picture
𝗘𝗹𝗹𝗮4 days ago

@reasonmachines The real breakthrough is AI agents collaborating, not just coding faster.

Bryan Quartz's profile picture
Bryan Quartz4 days ago

@reasonmachines would you trust it on prod code?

ABBA's profile picture
ABBA4 days ago

@reasonmachines Clear structure supports better understanding

Xavi's profile picture
Xavi4 days ago

@reasonmachines multiplayer agents are cool, but shared context is the hard part

Shuvo's profile picture
Shuvo4 days ago

@reasonmachines This approach could change development teamwork

Zaric's profile picture
Zaric4 days ago

@reasonmachines love the multiplayer angle, feels way more real-world

Duc Crypto's profile picture
Duc Crypto4 days ago

@reasonmachines maybe still too dependent on one agent despite multiplayer claim

Lenda Noire's profile picture
Lenda Noire4 days ago

@reasonmachines this team collaboration vibe feels right. can’t wait to see how it changes the game for devs working together long distance

Tazman's profile picture
Tazman4 days ago

@reasonmachines multiplayer coding agents splitting tasks beats single agent bottlenecks every time

Related Videos

We're only year 3 of a decade (if not multi-decades) long transformation of work. 3 years ago we bet on building an horizontal platform for work with agents, a chance to invent a new operating system for companies, from scratch, with AI as a fundamental premise. Many people considered us crazy for going after that, praising verticalized AI products as the winning strategy. But here's the thing: the time horizon of tasks successfully handled by agents has been predictively increasing form minutes to hours and will in all likelihood reach the equivalent of days and weeks of human work equivalent in the coming quarters. This is were verticalized and/or single-player AI falls short. Single-player tools, one person, one agent, confined to your machine is the wrong architecture for what's coming. We're shifting from using AI to produce things, to managing fleets of agents that do the producing. 3 years ago I wrote[1]: "ChatGPT is the Pong of LLMs. [...] Imagine, one day we'll get the DOOM, Civ, Red Alert, and Counter Strike of LLMs. Let alone multiplayer modes." Weeks long tasks in companies are inherently collaborative and mechanically spanning multiple teams. The new bottleneck in harnessing agents within organizations is coordination: multiple humans and multiple agents need to work together, with shared context, shared tools, shared goals. Agents that can hand work off to other agents or surface decisions to the right person at the right time. Humans who can review, steer, and step in without losing the thread. Teams that can run parallel workstreams and actually stay aligned. This is Multiplayer AI, and that's what we've been building at Dust. Across Datadog, Clay, Persona, 1Password, Doctolib and 3,000+ organizations globally, we've watched teams figure out what this looks like in practice. 300,000+ agents deployed. 70% weekly active. 240%+ NRR. Today we're announcing a $40M Series B with Abstract, Sequoia, Snowflake, and Datadog to accelerate our vision. Designing the right interfaces for multiplayer AI is the next frontier. Join us to redefine work by defining multiplayer AI.

Stanislas Polu

3,206,770 views • 5 months ago

Most AI coding setups right now look something like this: one agent in a terminal, another in a browser tab, a chat window somewhere else, and you in the middle copy-pasting diffs like a very tired air traffic controller. JetBrains just launched something aimed right at that mess. It's called JetBrains Air, and it lives inside their IDEs. The short version: Air lets you direct multiple coding agents, run their tasks in parallel, and review their work without ever leaving your IDE. Here's what stood out to me: 👇 1. You pick the agents. Air isn't tied to a single agent or provider. You can use the ones you already like. That matters more than it sounds, because the "best" coding agent changes every few months, and nobody wants to rebuild their whole workflow each time. 2. Parallel work without losing track. You can run several agent sessions at once, even across different projects. Air shows you where your attention is needed, so you're not hopping between tabs to find out which agent is stuck. 3. You stay in control. You can follow what each agent is doing, give it input, inspect the changes, and review the output before accepting anything. Nothing lands in your codebase just because an agent felt confident. 4. The agents get IDE smarts too. This is the part I find most interesting. JetBrains IDEs already have great code navigation, refactoring, testing, and debugging. With Air, both you and your agents work with that context. So the agents aren't guessing blind inside a chat box, and when something needs a human, the real tools are right there. The bigger idea here is that agents become part of your development workflow instead of a separate chat you keep switching to. There's also a nice bonus. For a limited time, JetBrains is offering Junie Lite for free (fair use applies). It's their own coding agent paired with a highly efficient model. It isn't pitched as a frontier-level agent. Think of it as a solid, free baseline for trying out Air and running everyday tasks. Air works in any JetBrains IDE and is in early access right now. If you write code with agents, give it a try: #ad

Mushfiq Sajib

40,469 views • 13 days ago

Mark Zuckerberg says the future of coding is closer than we think: AI agents inside Meta are being built not as generic developer tools, but to push Llama research forward — fully integrated into their workflow. He predicts that within 12–18 months, most of the code for these efforts could be written by AI itself — not simple autocomplete, but systems that take goals, run tests, fix bugs, improve performance, and even write higher-quality code than many skilled engineers. The real takeaway? This is only one part of a massive AI landscape, and no single company will dominate it all. Meta is building its own internal agents designed specifically to advance Llama research — deeply connected to their toolchain rather than built for enterprise customers. He expects that within the next year to year-and-a-half, AI will be writing most of the code in these projects, going far beyond autocomplete — understanding goals, running experiments, finding issues, and continuously improving systems. And according to him, this shift will become a core driver of how AI itself evolves. Meta is investing heavily in coding and research agents deeply integrated into their own systems, focused on advancing Llama rather than building broad enterprise tools. He expects AI will soon move beyond autocomplete to fully goal-driven coding — testing, debugging, improving, and producing high-quality results. But in his view, the AI revolution is too big for any single winner — multiple players and approaches will shape the future.

Ian Miles Cheong

20,561 views • 8 months ago