Skip to content
| Marketplace
Sign in
Visual Studio Code>AI>Cortega AI Booster PackNew to Visual Studio Code? Get it now.
Cortega AI Booster Pack

Cortega AI Booster Pack

Cortega

|
1 install
| (0) | Free
Signs developers, lawyers and other teams in to Cortega; governs AI tools, selects projects, and protects sensitive work.
Installation
Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.
Copied to clipboard
More Info

Cortega AI Booster Pack (VS Code extension)

Signs developers, lawyers and other teams in to Cortega and routes their AI tools (Claude Code, Codex, Continue, OpenCode, Pi, Goose, Aider, and Cursor) through the Cortega gateway. Design: docs/product/legal-extension-pack-design.md.

Slices 1 and 2 of the build: sign-in, tool provisioning, drift repair, undo, citation checks in the editor, and the Cortega AI Booster Pack MCP server. It also has a project picker and a privileged/sensitive-work switch (status bar and the Cortega AI Booster Pack: Choose project and Turn privileged/sensitive work on or off commands). Both are held on the Cortega server and applied by the gateway to every request from your AI tools. A project can be marked sensitive. While one is selected the privileged mark is always on, so the person does not set it.

What it does

  • Sign in with your work email. Cortega opens your browser, shows a code that must match the one in VS Code, and signs you in with your organization's identity provider.
  • Configures supported tools with the Cortega gateway address, credentials, and model selection. Discovers installed VS Code extensions, standalone tool configuration, and commands on PATH. Claude Code and Codex share configuration with their standalone clients. OpenCode, Pi, Goose, and Aider work without a VS Code plugin. Cursor uses its saved BYOK settings. Existing user settings are retained and changed values are recorded for undo.
  • Turns VS Code telemetry off, and stops the Claude Code extension asking for an Anthropic sign-in.
  • Registers a VS computer seat on sign-in and sync, using VS Code's computer ID and your authenticated account. It appears in Devices and counts against Endpoint Guard / AI Booster and installation Edge seat limits. Repeated sign-in on the same computer reuses it; deletion permits registration again.
  • Detects drift every 5 minutes and syncs settings every 30 minutes. Run Sync AI tools to repair immediately. The status menu's Show status and repair details and the Cortega Output channel show missing settings, mismatches, and file errors. Claude Code and Codex share settings across windows and native clients under the same OS user, so another account's sync may replace them.
  • Reports Git repositories when the tenant ticks Collect repository inventory. Sync sends open workspace roots and a bounded scan of the signed-in user's home directory: remotes, branch, Git identity, and working-tree state. Local paths are included. Source code is not sent. Remote (vscode-remote://) folders are skipped. Open folders are marked open or focused; other home checkouts are included with their dirty/clean state.
  • Undo puts every file and setting back. Sign out does the same.
  • Uninstalling attempts to restore all configured tools too. Close Cursor before uninstalling. VS Code runs dist/uninstall.js after the extension is removed and the editor restarts. Disabling does not undo anything: VS Code gives an extension no warning that it is about to be disabled, so run Undo all changes to my AI tools before you disable it. If it is already disabled, node dist/uninstall.js in the installed extension's folder does the same revert. The uninstall script cannot restore VS Code's own settings (telemetry off, no Claude Code login prompt), because those need the editor.
  • Checks citations. Verify citations (editor right-click menu, or the command palette) checks the selection or the open document. A citation that is not found gets a red squiggle with the reason, and a verified one gets a check mark. The marks go away when you edit the text. Verify citations in a document (explorer right-click, for .pdf, .docx, .txt, .md and others) opens a report.
  • Adds a Projects server too. The same sign-in registers the Cortega Projects MCP server in Claude Code and Codex, so an assistant can list the organization's projects and, for people who may change them, add, update or bulk load projects, including the sensitive flag.
  • Gives your AI tools the same check. Claude Code, Codex and Continue are given the Cortega AI Booster Pack MCP server, so an agent can run verify_citations on its own draft before showing it to you.

Supported tools and platform behavior

The extension runs locally in desktop VS Code on Windows and macOS. Install the AI clients you want to use separately; Cortega AI Booster Pack does not bundle or install third-party clients. It is not a browser extension; extensionKind: ui keeps local device configuration on the local host in remote workspaces. Gateway controls apply to requests actually sent through Cortega. Configuration does not prevent bypass; use Endpoint Guard on macOS when you need Shadow AI discovery, monitoring, or blocking.

