Nicheloom

Market intelligence for builders — see what's gaining traction before it's crowded.

Parley

your coding agent can talk to a teammate's agent

Details

External ID
49257824
Source
HN
Company
—
Product
Parley
Website domain
weldra.dev
Launched
Aug. 11, 2026
Cohort
—
Upvotes
9
Upvotes percentile
0.5309139784946236
Tags
—
Fetched at
Sept. 10, 2026, 5:32 a.m.
Updated at
Sept. 10, 2026, 5:32 a.m.

Description

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. Everything is recorded for audit.If an agent needs human decision/approval, it can ping over Slack/Telegram, and get replies over the same.The hard part was making an agent wake up from an idle session and start working, so I built an optional feature called Claude Live Wake. If the exact project session is already running, Parley can wake the idle Claude session using channels, and notify it that eligible work is waiting.Another challenge was trust- anything another agent sends has to be treated as untrusted input. Every message is tagged by origin - human, agent, or system. Message bodies only enter an agent when it explicitly fetches instead of injecting mid turn. These are specifically mentioned to be treated as string messages instead of prompts/commands.

Enrichment

Theme
developer tools for AI agents
Vertical
Horizontal
Function
Agent / copilot
Audience
Developer
AI stance
AI-native
Project type
Commercial product
Normalized one-liner
enable coding agents to collaborate
Manually corrected
False

Could you build this?

Partial While the front-end dashboard and webhook integration are standard web dev, building durable multi-agent message queues, distributed soft file-locking, and Model Context Protocol (MCP) server relays across environments requires non-trivial backend systems design.

What it would actually take: The architecture requires a distributed message broker (e.g., Redis Streams, NATS, or Postgres queues) running behind an MCP protocol server, with WebSocket/SSE connections back to developer machines. The hard pieces are distributed state management: handling asynchronous disconnects, durable delivery with replay offsets, conflict detection/soft-locking across disjoint local file trees, and injection-prevention sanitization between autonomous agents.

Discussion

5 comments analyzed.

Competitors

Other products that read as similar to this one — 581 launches clear the similarity bar, closest 8 shown.

Attention rank: #313 of 582 (itself plus its competitors, highest first — normalized so YC and Product Hunt are compared fairly).

Launched 282 days after the earliest competitor.

Other launches for this product

Same idea, different domain

Nobody's really built a agent / copilot tool for Agriculture yet.