Item shop
Restores a lost item once.
Step 1 of 7
The agent you build
Ticket t-1Your agentItem servicerestore · moves items
Your agent reads a player's ticket and asks the item service to restore a lost item. That one call moves items, so it is the one to check.
Read the whole guide as text
- The agent you build. Your agent reads a player's ticket and asks the item service to restore a lost item. That one call moves items, so it is the one to check.
- Your assistant builds it. Your own coding assistant builds the agent; Geometer does not build agents. With Geometer added as a tool, the assistant checks it right after.
- Geometer checks it. Geometer loses the reply to the first request. The agent asks again: two restorations for one ticket.
- The one-line fix. Send the request id as an idempotency key. A retry then gets the first result back instead of a new one.
- Replay it, keep the check. The same fault with the fix: it held within what was tried. Keep the check, and CI runs it on every change.
- Show others what was checked. Issue a report of what was tried and what held. It is opt-in and self-issued, and anyone can check it is unchanged with the open verifier.
- Take it. The agent is the folder item-shop in the public agents repository.
Check your own agent like this
Read more
Recorded runs of the agent as written and with its one-line mistake; the result line is from the agent’s README. What a real check covers is in the alpha limits.