Cursor & VS Code

Cursor, VS Code with the official AI extensions, and most AI coding tools read OPENAI_BASE_URL / OPENAI_API_KEY. Set them globally and every suggestion, chat, and tool call flows through TapPass.

Cursor

Open Settings → Cursor → Models → OpenAI API key:

• OpenAI Base URL: https://tappass.example.com/v1
• OpenAI API Key: tp_...
• Toggle off Use OpenAI GPT-4 directly

Save. Cursor’s chat, Cmd-K, and Composer now all flow through TapPass.

Anthropic in Cursor

For Claude models, also set:

• Anthropic Base URL: https://tappass.example.com
• Anthropic API Key: tp_...

VS Code + GitHub Copilot

Note

Native Copilot integration is on the roadmap. Today you can route Copilot Chat’s @ external models through TapPass using OPENAI_BASE_URL — but autocompletion still goes to GitHub directly.

VS Code + other AI extensions

For extensions that accept a custom OpenAI endpoint (Continue, Cody, Codeium’s custom endpoint mode):

Add to your shell profile:

export OPENAI_BASE_URL=https://tappass.example.com/v1
export OPENAI_API_KEY=tp_...

Restart VS Code. Most extensions pick the env vars up on launch.

Per-workspace override

Drop a .env at the root of your workspace:

.env

OPENAI_BASE_URL=https://tappass.example.com/v1
OPENAI_API_KEY=tp_dev_team_alice

VS Code’s Python and Node extensions load workspace .env files automatically.

Why this matters

IDE assistants pull from your code. Without TapPass, secrets in open files are sent to OpenAI/Anthropic as context. With TapPass:

• PII detection masks emails, keys, and tokens from prompts before forwarding
• Audit trail captures what source files were included in which prompts
• Per-developer tp_ keys show exactly who prompted what