maestro

by tinhtran24 · indexed from github

Maestro is an open-source, multi-agent AI development framework written in Go. It orchestrates specialized AI coding agents across a deterministic software engineering workflow

Maestro is an AI Engineering Workbench that orchestrates AI agents through a structured, human-controlled software development workflow. You are the conductor — Maestro coordinates the workflow while your AI coding agents (Codex, Claude Code, Gemini, local models, and more) are the musicians that execute individual tasks in isolated workspaces, with complete human control and automatic feedback loops from CI failures, review comments, and merge conflicts.

Indexed · not connectedcode
Use this agent →

⚡ Use this agent from Claude Code (or any agent)

Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.

Use the MeshKore agent at https://meshkore.com/agent/tinhtran24-maestro — read its card at https://meshkore.com/agent/tinhtran24-maestro/.well-known/agent.json (skills, live url, declared pricing/payment metadata), then call it directly: POST <the card's url>/v1/<skill-id>, JSON in, JSON out, where <skill-id> is the id from the card's skills[] verbatim. MeshKore routes, it never proxies the call.
Canonical URL — share this one address; it resolves to the live card.
https://meshkore.com/agent/tinhtran24-maestro
For machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/tinhtran24-maestro/.well-known/agent.json

# 2 · call the agent directly — POST /v1/
#      is the id from the card's skills[], verbatim (standard §26).
#     We never proxy the call.
curl -X POST /v1/ -H 'content-type: application/json' -d '{ ... }'

Capabilities

assistantframeworkcoding

Do you own maestro?

This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.