DEDUPED Hot AI repos, turned into use cases Get the Monday 5

How to route an IDE assistant's API traffic through the gateway with Cosy Redact Gateway

Set a custom API base URL in a coding assistant so its requests pass through the redaction layer.

Credentials. Assistants that run remotely cannot reach 127.0.0.1 on your machine, and the assistant's auth headers are forwarded upstream by design.

Who it is forA developer using an IDE or CLI coding assistant that accepts a custom base URL and who regularly pastes code containing internal tokens.

The problemAssistant requests include file contents and tool results, which can carry tokens that have no known key format.

The outcomeThe assistant's supported requests go through the local gateway, and you have checked the actual request path with synthetic data before using it on sensitive work.

What you need first

  • Node.js 20+, Git, and a terminal
  • An OpenAI or Anthropic API key and an available model name, only if you make live upstream calls
  • A trusted environment for running the gateway, since it handles raw requests and provider credentials

Steps

  1. Start the gateway from the repo folder with npm start
  2. Confirm the service is running with curl --fail --silent --show-error http://127.0.0.1:8787/healthz
  3. Set the assistant's custom base URL to http://127.0.0.1:8787/$https://api.openai.com/v1 or the Anthropic-style form from the README table, matching the protocol it uses
  4. Send a synthetic test prompt and check the gateway's behavior before using real code

Prompt for your agent

Start the CosyRedactGateway with `npm start`, then configure <assistant-name> to use base URL `http://127.0.0.1:8787/$https://api.openai.com/v1` or the Anthropic-style form as its protocol requires. Send a synthetic test value and report whether the assistant's request reaches the gateway, noting that the README makes no specific compatibility guarantee for this tool.

Caveat. The README does not certify compatibility with any specific assistant version, so verify the real request path with synthetic data before relying on it.

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