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

How to run a personal WhatsApp assistant that remembers you with Wappy Kit

A self-hosted agent on your own machine that keeps session context across days of chats.

Credentials. Your WhatsApp access token, app secret, and model key sit in a local .env file, so keep that file out of version control.

Who it is forA developer who wants a private personal assistant on the WhatsApp app they already use every day.

The problemMost chat assistants forget earlier conversations, and hosted tools keep your chat history on someone else's servers.

The outcomeA WhatsApp agent running on your machine that keeps a session profile, so later messages still reflect earlier context.

What you need first

  • Node.js 22 or newer
  • A WhatsApp Cloud API app from Meta's developer portal with a phone number, access token, and app secret
  • A model API key from OpenAI, Anthropic, or Gemini, or a local Ollama install
  • A Google account, only if you use the Gmail/Calendar assistant

Steps

  1. Run npm create @wappy_ai/agent and answer the setup questions.
  2. Run cp .env.sample .env and add your model key and WhatsApp credentials.
  3. Run npm install.
  4. Run npm run dev and copy the printed tunnel URL into Meta's webhook configuration.
  5. Send a message to your WhatsApp number, then send a follow-up that depends on the first and check the reply uses that context.

Prompt for your agent

In the csr1010/wappy-kit repo, scaffold a project with `npm create @wappy_ai/agent` into ./<project-dir>. Expected output: a generated project folder with a .env.sample listing the model key and WhatsApp fields. Verify that no files were written outside ./<project-dir>.

Caveat. Wappy is pre-1.0, and the WhatsApp Cloud API setup in Meta's portal is a manual step that the installer does not do for you.

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