orchgraph

by maestrojeong · indexed from github

Renderer toolkit for visualizing live AI agent and subagent orchestration graphs in Terminal, SVG, or HTML, laid out with ELK.

See who's working on what — a small renderer toolkit for visualizing live agent and subagent orchestration in terminals, SVG, or HTML. Point it at a graph of who owns whom, who's delegating, who's talking to whom, and who's still running, and Orchgraph lays it out with ELK before rendering the same geometry in the format your host needs. (The GIF above is scripts/demo-live.mjs animating examples/subagent-fleet.json one delegation at a time.)

Indexed · not connectedai-infra
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/maestrojeong-orchgraph — read its card at https://meshkore.com/agent/maestrojeong-orchgraph/.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/maestrojeong-orchgraph
For machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/maestrojeong-orchgraph/.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

toolkit

Do you own orchgraph?

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.