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

How to keep sensitive chats locked on your device with Whirl

Use locked chats so messages are encrypted on your device and answered only by zero-retention models.

Who it is forA user or team member who discusses sensitive material and wants chats the server cannot read.

The problemStandard chat history is stored on servers, so sensitive conversations stay exposed to whoever runs the backend.

The outcomeChats that are encrypted on your device with a password the server never sees.

What you need first

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

Steps

  1. Run the self-host steps and open Whirl at localhost:3000.
  2. Start a new chat and choose the locked chat option in the app.
  3. Set a password for the locked chat and keep it somewhere safe.
  4. Send messages and confirm that the model answering is a zero-retention model.
  5. Reopen the locked chat later and enter the password to read it.

Prompt for your agent

In the whirlchat/whirl repo, read the README's Locked chats feature and the docs/architecture.md file, then explain how a locked chat is encrypted and which models answer it. Output a short summary with two cited facts. Verify that every claim appears in the README or docs.

Caveat. The README does not describe password recovery, so assume a lost password may leave a locked chat unreadable until the README or docs say otherwise.

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