Status: [LIVE] Endpoints found: https://gitlab.com/api/v4/projects/42` Source: https://github.com/mpenchenat93/token-proxy # Token Proxy A local proxy for macOS that adds API tokens to requests, so AI agents (Claude Code, Codex, Cursor, scripts…) can call your services **without ever seeing a token**. ``` agent ──► http://127.0.0.1:8787/acme/coolify/api/v1/applications │ is route "coolify" of group "acme" enabled? │ + Authorization: Bearer ▼ https://coolify.acme.example/api/v1/applications ``` Token Proxy admin UI: routes grouped by owner, their state and the latest requests > The admin UI is in English and French: it follows your browser language and has a switcher. Admin API errors and Touch ID prompts follow the macOS language (French, or English otherwise; `TOKEN_PROXY_LANG=en` or `fr` overrides it). What the agent reads on the proxy port is always in English. The screenshots show demo data. ## Why An agent that calls an API needs a credential. Pasting it into the chat, an `.env` file or a shell variable puts it in the agent's context, its logs and its provider's servers. A prompt injection can then make the agent send the token elsewhere. Token Proxy keeps the tokens in the macOS Keychain and adds them to requests itself. The agent only knows a local URL. You choose which routes are open and for how long, and every change that grants more access needs your Touch ID, which an agent cannot provide. ## How it works - A **route** maps a local URL to a service: `http://127.0.0.1:8787///` is forwarded to `/` with the token added, as `Authorization: Bearer`, a custom header (`x-api-key`…) or a query parameter (`access_token`…). - A **group** says whose account a route uses: `perso` for your own, one group per client (`acme`, `globex`…). The URL always names the group, so an agent c