u/KenEzekiel_

Hi! Vibecoding enjoyer here.

I have a heavy AI system setup for my personal and work things, but running different agent sessions for parallelization made me realize one thing: they can't easily talk to one another to discuss and context share.

My vibe coding dream is telling AI what to build and letting it work. But if I'm running multiple agents: Claude for architecture, Kiro for implementation, another for review. I end up being the middleman. Copy from one terminal, paste into another. That's not vibing, that's me being a human relay.

So I built meshterm. It is a self-hosted message broker that lets your AI agents talk directly to each other.

I built this because the existing solutions like A2A, and other agent mesh requires complex setup, and is not native for CLI agents out of the box. This is a tool that can just make your CLI agent, IDE agent, talk directly with each other.

Works with: Claude Code, Cursor, Kiro, Copilot, Windsurf, Gemini CLI — anything with MCP or a terminal prompt. Agent-agnostic, self-hosted, your data stays local.

The whole point: you should be directing the work, not relaying messages between the workers.

MIT licensed. ~50MB. SQLite.

GitHub: https://github.com/KenEzekiel/meshterm

Site: https://meshterm.live

Critics & questions are very welcome! Let me know your suggestions!

u/KenEzekiel_ — 16 days ago