Building a coordination layer for Claude/AI agent teams — would love feedback

Reddit r/AI_Agents Tools

Summary

The author introduces AgentsHive, a coordination layer for managing teams of AI agents across tools and models, and asks for feedback from Claude users on workflow pain points and human-in-the-loop requirements.

Disclosure: I’m affiliated with AgentsHive. I’m working on AgentsHive, a coordination layer for running a team of AI agents across tools, machines, and model providers. The idea is to move beyond single chat threads: agents can remember project context, debate tradeoffs, produce reviewable artifacts, and surface decisions for human approval. I attached a couple product screenshots from the landing page so people can judge the workflow instead of just reading a pitch. I’m especially interested in feedback from people using Claude or Claude Code for real work: \- Where does your current agent workflow break down? \- What would make you trust an always-on agent team? \- What decisions should always stay human-in-the-loop? \- Would reviewable artifacts/approval queues be useful, or is chat enough? Happy to take blunt feedback. I’m trying to understand what Anthropic/Claude users actually need here, not just pitch into the void.
Original Article

Similar Articles

AI agents still suck, so I built my own

Reddit r/AI_Agents

The author built a custom AI agent application wrapping Claude Code and upcoming Codex support, focusing on composable workflows and seeking community feedback.

How are you handling cross-client communication between MCP agents?

Reddit r/AI_Agents

A developer discusses the challenge of coordinating multiple MCP-speaking AI agents (like Claude Code and Cursor) working on the same project, sharing their self-built open-source solution using a shared 'room' model inspired by IRC, and asking the community for patterns and opinions.