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

How to book tickets and run errands by iMessage with Open Instinct

Text your assistant a chore and it uses a cloud browser to try to finish it.

  • Top pick
  • Life admin
  • Intermediate
  • 60 minutes
  • From the README
  • Any agent

Who it is forA busy person who wants to hand off chores like booking movie tickets or ordering groceries from a phone text thread.

The problemRoutine online errands take time that could go to other work, and most assistants cannot act inside a website for you.

The outcomeYou text a task to your own assistant line and it works through a browser on your behalf while you stay in control.

What you need first

  • A Vercel account on the Pro plan, since the Hobby plan cannot run the every-minute schedule
  • A Kernel account on its free plan for cloud browsers
  • A Neon account on its free plan for Postgres
  • An iMessage-capable phone to verify the managed Linq line
  • A Stripe account only if you want Link wallet purchases

Steps

  1. Open https://github.com/Merit-Systems/OpenInstinct and click Deploy with Vercel, selecting a Pro team.
  2. In the connector's Vercel Connect settings, complete the one-time Phone Numbers verification for the Linq line.
  3. Open your deployed app and sign in with your phone number.
  4. Text the Linq number a task such as booking movie tickets or ordering groceries.

Prompt for your agent

Using the repo Merit-Systems/OpenInstinct, deploy it to a Vercel Pro team and confirm the Linq line is verified for <target phone number>. Expected output: a live app URL and a reply to a test iMessage from the assistant. Verify that sign-in with the phone number works before reporting success.

Caveat. The app needs a Vercel Pro plan because the Hobby plan only allows daily cron jobs and Open Instinct checks for scheduled work every minute.

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