DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to fill a booking form up to the last button at a set time with Andee

Andee opens an app at the time you set, reads the page and fills everything up to just before the final button.

Credentials. Booking forms may need your personal details or account login, which Andee fills in on the device.

Who it is forA person who wants to book something the moment a site or app opens, such as a limited slot.

The problemLimited bookings disappear quickly, and filling in the form by hand at the exact moment is hard to do.

The outcomeAt the set time, the form is filled in up to the last button, and you complete the payment and final confirmation yourself.

What you need first

  • An Android phone (the README says Android is the only shipped body today)
  • Permission to install the Andee APK and to enable its accessibility service
  • Access to an OpenAI-compatible model endpoint and its API key, since you choose the model
  • A speech provider account if you use voice, Volcengine by default or Google if you select it

Steps

  1. Install the Andee APK and enable its accessibility service.
  2. Set the model Andee should use for reading the page.
  3. Ask Andee to book it for you at the time you choose, for example "Book it for me the moment it opens."
  4. Check the filled form before the final button, then complete payment and the final confirmation yourself.

Prompt for your agent

Using the Andee repo at github.com/kuafuai/andee, schedule Andee to open <target app> at <time> and fill the booking form to just before the final button. Expected output: a filled form with the last button and payment left for the user. Verify that Andee does not enter a payment password or press the final confirmation.

Caveat. The README says a scheduled task must be set and confirmed before Andee promises to remind you, so confirm the time before you leave the phone.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page