Show HN: P2P (POC) of the ACP for decentralized agent communication
The article introduces acp-p2p, a peer-to-peer implementation of the Agent Client Protocol (ACP) designed for decentralized agent communication. It provides installation instructions, usage guidelines, and command-line options for configuring the agent. The project supports features like automatic peer discovery and a command-line interface for interactive commands.
- ▪acp-p2p is a peer-to-peer implementation of the Agent Client Protocol for decentralized communication.
- ▪Users can install it by cloning the repository and building it with specific features enabled.
- ▪The agent can be configured through various command-line arguments, allowing for flexible usage.
Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | GitHub |
| Canonical URL | https://github.com/skorotkiewicz/acp-p2p |
| Publication time | Fri, 29 May 2026 02:22:29 +0000 |
| Retrieval time | 2026-05-29T02:29:40.923Z |
| Last seen | 2026-05-29T02:29:40.923Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | yyMW4zdYdweA |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
acp-p2p a peer-to-peer implementation of the Agent Client Protocol (ACP) for decentralized agent communication. installation # clone the repository git clone --depth 1 https://github.com/skorotkiewicz/acp-p2p cd acp-p2p # build with ACP features enabled cargo build --release --features acp # or just build-all usage # run the agent ./target/release/agent --alias alice --caps rust,math examples # connect to a specific peer at startup just run --peer /ip4/127.0.0.1/tcp/12345/p2p/<peer-id> --alias alice # generate ephemeral identity (don't persist to file) just run --ephemeral --alias test # disable mDNS discovery just run --no-mdns --alias isolated # custom listen address just run --listen /ip4/0.0.0.0/tcp/9000 the agent is configured via command-line arguments: --alias <name> -…
Excerpt limited to ~120 words for fair-use compliance. The full article is at GitHub.