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

How to run research chats with memory and live web search with Whirl

Enable web search, page reading, and long-term memory so answers use today's web and past context.

Credentials. Exa and Supermemory each need their own API key, so store those keys in Convex env settings and not in client code.

Who it is forA researcher or analyst who asks repeat questions over days and needs current sources in each answer.

The problemA chat model answers from old training data and forgets your projects between sessions, so you repeat context and check sources by hand.

The outcomeAnswers grounded in live web results, plus preferences and projects remembered across chats.

What you need first

  • Bun installed
  • A free Convex account
  • A Clerk application
  • An OpenRouter API key
  • Git and a terminal

Steps

  1. Complete the self-host steps and confirm the app runs at localhost:3000.
  2. Open docs/configuration.md and find the keys for web search (Exa) and memory (Supermemory).
  3. Add those keys to your Convex deployment using the same env set command pattern from the quick start.
  4. Start a chat, ask a question that needs current information, and confirm sources appear.
  5. Tell Whirl a project preference in one chat and check that it is recalled in a new chat.

Prompt for your agent

In the whirlchat/whirl repo, open docs/configuration.md and list the exact environment variable names for Exa and Supermemory. Output them as a table with the feature each one enables. Verify each name against the file before reporting.

Caveat. The README says these features are hidden until their keys are set, so a missing key will make search or memory appear absent rather than fail loudly.

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