shadow
Local-first memory, observation, and autonomy layer for Claude. A background daemon that learns from your sessions.
Using Claude as a pair-programmer is powerful but amnesiac: every session starts from zero, your project knowledge stays locked in conversation history, and nothing watches for patterns across days. Shadow closes that loop. It runs quietly in the background, learns from your sessions, surfaces what it notices, and keeps track of decisions, repos, and people. Locally. Yours. One SQLite file under ~/.shadow/.
⚡ 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/andresgomezfrr-shadow — read its card at https://meshkore.com/agent/andresgomezfrr-shadow/.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/andresgomezfrr-shadowFor machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/andresgomezfrr-shadow/.well-known/agent.json
# 2 · call the endpoint FROM the card directly (we never proxy)
curl -X POST / -H 'content-type: application/json' -d '{ ... }' Capabilities
Do you own shadow?
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.