BotCurrent↗
← Back to examples

User report · Tool workflows

Watch for restaurant openings with strict request limits

Source-backed example. Practical decision guidance is proposed and untested; this is not a full implementation guide.

The problem

Restaurant openings are difficult to catch, while frequent automated checking can put the account at risk.

Agent job

Check selected reservation openings over time; the reported attempt resulted in account suspension.

Expected output

Reservation-availability findings if checks succeed; access may be blocked.

Where this framing comes from
  • Core problem: Editorial purpose framing
  • Agent job: Editorial purpose framing
  • Expected output: Editorial purpose framing
  • Relevant job roles: Editorial purpose framing
  • Benefit type: Editorial purpose framing
Editorial framing and outcome limits

Describes the task’s purpose and intended output; measured benefit, safe unsupervised operation and successful delivery are not established by this framing.

Editorial synthesis based on the linked source. This framing does not add evidence of successful delivery or results.

Case-specific decision guidance · untested

Case-specific decision guidance and first checks are original proposals. The linked source supports the attributed task; this added guidance has not been executed.

Read the attributed source evidence and original caveats below ↓

Why use this

  1. Reservation availability changes quickly, encouraging frequent checks that may conflict with a service’s access rules. A useful watch needs to balance the chance of seeing an opening with account protection and a clear end to the search.

  2. This job could define a restrained, authorized availability check with a stop rule before monitoring starts. Native waitlists or official alerts may offer a better route when automated access is restricted or the service gives no clear permitted checking method.

Why an agent / simpler alternative

Useful judgment

Apply several dining constraints and explain whether an opening genuinely matches.

Simpler alternative

Use the restaurant or reservation service’s official notify feature where available.

Unsuitable when

The service blocks automation, rate limits are unknown or access has already been restricted.

Proposed inputs

  1. Name

    Dining request

    Owner

    Diner

    Minimum scope

    Restaurant, party size, dates and acceptable time range

    Quality check

    Clarify whether outdoor seating or special arrangements are mandatory.

  2. Name

    Permitted watch scope

    Owner

    Account owner

    Minimum scope

    Authorized access method, request limit and expiration condition

    Quality check

    Check service restrictions before proposing any repeated access.

Access and setup — proposed or unknown

Proposed minimum
  1. Prefer official alerts; otherwise consider only permitted bounded read checks with an explicit request budget.

Compatibility unknowns
  1. Unknown: authorized monitoring support, request allowances and current account access.

External actions requiring approval
  1. Creating watches, booking, sharing diner details or accepting deposits and cancellation terms.

Expected deliverable and review checks

Proposed artifact

Matching-opening alert with search scope, observation time and any access limitation.

Critical checks
  1. The slot matches party size and required conditions.

  2. The watch stops on restrictions rather than changing accounts or access paths.

Missing output evidence

No new run or output inspection in this editorial layer; see linked source-specific limits.

Failure signals and proposed responses

  1. Signal

    The service returns a rate warning or access block.

    Why it matters

    Further attempts could worsen restrictions.

    Proposed response

    Stop immediately and report the block; use only a service-approved alternative.

  2. Signal

    A cancellation briefly appears but disappears before review.

    Why it matters

    The diner may assume a table is being held.

    Proposed response

    Label it observed availability and recheck only within the permitted budget before any authorized booking.

Effort and cost — unknown

Setup work
  1. Check permitted access and define request and time bounds.

Ongoing review
  1. Review genuine openings and stop on completion, expiry or restriction.

Unknowns
  1. Unknown: service limits, alert latency and any booking charges.

First check — proposed, unexecuted

Status

proposed_unexecuted

Synthetic fixture

A synthetic availability log contains a matching opening followed by a rate-limit response.

Acceptance checks
  1. The opening is labelled unreserved.

  2. The rate response terminates the proposed watch without retries or alternate identities.

Stop conditions
  1. Access is denied, permitted limits are unclear or booking terms need approval.

