Independent use will determine whether Parley enables reliable, auditable questions and task handoffs between coding agents operated by different teammates.
state: expiredheat: lowuncertainty: highconvergesscott: mediumagent-harnesses multi-agent-coordination mcpWeldra
What is this?
Parley is presented in a Show HN launch as a tool that lets one teammate’s coding agent ask questions of, or hand tasks to, another teammate’s agent, with an emphasis on reliable and auditable collaboration. The supplied material associates it with Weldra and broadly supports the value of transparent, accountable agent handoffs, but it does not establish Parley’s implementation, MCP usage, adoption, or independent reliability. The hackathon snippet mentions a Parley project in a multi-agent context, though it is unclear whether that is the same product.
Why it matters to Scott
Parley’s stated design converges with Scott’s model-to-model delegation, explicit handoff contracts, and auditable agent control-plane work, potentially providing an external comparison for Paperclip. Relevance is medium because the evidence establishes only launch claims, not Parley’s implementation, MCP usage, adoption, or independent reliability.
dev:technology.paperclipdev:concept.deterministic-agent-control-planedev:concept.model-to-model-delegationip:concept.evidence-packageip:concept.agent-receiptsradar:claude-code-session-messagingradar:concept.multi-agent-coordination
queries asked of Scott's wikis
- cross-teammate coding-agent coordination
- auditable agent questions and task handoffs
- human oversight in multi-agent coding workflows
- MCP for agent-to-agent communication
- shared context and permissions across coding agents
- reliability tests for agent handoff protocols
Measured heat
no measured readings yet — the hourly heat pass fills this in
How the heat travelled
no chain yet — the hourly chain pass fills this in
Evidence (2) — ⭐ canonical anchor
Interpretation history
2026-08-14T18:37:35Z
No independent deployment, reliability result, or audit evidence followed the launch-thread testimonial, so the product-specific hypothesis has failed to develop into an active signal. Broader interest in agent messaging remains, but Parley no longer merits its own watch without substantive new use evidence.
2026-08-12T17:39:59Z
A commenter now claims hands-on use and specifically endorses Parley’s file-claim and trust mechanisms, providing the first weak external usage signal. The anecdote offers no demonstrated cross-team reliability, audit evidence, or sustained deployment, so it does not yet corroborate the product-specific hypothesis.
2026-08-11T15:01:56Z
Agent-exchange independently supports demand for terminal-agent messaging and coordination, moving the broader pattern beyond a single launch. It does not validate Parley’s implementation, cross-team reliability, auditability, or independent use, so the product-specific hypothesis remains open.
2026-08-11T14:28:21Z
evidence attached: hn.story.49257861 — Independent corroboration of terminal-agent messaging and coordination directly bears on the open cross-agent handoff hypothesis.
2026-08-11T13:55:26Z
The small engagement increase adds no independent use, implementation evidence, or reliability results, so Parley remains an unvalidated launch claim rather than a demonstrated cross-team coordination system.
2026-08-11T13:38:13Z
grounded: converges/medium — Parley’s stated design converges with Scott’s model-to-model delegation, explicit handoff contracts, and auditable agent control-plane work, potentially providi
2026-08-11T13:35:41Z
case created — Parley exposes a concrete MCP-based coordination mechanism with team-scoped identities and audit trails.
Decision trace
- 08-15 04:37expireNo independent deployment, reliability result, or audit evidence followed the launch-thread testimonial, so the product-specific hypothesis has failed to develop into an active signal. Broader interes
- 08-15 04:37alert_silentThe staleness trigger adds no consequential evidence or event; expiry can occur quietly, with any future independent deployment or reliability result reopening the case.
- 08-15 04:37alert_routeThe staleness trigger adds no consequential evidence or event; expiry can occur quietly, with any future independent deployment or reliability result reopening the case.
- 08-13 03:39repriceA commenter now claims hands-on use and specifically endorses Parley’s file-claim and trust mechanisms, providing the first weak external usage signal. The anecdote offers no demonstrated cross-team r
- 08-13 03:39alert_silentThe new testimonial modestly improves confidence that Parley is usable, but a single low-detail launch-thread comment is insufficient to establish reliable or auditable coordination and can wait for n
- 08-13 03:39alert_routeThe new testimonial modestly improves confidence that Parley is usable, but a single low-detail launch-thread comment is insufficient to establish reliable or auditable coordination and can wait for n
- 08-12 02:21sensor_dirtyengagement_update
- 08-12 01:01repriceAgent-exchange independently supports demand for terminal-agent messaging and coordination, moving the broader pattern beyond a single launch. It does not validate Parley’s implementation, cross-team
- 08-12 01:01alert_silentThe new project is useful category convergence but supplies no consequential evidence about Parley itself; substantive implementation details, independent usage, or reliability results can wait for th
- 08-12 01:01alert_routeThe new project is useful category convergence but supplies no consequential evidence about Parley itself; substantive implementation details, independent usage, or reliability results can wait for th
- 08-12 00:30alert_silentA second terminal-agent coordination project is relevant convergence, but the available evidence is only a Show HN title and repository link, with no implementation details, independent use, reliabili
- 08-12 00:30surface_candidateA second terminal-agent coordination project is relevant convergence, but the available evidence is only a Show HN title and repository link, with no implementation details, independent use, reliabili
- 08-12 00:30alert_routeA second terminal-agent coordination project is relevant convergence, but the available evidence is only a Show HN title and repository link, with no implementation details, independent use, reliabili
- 08-12 00:28attachIndependent corroboration of terminal-agent messaging and coordination directly bears on the open cross-agent handoff hypothesis.
- 08-12 00:28propose_attachIndependent corroboration of terminal-agent messaging and coordination directly bears on the open cross-agent handoff hypothesis.
- 08-11 23:55repriceThe small engagement increase adds no independent use, implementation evidence, or reliability results, so Parley remains an unvalidated launch claim rather than a demonstrated cross-team coordination
- 08-11 23:55alert_silentNo consequential new fact has emerged beyond minor engagement; independent usage or technical validation can wait for the next briefing.
- 08-11 23:55alert_routeNo consequential new fact has emerged beyond minor engagement; independent usage or technical validation can wait for the next briefing.
- 08-11 23:50alert_silentA creator-reported launch describes a relevant MCP coordination pattern—team-scoped identities, agent handoffs, file claims, audit logs, human approvals, and untrusted-message provenance—but provides
- 08-11 23:50surface_candidateA creator-reported launch describes a relevant MCP coordination pattern—team-scoped identities, agent handoffs, file claims, audit logs, human approvals, and untrusted-message provenance—but provides
- 08-11 23:50alert_routeA creator-reported launch describes a relevant MCP coordination pattern—team-scoped identities, agent handoffs, file claims, audit logs, human approvals, and untrusted-message provenance—but provides
- 08-11 23:38groundParley’s stated design converges with Scott’s model-to-model delegation, explicit handoff contracts, and auditable agent control-plane work, potentially providing an external comparison for Paperclip.
- 08-11 23:35createParley exposes a concrete MCP-based coordination mechanism with team-scoped identities and audit trails.