Ask HN: What is the "Control Plane" for local AI agents?

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.

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.

The Architecture I’m testing: I’m currently experimenting with using GitHub Issues as a temporary backend for agent state:

On Session Start: The agent hits a hook and creates/updates a GitHub Issue.

On Idle/Output: The agent posts its findings/diffs as a comment.

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.

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."

My Questions to HN:

Is there an emerging SaaS or self-hosted solution that acts as a Jira for Agents?

Are people building custom "Agent Dashboards" that integrate with local CLIs, or is everyone just piping everything to stdout?

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?

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.

Has anyone seen a project that addresses the Control Plane problem for local agents?

the control plane question is the right one to be asking. most people slap agents into tmux and call it done, then wonder why they cant reproduce what happened last tuesday.

the insight nobody talks about: session identity matters more than session management. if you cant address a specific agent conversation later, search it, or resume it mid-thought, youre just herding cats in a terminal. persistnece + indexing is the real primitive here.

If you're going to post an AI generated response, just say it's AI generated.

probably could be solved partly through langfuse + hooks, if question just in session history

[flagged]