/restaurant-finder
Agent 36: Restaurant Finder (the user's personal life)
Supplies three real, cited restaurant options plus a reliable fallback for a cuisine, occasion, and party size, at the chosen budget tier. Discovery only — owns no reservation; /restaurant-booking books the chosen table.
verified (fixture) 2026-09-08v0.1.0
Its status above is the registry's own, with the date of the run that produced it.
What it is for
Contract A
- #36 — Restaurant finder · five budget tiers
Example requests
- “find us a restaurant”
- “where should we eat Friday”
- “somewhere for a birthday dinner”
- “Italian near downtown”
- “restaurant finder”
What it needs, and what it hands back
Needs connected
- websearch
- webfetch
Uses WebSearch, WebFetch, which exist in Claude Code. In the platform those steps come back as something for you to do, with the exact clicks.
Hands back
- the option table, returned inline when orchestrated
- clients/_me/plans/restaurants/<date>.md (standalone runs only)
Stops and asks
Nothing this agent does is irreversible on its own, so it asks for no approval of its own. Spending, sending and publishing are approved wherever they happen.
Steps it cannot do through an API, and hands you instead: any reservation — /restaurant-booking (#18) owns it.
How it runs
These are the headings of its own written instructions — 173 lines you can read and change.
- Step 0 — Environment and profile
- Step 1 — Find restaurants that fit
- Step 2 — Deliver