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

How to hide API keys from a relay before requests leave your machine with Think Watch Lite

Replace secrets in requests with placeholders so a relay never receives the real key or private data.

Credentials. Test with dummy values first and keep the gateway's request history private, since it stores request and answer text that may include keys.

Who it is forA user who sends AI requests through a third-party relay and does not want that relay to see API keys, private keys or personal identifiers.

The problemA relay sees every request in full, so any key or sensitive value inside a prompt is exposed to it.

The outcomeAPI keys, private keys, JWTs, connection-string passwords and similar values are swapped for placeholders before the request leaves the machine.

What you need first

  • A supported computer: macOS 12 or later on Apple silicon, Windows 10 21H2 or later, or a Linux x86_64 or aarch64 machine
  • At least one upstream you already have access to, such as an API key, a relay, or a local model
  • The AI client you want to connect, such as Claude Code or Codex, already installed

Steps

  1. Install the app and connect your client through the gateway as described in the install section of the README.
  2. Add the relay as an upstream in the gateway.
  3. Open the secrets and privacy protection and switch it on, starting from Monitor mode to see what it would change.
  4. Send a test request that contains a dummy key and check the request log to confirm the placeholder was used.
  5. Switch the protection from Monitor to active once you are satisfied with the results.

Prompt for your agent

Using the repo ThinkWatchProject/ThinkWatch-Lite, enable the secrets and privacy protection and route a test request containing the dummy value <dummy key> through the relay <relay name>. Expected output: the relay-side request shows a placeholder instead of the dummy key. Verify this in the request history of the gateway.

Caveat. The README says each protection starts in Monitor mode and is switched on one at a time, so it does not block anything until you turn it on.

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