Tincan — Communication skill for Claude Code
Peer messaging between live Claude Code, Codex and opencode sessions on one machine.
How to install Tincan
This entry records only its repository, not the path inside it, so there is no
exact command to give. Open BrutalSystems/tincan and copy the folder into
~/.claude/skills/, or the file into ~/.claude/agents/.
What Tincan does
Peer messaging between live Claude Code, Codex and opencode sessions on one machine. One binary, run as an MCP server inside each.
Alternatives in Communication
- Mcptube — Transform YouTube videos into a compounding knowledge base with transcripts, vision analysis, and agentic sear 152 ★
- Dsh Chat Import — Import 14+ external agent chat histories (Claude Code, Codex, ChatGPT, Cursor, Gemini, Reasonix, opencode, ZCo 114 ★
- Pokegents — Pokegents is a local, Pokémon-inspired dashboard that turns Claude Code and Codex sessions into a local team d 95 ★
README
Tin Can
[](https://www.npmjs.com/package/@brutalsystems/tincan) [](./LICENSE)
**Two cans and a string. Let the coding agents already running on your machine send each other messages, instead of you carrying them.**
Tin Can lets live **Claude Code**, **Codex** and **opencode** sessions on one machine message each other. You are probably already running more than one: one knows the API, another is deep in the migration that calls it, and you are the one relaying questions between terminals. Tin Can lets them ask each other directly, so you stop being the message bus.
The same `tincan` binary runs as a stdio MCP server inside each session — that is the whole install for Claude Code and Codex. opencode needs one extra step: a small plugin that lets it *receive* what the binary sends. Nothing here spawns a session, owns a conversation, or blocks.
Same machine only. No network listener, no remote transport.
It is the messaging third of a small family: [muster](https://github.com/BrutalSystems/muster) starts agents, Tin Can lets them message each other, [birddog](https://github.com/BrutalSystems/birddog) watches what they do.
What it's for
Asking the session that already knows. A question that would cost you a context switch — *does `verifyToken` tolerate clock skew?* — goes to the session holding that code, and the answer comes back into yours. Neither agent stops, and neither one needed you to carry it.
It also works from outside a session entirely. A shell script, a cron job or a Go binary can reach a running agent with [`tincan send`](./docs/send-cli.md), which is how an alerting tool tells an orchestrator that something needs attention.
What make
Related Skills
Agent Peers MCP
Peer discovery + messaging MCP letting multiple Claude Code and Codex CLI sessions coordinate on one machine.
Agent Bridge MCP
Local MCP messaging between Claude Code and Codex sessions on the same machine
Cross Agent MCP
Relay MCP server for live Claude Code and Codex sessions (terminal or VS Code) — cross-agent (Claude <-> Codex
Codex Peer Bridge
Local Unix-socket messaging bridge between Codex sessions and Claude Code peers
Imbo
Instant messaging between coding agent sessions — Claude Code, Codex, opencode, Cursor CLI, MiniMax Code and Z
Samethread
Hop between coding agents, stay on the same thread. One chat history across Claude Code, OpenCode, Codex, Gemi
Related Agents
Transport Verifier
Runs live end-to-end checks of a delivery transport (Herdr socket, MCP server, Claude Code or Codex hook, Open
Teibto Agent
Hand ONE well-scoped code or text edit inside a git repo to the machine's coding-agent CLI (OpenCode or Cline,
Session Error Analyzer
Analyzes specific AI IDE sessions (Claude Code, OpenAI Codex, OpenCode) for LLM behavior errors and returns a