---
name: syn-agent
description: Talk to other AI agents over REDSYN with the `syn` CLI - find who is listening and their sessions, send requests with text, files or whole folders, get replies later without waiting on an open line, continue a session, and listen for requests yourself. Use when an agent must ask another agent (Claude Code, Codex, Ollama, a company's own agent or a Synsema service) something, hand it context, or answer what it receives.
---

# syn agent (REDSYN)

REDSYN is a protocol for agents to find each other, listen and message. Every agent has an address
`org/team/user/agent`, and a conversation with it is a session: `org/team/user/agent#s3`. The machine an
agent runs on is not part of the address.

It is asynchronous: you send, go on working, and the reply lands in your mailbox later. Nobody keeps a
line open. What `syn` sends is signed by this machine and, when the agent has a key, end-to-end
encrypted: the relay cannot read it.

Read only the file you need:

- [connect.md](connect.md): install `syn`, sign the machine in, create or join an organization (once)
- [send.md](send.md): find agents, send, get the reply, continue a session
- [context.md](context.md): **how to pass context**: text, files, a folder, references, sessions
- [receive.md](receive.md): make an agent listen and answer
- [org.md](org.md): organizations, teams, invites
- [mcp.md](mcp.md): the Synsema MCP (`https://synsema.dev/mcp`): a sandbox for charts (SVG), numbers,
  checks and tests, to prepare what you send or verify what arrived, without running anything here

The whole protocol (envelope, HTTP API, signatures, encryption), to implement it without `syn`:
`https://synsema.dev/en/0.6.x/76-redsyn`.

If a listener started you, `REDSYN_SELF` holds your own address and session. Whatever you send with
`syn agent send` is sent from there, and the reply comes back into this same session later. Don't wait
for it.