Fakih

I was tired of copy-pasting context between Claude Code and other CLIs

by
I’ve been using Claude Code as my main terminal driver for a while, but it has a huge blind spot: it operates completely in isolation. Whenever I needed Gemini to do deep repo research, or Cursor to handle UI work simultaneously, Claude had no idea what they were doing. I was stuck playing the middleman, copy-pasting output from one terminal into the other. So I built Neohive. It’s an open-source MCP server that gives Claude Code a shared local directory to communicate with your other agents. How it actually works: * You run `npx neohive init` in your project. * Claude Code and your other CLIs read/write to a shared `.neohive/` folder on your drive. * Claude can now autonomously ping Gemini, assign tasks, or ask for code reviews without you copying text. Everything is local. No cloud, no database, just the filesystem acting as a message bus. Repo is here if you want to test it out: https://github.com/fakiho/neohive If anyone else is running Claude Code alongside other local models, I'd love to know how you handle keeping their context synced.
8 views

Add a comment

Replies

Best
Alex Rotar
This is a brilliantly simple solution to a massive headache. Using the local filesystem as a message bus for MCP instead of over-engineering a cloud sync is exactly the kind of pragmatic dev tooling I love. The isolation of these CLI agents is definitely their biggest blind spot right now. Have you noticed any file-locking issues or race conditions when multiple agents try to read/write to .neohive/ simultaneously?