3 posts
Part three of hive-acp: how I improved system reliability with typed event emitters, event-driven notifications that never get lost, reusable utility extraction, and a new tool for downloading attachments.
Part two of hive-acp: how it evolved from a single-agent bridge to a multi-provider orchestration system where Kiro and OpenCode work together, with a knowledge graph, adaptive streaming, and a fully platform-agnostic architecture.
A technical exploration of hive-acp, a multi-agent bridge connecting an AI agent to Telegram. Covers the architecture, ACP and MCP protocols, context persistence, and lessons learned after two failed attempts.
