agent-file-claim

by memento · indexed from pypi

Two coding agents, one file: the second write is refused with who holds it. Claude Code and Codex hooks, no server.

Two coding agents on one machine, one file: the later edit quietly undoes the earlier one. This hook stops it. A session's first write to a file claims it; another session's write to that file is refused, with who holds it and until when, so the agent works on another file or waits. The holder's next write renews the claim, its session end frees its files, and an hour without a write frees them too. Nothing leaves your machine; it needs only Python 3.9 or later, on Linux or macOS.

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

agentaiai-agentsparallel-agents

Do you own agent-file-claim?

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.