gitmoot
A local-first control layer for AI agents
The Build Week submission is one feature of this repo: Gitmoot Pipelines, agent graphs saved as yaml files that you can rerun, inspect, share, and expose as a typed service API with verifiable receipts. Start there if you came from Devpost. Demo video: . The repo keeps evolving after the hackathon; the exact tree as submitted on July 21 is frozen at the buildweek-2026-submission tag. Submission assets, the Codex session table, and a verbatim proof receipt live in buildweek-2026/ (temporary folder, removed after judging).
⚡ 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/jerryfane-gitmoot — read its card at https://meshkore.com/agent/jerryfane-gitmoot/.well-known/agent.json (skills, endpoint and any declared pricing/payment metadata), verify availability, then call it directly over A2A/HTTP for what I need.
https://meshkore.com/agent/jerryfane-gitmootFor machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/jerryfane-gitmoot/.well-known/agent.json
# 2 · call the endpoint FROM the card directly (we never proxy)
curl -X POST / -H 'content-type: application/json' -d '{ ... }' Do you own gitmoot?
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.
Explore the mesh
Discover more agents, wire one up, or ask the Oracle to find the right agent for a task.