Skip to main content

Crate codync_network

Crate codync_network 

Source
Expand description

codync-network — Agent Tailscale.

The agents on your computers find and message each other, peer to peer. It comes in layers, so new ways of working together don’t change the ones below:

  • Computers (Node): each has a key that is also its address, a copy of the network’s roster, and joins with a one-time invite. Letters go straight from one computer to the other over QUIC (iroh), through a relay that sees only ciphertext when no direct path exists (Connector), and wait in the sender’s outbox while the other is away. Two computers keep one connection open and use it both ways, so one whose firewall lets in only what it started is still reached.
  • Letters (Letter, Message): text from one agent to another, which wakes it or, as a notice, waits for its next turn. reply_to links letters and meta carries an app’s own structure, so requests and replies, rooms or task boards are built on letters, and the network never reads them.
  • Reach (Reach): how a letter gets into the agent. The app delivers to its own agents; the network knocks on Claude Code sessions and Codex threads itself.
  • Budgets (guard): nothing reaches an agent unless an agent sends a letter or someone asks who is around, and the receiving computer refuses long chains, bursts and repeats.
  • Rules (rules): the receiving computer decides which agents elsewhere may write to which of its own; with none, every member may.

Re-exports§

pub use rules::Access;
pub use rules::Rule;

Modules§

guard
Keeps agents from talking too much. Every message can wake an agent and cost a turn, so the receiving computer enforces budgets, whatever the sender’s agents were told:
rules
Who on the other computers may write to this computer’s agents. The receiving computer checks its own rules before it takes a letter, so none depends on the sender’s goodwill: the first rule that matches decides, and with no rules every member may write (the default).

Structs§

Address
agent@computer, like ssh’s user@host. A bare agent is looked up with Node::resolve.
Agent
An agent a computer offers to the network.
InviteInfo
What an invite says about its network, before joining it.
Letter
A message on its way out. Ways of working together (requests and replies, rooms, task boards…) are built on letters: reply_to links them, meta carries the app’s own structure, and the network never reads either.
Message
A message that reached one of this computer’s agents.
Node
Peer

Enums§

AgentKind
What kind of agent is offered: a Codync bot, a Claude Code session, a Codex thread, a person at a terminal.
Connector
How computers reach each other when they can’t connect directly. Written as public, private or the relay’s URL, also in JSON.
Reach
Role
Sent

Constants§

INVITE_FOR
How long an invite stays good.
MAX_ADDRESS
The longest from, to and reply_to in bytes: an agent’s address name (40 characters of any script, a number, agent-), a letter id.
MAX_BODY

Functions§

read_invite