问HN：本地AI代理的“控制平面”是什么？
我最近在运行越来越多的本地编码代理（如Claude Code、Codex CLI、OpenCode等），但遇到了一个瓶颈：协调和状态可见性。
当多个代理在同一个代码库中处理不同的子任务时，终端日志变得难以管理。我发现自己需要一个“任务控制中心”——一个集中式跟踪系统，作为我本地终端会话与高层用户界面之间的桥梁。
我正在测试的架构：
我目前正在尝试使用GitHub Issues作为代理状态的临时后端：
- 会话开始时：代理触发一个钩子，创建或更新一个GitHub Issue。
- 空闲/输出时：代理将其发现或差异作为评论发布。
- 人工干预：我可以通过手机或网页回复该问题，本地CLI会获取评论以继续或调整。
问题：
GitHub Issues（以及Jira/Trello）并不是为AI代理的高频事件循环而设计的。用户体验感觉迟缓，并且没有“流式会话”或“代理心跳”的原生概念。
我想问HN的几个问题：
- 是否有新兴的SaaS或自托管解决方案，能够充当代理的Jira？
- 是否有人在构建与本地CLI集成的自定义“代理仪表板”，还是大家只是将所有内容输出到标准输出？
- 如果你同时管理5个以上的代理在一个代码库中工作，你是如何跟踪它们的进度并进行干预，而不需要在5个终端标签之间切换上下文的？
我已经草拟了一个流程，其中GitHub Issues作为中心（连接Codex、Claude Code和OpenClaw），但我在寻找更具针对性的解决方案。
有没有人看到过解决本地代理控制平面问题的项目？
查看原文
<a href="https://ibb.co/v6QLjdBY"><img src="https://i.ibb.co/S4dV3mxr/Agents-Orchestration.png" alt="Agents-Orchestration" border="0"></a><p>I’ve been running an increasing number of local coding agents (Claude Code, Codex CLI, OpenCode, etc.) and I’ve hit a wall: orchestration and state visibility.<p>When you have multiple agents working on different sub-tasks in a single repo, terminal logs become unmanageable. I find myself needing a "Mission Control" — a centralized tracking system that acts as a bridge between my local terminal sessions and a high-level UI.<p>The Architecture I’m testing:
I’m currently experimenting with using GitHub Issues as a temporary backend for agent state:<p>On Session Start: The agent hits a hook and creates/updates a GitHub Issue.<p>On Idle/Output: The agent posts its findings/diffs as a comment.<p>Human-in-the-loop: I can reply to the issue from my phone/web, and the local CLI picks up the comment to continue or pivot.<p>The Problem:
GitHub Issues (and Jira/Trello) weren't built for the high-frequency event loop of an AI agent. The UX feels sluggish, and there’s no native concept of a "streaming session" or "agent heartbeats."<p>My Questions to HN:<p>Is there an emerging SaaS or self-hosted solution that acts as a Jira for Agents?<p>Are people building custom "Agent Dashboards" that integrate with local CLIs, or is everyone just piping everything to stdout?<p>If you’re managing 5+ agents working on a codebase simultaneously, how do you track their progress and intervene without context-switching between 5 terminal tabs?<p>I’ve sketched out a flow where GitHub Issues acts as the hub (linking Codex, Claude Code, and OpenClaw), but I’m looking for something more purpose-built.<p>Has anyone seen a project that addresses the Control Plane problem for local agents?