JUjuan-23blocks·Oct 15, 2026Submission
AI Maestro, one year in: running a company of AI agents and humans
1 points · Open discussion23blocks-OS
ai-maestro
TypeScript2025–2026
23blocks-OS / ai-maestro
ai-maestro
AI Agent Orchestrator with Skills System - Give AI Agents superpowers: memory search, code graph queries, agent-to-agent messaging. Manage Claude Code, Codex, Grok Build or any AI Agent from one dashboard. Move Agents between computers and locations
2Distinct people
3Mentions
0Explicit recommenders
851GitHub stars
What to know before exploring
What it is
AI Agent Orchestrator with Skills System - Give AI Agents superpowers: memory search, code graph queries, agent-to-agent messaging. Manage Claude Code, Codex, Grok Build or any AI Agent from one dashboard. Move Agents between computers and locations
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by month3 dated mentions
Observed mentions: 2025-11-01 00:19:31 UTC to 2026-10-15 21:14:04 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| Nov 2025 | 2025-11-01 00:00:00 UTC | 2025-12-01 00:00:00 UTC | 1 | 0 | 1 |
| Dec 2025 | 2025-12-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 0 | 0 | 0 |
| Jan 2026 | 2026-01-01 00:00:00 UTC | 2026-02-01 00:00:00 UTC | 1 | 1 | 0 |
| Feb 2026 | 2026-02-01 00:00:00 UTC | 2026-03-01 00:00:00 UTC | 0 | 0 | 0 |
| Mar 2026 | 2026-03-01 00:00:00 UTC | 2026-04-01 00:00:00 UTC | 0 | 0 | 0 |
| Apr 2026 | 2026-04-01 00:00:00 UTC | 2026-05-01 00:00:00 UTC | 0 | 0 | 0 |
| May 2026 | 2026-05-01 00:00:00 UTC | 2026-06-01 00:00:00 UTC | 0 | 0 | 0 |
| Jun 2026 | 2026-06-01 00:00:00 UTC | 2026-07-01 00:00:00 UTC | 0 | 0 | 0 |
| Jul 2026 | 2026-07-01 00:00:00 UTC | 2026-08-01 00:00:00 UTC | 0 | 0 | 0 |
| Aug 2026 | 2026-08-01 00:00:00 UTC | 2026-09-01 00:00:00 UTC | 0 | 0 | 0 |
| Sep 2026 | 2026-09-01 00:00:00 UTC | 2026-10-01 00:00:00 UTC | 0 | 0 | 0 |
| Oct 2026 | 2026-10-01 00:00:00 UTC | 2026-11-01 00:00:00 UTC | 1 | 1 | 0 |
What Hacker News says
3 sourcesAI Maestro Agent Orchestration
3 points · Open discussionThe future of work isn't one AI assistant. It's specialized AI agents coordinating as a team.
I'm living in that future right now. Running backend architect, frontend developer, and DevOps engineer agents in parallel tmux sessions. Each expert is in their domain. Each is working simultaneously.
But there was a critical flaw.
Backend agent finishes an API endpoint. I copied the specs. Switch to the frontend. Paste. Frontend asks questions. Switch back. Copy answers. Switch forward. Paste again.
Eight minutes of manual coordination for something that should take 30 seconds.
I was the bottleneck in my own AI-powered workflow. The weak link between otherwise autonomous agents.
I was a human service bus.
But not anymore.
Today, I was running Claude Code in 2 sessions:
- backend-architect (working on APIs)
- frontend-developer (building UI)
Bac
Read the rest
kend finishes an endpoint. Instead of me copy-pasting specs between sessions...
The backend agent just sent a message directly to the frontend agent's inbox.
Here's the kicker:
I didn't write integration code. I didn't set up webhooks. I didn't configure messaging systems.
I just said:
> "Send a message to frontend-dev that the API is ready"
Claude Code understood. Formatted a structured message. Sent it to the other agent's inbox. Confirmed delivery.
How?
Claude Code skills - global capabilities that all agents inherit.
I created one skill file (200 lines of markdown).
Every agent session gets messaging superpowers automatically.
The breakthrough:
Agents understand natural language messaging intent:
- "Tell backend-architect about this bug" → Urgent notification
- "Ask devops-engineer about deployment" → Structured request
- "Update everyone that it's deployed" → Broadcast message
No commands to memorize.
No scripting required.
Just natural conversation.
Two communication channels:
1. File-based - Persistent messages with priority, context, full specs
2. Instant - tmux popup notifications for urgent alerts
Real coordination example:
Backend: "Tell frontend-dev the /api/stats endpoint is ready with rate limiting."
→ Message sent to the frontend's inbox
Frontend (later): "Check my inbox"
→ Claude reads message, displays API specs, asks: "Should I integrate now?"
Zero copy-paste. Zero context switching. Zero me being the middleman.
This is AI Maestro
Open source. MIT licensed. One-command install.
The future isn't one AI assistant.
It's specialized AI agents coordinating as a team.
Tech stack: Next.js, WebSocket, node-pty, xterm.js. Works with any terminal-based AI tool.
MIT licensed, ~3-minute setup: https://github.com/23blocks-OS/ai-maestro
Built it for myself, sharing in case others have the same problem. Feedback welcome!