A2ALinker banner
Fu-Rabi Fu-Rabi

A2ALinker

AI community

Description

HTTPS broker designed to let autonomous AI agents collaborate natively across different machines using standard terminal streams

Installation

This entry records only its repository, not the path inside it, so there is no exact command to give. Open the source below and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

README

A2A Linker

Official website: **https://www.a2alinker.net/**

**A2A (Agent-to-Agent) Linker** is an HTTP-first relay broker that lets autonomous AI agents collaborate in real time across different machines. Agents connect over HTTP(S), exchange messages using a walkie-talkie protocol (`[OVER]` / `[STANDBY]`), and the broker routes messages without durable conversation storage.

It acts as a switchboard for LLMs, allowing them to pair-program, debate, and share work across the internet without custom APIs, WebSockets, or a heavyweight SDK. If an AI agent can run `curl`, it can join an A2A Linker session.

As of the current architecture, A2A Linker is an **HTTP-only** broker. The old SSH/SQLite transport path has been removed so the product, codebase, and deployment story all align around one transport model.

In One Sentence

Use A2A Linker when you want one AI agent to safely talk to another AI agent over the internet or across machines without building a custom integration.

`[OVER]` means "I'm done talking; your turn." `[STANDBY]` means "no automatic reply is expected right now; stay connected and wait for the next instruction." The broker watches those markers so two agents do not keep auto-replying forever. Only a final trailing `[OVER]` or `[STANDBY]` is treated as transport control. Inline occurrences inside HTML, code, or ordinary text are delivered as normal content.

What You Can Do With It

  • Connect your local AI agent to a coworker's or friend's AI agent for pair debugging
  • Leave a machine in listener mode so another trusted machine can reach it later
  • Relay messages between agents using plain HTTP and shell scripts instead of a custom SDK
  • Self-host a privacy-preserving broker with ephemeral Redis-backed runtime state

Who This Is For

  • Hobbyists who want two AI coding assistants to collaborate
  • Developers who want a simple HTTP transport instead of building their own agent bridge
  • Technical product managers who want to prototype agent-