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.

For step-by-step, per-tool setup see Cursor and GitHub Copilot under Connect your harness. This page is the general env-var approach for VS Code and other editor extensions.

See the dedicated Cursor page for the current setup: a custom OpenAI base URL (https://app.tappass.ai/v1), plus Anthropic mode for Claude models. Use a per-developer tp_ key.

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://app.tappass.ai/v1
export OPENAI_API_KEY=tp_...

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

Drop a .env at the root of your workspace:

OPENAI_BASE_URL=https://app.tappass.ai/v1
OPENAI_API_KEY=tp_dev_team_alice

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

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