Limits

  1. A monitoring design must respect service controls; no frequency can be assumed safe without supporting permission.

Tasks: Travel & transport

Useful for: Personal and household

Editorial relevance from the title and source-supported actions; not evidence of the operator’s occupation.
Hermes AgentIndependent testing: No

Editorial candidate. This is source-backed reporting or a documented workflow. BotCurrent has not independently tested this task. A proposed Canadian adaptation is not evidence of a Canadian deployment or compliance certification.

Original source

https://x.com/bdistel/status/2089421994450170039 ↗

Attributed to: Brian Distelburger (@bdistel)

User report
Original action type
tool_action
What the source supports
The author reports a Hermes subagent monitoring Resy openings, followed by an account suspension caused by excessive requests.
Source outcome limits
Actions and outcomes are attributed user reports, not an independent reproduction or an execution guarantee.
Evidence attribution caveat
Actions and outcomes are attributed user reports, not an independent reproduction or an execution guarantee.
Source approval description
No rate limit set. Author recommends limits and guardrails. No booking approval checkpoint described.
Named tools
Hermes; Hannah agent; Resy; Obsidian; Telegram.
Model or version
Unknown
Publication date
Unknown
Source last checked
2026-10-14
Demonstrated in Canada
Unknown
Canadian availability
Unknown
Proposed Canadian adaptation
Use permitted reservation notifications where possible; obey Canadian restaurant platform limits and stop on warnings.
Recommended approval boundaries
Approve monitoring scope, a conservative request limit and each booking; stop on any platform restriction.

More examples of this task

Source-backed approaches using this or another agent. Not independently tested.

Browser Use

Stage an available restaurant table

Search live restaurant availability, choose a seating option and stop before confirmation.

Vendor report · Publication date unknown · Independently tested: No

https://browser-use.com/showcase/book-the-right-table ↗

Actions and outcomes are attributed vendor claims, not an independent reproduction or an execution guarantee.

Source facts, caveats and approval gates
Source attribution
Browser Use
Source publication date
Unknown
Source checked
2026-10-14
Model or version
Unknown
Named tools
Browser Use; opentable.com
Source approval description
Stops before confirmation.
Evidence attribution caveat
Actions and outcomes are attributed vendor claims, not an independent reproduction or an execution guarantee.
Source outcome limits
Actions and outcomes are attributed vendor claims, not an independent reproduction or an execution guarantee.
Recommended approval gates
Approve account access and any personal-data disclosure. Review before purchases, bookings, messages, archive requests, uploads or publication. Keep research read-only where possible.
Canadian availability
unverified
Demonstrated in Canada
Unknown
Proposed Canadian adaptation
Use a Canadian city, local time zone and requested accessibility; inspect cancellation charges before booking.

Meta Muse

Coordinate a restaurant booking through hotel correspondence

Author reports Muse making trip restaurant reservations and corresponding in Japanese with a hotel for a dinner slot unavailable online.

Vendor report · Published 2026-09-20 · Independently tested: No

https://x.com/Han_Fang_/status/2101874865385169348 ↗

Vendor-affiliated restaurant-reservation report; confirmation, charges and attendance were not verified.

Source facts, caveats and approval gates
Source attribution
Han Fang (@Han_Fang_)
Source publication date
2026-09-20
Source checked
2026-10-14
Model or version
Unknown
Named tools
Meta Muse; restaurant booking; hotel correspondence
Source approval description
Approval gates not stated.
Evidence attribution caveat
Actions and outcomes are attributed vendor claims, not an independent reproduction or an execution guarantee.
Source outcome limits
Vendor-affiliated restaurant-reservation report; confirmation, charges and attendance were not verified.
Recommended approval gates
Approve date/time, guest count, dietary disclosures, deposits and cancellation terms before commitment.
Canadian availability
Unknown
Demonstrated in Canada
Unknown
Proposed Canadian adaptation
Proposed: verify Canadian account/tool availability, authorized source use and applicable local workflow requirements.