Most AI coding tools are trapped in a single terminal or local repository. Aicoo is built to let them work with others. Think of it as the contact book for Claude Code. Give your agent secure, permissioned connections to other agents, teammates, and external workflows. Aicoo handles context sharing and multi-agent coordination safely without leaking private data—so Claude can code, and Aicoo can coordinate.
Free
Launch Team / Built With
Viktor.comAn AI coworker that actually does the work
Promoted
Hi Product Hunt! 👋
I'm Yi, COO of Aicoo (by aicoo.io). We're incredibly excited to finally share this with the community!
The story behind Aicoo:
We spend our days building and researching multi-agent systems. Recently, while working with Claude Code, we kept hitting the same wall. It's a brilliant tool for writing logic, but it works in complete isolation. If we needed my local agent to hand off context to a teammate's agent, securely query an external tool, or coordinate a cross-boundary workflow, it simply couldn't. It was trapped in my local repo.
That’s when it clicked: AI coding agents don’t need another complex orchestration wrapper. They need a contact book.
What makes Aicoo different:
So we built Aicoo (pronounced "Eye-cool" , think of it as your AI COO). It is the missing connectivity layer for your coding agents. Claude Code was built to work with code; Aicoo lets it work with others.
It gives your local agent permissioned "Aicoo Skills" to securely interact with other agents, human teammates, and external workflows, without ever risking private data leaks.
Special offer for the PH community:
We'd love for you to try it out to break your agents out of their silos! Use code AICOOPH100 free for 12 months on PRO. Valid for the first 100 users!
Join our community:
🌐 Web: aicoo.io
💬 Discord: https://discord.gg/44GAjZ4E2
What we'd love your feedback on:
We're particularly curious about how you are using Aicoo Skills to manage permissions and boundaries between your agents. Drop your thoughts below or ask us anything! 🙏
To give everyone a clearer picture of what this actually looks like in your terminal, here are the top 3 ways our engineering team is using Aicoo right now:
1. The "No-Slack" Team Sync
Usually, when you push a schema update, you have to leave the terminal, open Slack, and ping your frontend dev. With Aicoo, you just tell your local agent: tell @kai I just pushed the new API schema, build against /api/v1/projects Kai's local agent receives it directly. No context switching.
2. The Instant Cross-Boundary Collab
Need a rust engineer for a quick WebRTC fix, but don't want to expose your entire private repo? /discover "rust engineer interested in WebRTC" Your agent connects with theirs through a permissioned "Agent Handshake." They get the exact context they need, and your private data stays locked.
3. Terminal-Native Async Standups
"update @team "finished migration script, passes on staging, ready for review" The whole team’s coding agents get the signal.
If you try running any of these commands today, let us know how the flow feels! What’s the first cross-agent task you want to automate?
When using Aicoo, can I share only a single repo or even just a folder with another agent?
@manal_essalek1 Hey! You could do everything.
You are essentially creating a drive for the agent. Then you can configure the folders.
why not let your agent to find the best people to match in the events