Tool Configuration
Claude Code ~/.claude/settings.json and user MCP configuration
Codex ~/.codex/config.toml (shared with CLI and desktop clients)
Continue ~/.continue/config.yaml
OpenCode ~/.config/opencode/opencode.json or existing opencode.jsonc; ~/.local/share/opencode/auth.json
Pi ~/.pi/agent/{models,auth,settings}.json
Goose config.yaml and a dedicated custom_providers/custom_cortega.json; user OpenAI keychain credentials are retained
Aider ~/.aider.conf.yml; main, weak, and editor models use the gateway
Cursor User/globalStorage/state.vscdb under Cursor's app-data directory

XDG configuration/data directories, PI_CODING_AGENT_DIR, and GOOSE_PATH_ROOT are respected. On Windows, Cursor uses %APPDATA%/Cursor and Goose uses %APPDATA%/Block/goose/config. On macOS, Cursor uses ~/Library/Application Support/Cursor; Goose also recognizes an existing ~/Library/Application Support/Block/goose configuration directory.

Cursor: quit Cursor and run Sync in VS Code, then reopen Cursor. Sync and undo refuse to replace its database while Cursor is running or SQLite journals are present. This adapter uses internal Cursor settings, which may change between versions. It configures supported BYOK model requests; Cursor-specific cloud features are not routed through Cortega. Cursor documents that BYOK requests pass through its servers for prompt building. This does not make Cursor fully local. The gateway must be reachable through that request path.

Overrides: project configuration, command-line flags, environment variables, custom profiles, and existing sessions can override a tool's global defaults. Restart clients or start a fresh session after sync and verify that traffic appears in Cortega. New file-based adapters preserve comments, restore prior managed values, and leave later user edits intact on undo.

Models: router mode uses the server's default model alias. In direct mode, choose an available model before configuring tools that require a model ID. Codex keeps its native catalog selection; the gateway resolves its request as before. Legal MCP provisioning remains available for Claude Code, Codex, and Continue; the new adapters configure model traffic only.

Package and deploy

Run ./ai-pack/deploy/build.sh 0.1.2 from the repository root to set the version and build the customer VSIX plus checksum. See deploy/README.md for installation, managed-machine policy, and Open VSX publishing. pack/extensions.json records the AI client extensions Cortega can configure and their terms; npm run pack:build refreshes the licence inventory and policy files.

Develop

npm install
npm run typecheck
npm test            # unit tests, no editor needed
npm run build       # bundles to dist/extension.js
npm run test:host   # loads the built bundle in a real VS Code with a throwaway profile

test:host starts a VS Code window using /Applications/Visual Studio Code.app (pass another path as an argument). It uses its own profile and home directory, so nothing of yours changes. Redirect its output when running it from a script, because the editor's child processes keep the pipe open for a moment after it finishes.

Server address: setting cortega.ai.serverUrl (default https://live.cortega.ai).

Against the local dev stack use http://localhost:8001 (the management backend). Sign-in sends the IdP a redirect address built from this URL, and the dev Google client has only http://localhost:8001/api/v1/edge/sso/oauth/callback registered, so localhost:8080 fails with redirect_uri_mismatch.

./ai-pack/deploy/build.sh 0.1.2

cd ai-pack/release shasum -a 256 -c SHA256SUMS code --install-extension cortega-ai-pack-0.1.2.vsix

{ "cortega.ai.serverUrl": "http://localhost:" }

Upgrade from Cortega Legal

The extension is now cortega.cortega-ai-pack and the directory is ai-pack/. Before installing the new extension, run the old extension's Undo command and uninstall it; then install Cortega AI Booster Pack and sign in again. Do not run both extensions together. Existing server settings are read as fallback. Shared recovery state and owned Claude MCP entries migrate safely; entries you have changed are preserved.

The shared Projects MCP server (config name cortega-matters-projects) is registered in Claude Code and Codex. Cortega Agents → Insights → Project shows usage cost by explicit request selection or assigned conversation. The agent assigns confident captured sessions after pauses; it never changes your picker selection for unrelated work.

  • Contact us
  • Jobs
  • Privacy
  • Manage cookies
  • Terms of use
  • Trademarks
  • Your Privacy Choices
  • Consumer Health Privacy
© 2026 Microsoft