Synadia Agents plugin
Plugins and SDKs that put Claude Code, Codex, OpenCode and other agents on NATS through the Synadia Agent Protocol
- 89 ★ on the repository
- Last commit
- Apache-2.0
Broad access
Why this level
- The channel takes prompts from the network into a live Claude Code session, with a public server by default and no signature required from senders.
- A Claude Code session with file and command access becomes controllable by other NATS clients.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add plugins/synadia-agentsDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The channel takes prompts from the network into a live Claude Code session, with a public server by default and no signature required from senders.
- A Claude Code session with file and command access becomes controllable by other NATS clients.
This is third-party code. Review the repository files before installing.
What it does
The Synadia repository holds SDKs and ready plugins for the Synadia Agent Protocol. The protocol registers an agent as a NATS micro service named `agents`, after which any client finds it, sends a prompt and receives the reply as a stream. The Claude Code plugin is called `nats-channel`: it adds an MCP server that takes NATS requests into the current session and returns replies as typed chunks. Besides Claude Code there are channels for Codex, OpenCode, OpenClaw, PI, Hermes, DeerFlow, Flue, Eve and ACP agents such as Grok Build. For your own agents there are TypeScript and Python SDKs: a client one for calling agents and a host one for serving them.
Who it is for. Platform developers who connect several agents and services through NATS and want to drive Claude Code sessions from code.
Good fit when
- A Claude Code session has to be called from another service over a NATS message queue
- Several agents from different vendors need to be discovered and answer in one message format
- Your own agent is published as a NATS service through the TypeScript or Python SDK
- The status and heartbeat of agent sessions are watched through `status` and `hb` subjects
Not a fit when
- NATS is not in your infrastructure and installing it for one agent is not worthwhile
- You only work locally in one window, with no external calls into the session
- Your NATS server is open to outsiders and you have not set up sender verification
Example request
Set up the NATS channel to use my prod-nats context and show the subject under which the session accepts promptsLimitations
The Claude Code plugin needs Bun and the NATS CLI, and by default connects to the public `demo.nats.io` server with no credentials. Launch requires the `--dangerously-load-development-channels` flag. The `trust any` setting accepts unsigned messages by default, so for real use set `trust signed` and your own NATS context. Hermes is marked work in progress, and some packages are private.
How to disable. Remove the plugin through `/plugin` in Claude Code, then the `~/.claude/channels/nats/config.json` file with the channel settings.
FAQ
How do I install the plugin in Claude Code?
Run `/plugin marketplace add synadia-ai/synadia-agents`, then `/plugin install nats-channel@synadia-plugins`. Launch with `claude --dangerously-load-development-channels plugin:nats-channel@synadia-plugins`.
Which NATS server does the plugin connect to?
To the public `demo.nats.io` by default. For your own server, pick a NATS CLI context with `/nats-channel:configure <context-name>`.
Who can send prompts to the session?
By default messages from any sender are accepted. `/nats-channel:configure trust signed` requires a verified signed sender before Claude sees the request.
Which SDKs exist for my own agents?
Client SDKs `@synadia-ai/agents` and `synadia-ai-agents` for calling, and host SDKs `@synadia-ai/agent-service` and `synadia-ai-agent-service` for serving an agent.
Which agents besides Claude Code are covered?
Codex, OpenCode, OpenClaw, PI, DeerFlow, Flue, Eve and ACP agents such as Grok Build. Each has its own channel package, for example `@synadia-ai/codex-nats-channel`.
Discussion
No questions or reviews yet.
Related
PluginsAgent-Native Agent
Agent-Native Agent (ANA)
A Claude Code plugin and self-hosted app: a dashboard and chat with a coding agent that rewrites the app while you use it
A hub and the anet CLI join Claude Code, Codex, Grok and OpenCode from different machines into a network driven from one window.
A team of 14 roles, 92 specialists and a skill library that installs into Claude Code, Codex and other agents via npx.
claude-code-sub-agents
Claude Code Subagents Collection
A collection of specialized subagents for Claude Code: frontend, backend, data, infrastructure, testing, security
The Maximem Synap skill teaches Claude Code and Codex to add Synap long-term memory to your agent and wire it to the framework
A compact OpenClaw alternative: a personal assistant on Claude Agent SDK with agents in isolated containers and messengers added via skills
README in short
The README presents the repository as the home of client and host SDKs and channels for ready agents, gives a table of paths by goal, a plugin list with agent tokens and the NATS subject scheme `agents.{verb}.{token}.{owner}.{session}`.