Alternatives
Products that do what agent-talk does
Enabling coding agents to work together
- 1
- 2
- 3AL
Apr 2026 · juanpabloaj.com
- 4
- 5
- 6
- 7
- 8
- 9
- 10
- 11
- 12
- 13
- 14
- 15WB
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
- 16
- 172C
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
- 18
- 19
- 20
Hi HN, I saw one friction point when working as part of a team that uses coding agents extensively - there is nothing to enable coordination between agent used by people in a team. Many times my agent would ask me to decide upon something with a fellow teammate, for which I have to serve as the network layer. So I built Parley where agents can connect to the hub over MCP with their own team-scoped token. An agent addresses a teammate's agent by name and ask questions/handover tasks. Agents can also use file claims to signal what files they are working on, to highlight overlapping work.…
26d ago · parley.weldra.dev
- 21AC
Most people right now are talking to their AI agents through Telegram bots, WhatsApp, Discord, or just copying and pasting between terminals. There’s still no simple, straightforward way for agents to message each other directly. AgentBus solves exactly that. You register each agent with one quick API call. Then they can send messages to each other using simple REST calls. No servers, no queues, no WebSockets, no extra infrastructure. Just drop in a tiny polling loop and your agents can now talk, collaborate, and run real workflows across laptops, VPSes, clouds — whatever. You can also…
Mar 2026 · agentbus.org
- 22
Recently I've been running more and more agents in parallel however I noticed that they have no task context of what the other agents are doing even when a lot of work is interconnected It's like taking Slack away from a team. Agents duplicate work, make conflicting changes, and step on each others' toes simply because they can't talk to each other. Concord is an MCP + CLI that lets coding agents claim work, see what other agents are doing, and message each other live.
10d ago · github.com
- 23
- 24AL
Hello HN! I wanted to share a small MCP + web app I built to solve a problem at work. Essentially, we’ve been doing great when working with agents 1:1, but collaboration has been a struggle. E.g. when I have to collaborate with a teammate and share context or handoff work usually what I would do is create a markdown with my agent, paste in slack, then my teammate will copy and paste it to their agent and vice-versa. To make our lives easier, I built AgentCouch, a “messaging app” for agents that lets our agents chat and hand off work directly in shared rooms. Humans can also watch the…
Jul 2026 · agentcouch.dev
Ranked by how close each launch is in meaning, then by votes. Refine with a description →