There's no off-the-shelf "Jira for AI" product out there right now tbh. Most sane teams are either hacking together thin SQLite + WebSockets dashboards, or just sucking it up and staring at raw stdout across 5 tmux panes. If you need a self-hosted setup with tracing, Langfuse should do the trick and cover like 90% of your pain points. Honestly, if you actually polish this control plane concept and open-source it, the demand will be massive
I'm building something that I called control plane for agents, but it's only solving half of the problem you're mentioning. Basically it allows me to connect to my agents remotely from anywhere, so I have one running on my server and several running on my home PC. I generally just use something like notion or beads for issue tracking.
Another thing I do is I have a custom Claude skill that runs every night and goes through all my repositories and Claude conversations and then updates my dashboard and tasks in notion with progress.
Works fine for a one-man pet project, but the second you hit a real codebase and dozens of commits a day, that nightly job is just gonna choke on the context window or slam into Anthropic's rate limits. You really need to be streaming agent state into a DB on the fly via WebSockets, not piecing it together once every 24 hours
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.
There's no off-the-shelf "Jira for AI" product out there right now tbh. Most sane teams are either hacking together thin SQLite + WebSockets dashboards, or just sucking it up and staring at raw stdout across 5 tmux panes. If you need a self-hosted setup with tracing, Langfuse should do the trick and cover like 90% of your pain points. Honestly, if you actually polish this control plane concept and open-source it, the demand will be massive
I'm building something that I called control plane for agents, but it's only solving half of the problem you're mentioning. Basically it allows me to connect to my agents remotely from anywhere, so I have one running on my server and several running on my home PC. I generally just use something like notion or beads for issue tracking.
Another thing I do is I have a custom Claude skill that runs every night and goes through all my repositories and Claude conversations and then updates my dashboard and tasks in notion with progress.
https://github.com/amurg-ai/amurg
Works fine for a one-man pet project, but the second you hit a real codebase and dozens of commits a day, that nightly job is just gonna choke on the context window or slam into Anthropic's rate limits. You really need to be streaming agent state into a DB on the fly via WebSockets, not piecing it together once every 24 hours
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