v1.0.5 β€” Latest Release

WorkspaceGPT Extension Docs

Everything you need to install, configure, and get the most out of WorkspaceGPT inside VS Code, Cursor, or Antigravity.

πŸ”

Privacy-First

100% local with Ollama β€” no data leaves your machine. Cloud providers available optionally.

πŸ€–

RAG-Powered

Retrieval-Augmented Generation over your codebase, Confluence docs, and ADO tickets.

⚑

Zero Setup

Install from the marketplace and start chatting in under 2 minutes.

Installation

Available in the VS Code and Cursor marketplaces, and on Open VSX for Antigravity.

1

Via Extensions Marketplace

Open VS Code, Cursor, or Antigravity and navigate to the Extensions view:

Ctrl+Shift+X Β or Β Cmd+Shift+X on macOS

Search for WorkspaceGPT and click Install.

2

Via Command Palette

Press Ctrl+P to open Quick Open and run:

bash
ext install Riteshkant.workspacegpt-extension
3

Via Marketplace Website

Visit the VS Code Marketplace page and click Install.

4

On Antigravity (or other VS Code forks)

Antigravity, Windsurf, and VSCodium install from Open VSX instead of the Microsoft Marketplace. Search WorkspaceGPT in the Extensions view, or open the Open VSX page and click Download.

Minimum VS Code version: 1.98.0. WorkspaceGPT activates automatically on startup (onStartupFinished).

AI Providers

Choose between fully local operation with Ollama or cloud-based providers for maximum capability.

ProviderPrivacyRequires API KeyNotes
Ollama100% LocalNoDefault. Run llama3.2:1b or any local model.
OpenAICloudYesGPT-4o, GPT-4-turbo, GPT-3.5 etc.
GeminiCloudYesGoogle's Gemini Pro/Flash models.
GroqCloudYesHigh-speed inference on Llama / Mixtral.
OpenRouterCloudYesAccess 100+ models via one API key.
RequestlyCloudYesCustom API endpoint proxy integration.

Configuring Ollama (Recommended)

1

Install Ollama

Download from ollama.com and follow the installer for your OS.

2

Pull a model

bash
ollama pull llama3.2:1b

For better responses, try a larger model:

bash
ollama pull llama3.2:4b
# or
ollama pull gemma3:4b
# or
ollama pull mistral
3

Select in WorkspaceGPT

Open the WorkspaceGPT sidebar β†’ Settings β†’ Providers β†’ Ollama. Your locally running models will appear automatically.

Configuring Cloud Providers

Open Settings β†’ Providers, select your provider, and paste your API key. Keys are stored securely in VS Code's secret storage and never logged.

Codebase Indexing

WorkspaceGPT indexes your local workspace files so you can chat with your own code.

1

Open the Codebase panel

In the WorkspaceGPT sidebar, go to Settings β†’ Codebase.

2

Start Sync

Click Start Sync. The extension will walk the workspace folder tree, generate embeddings using the bundled local model (all-MiniLM-L6-v2), and store them in VS Code's global storage.

3

Chat with your code

Once indexing is complete, your questions will automatically draw context from your codebase alongside any other connected data sources.

Note: Large monorepos may take a few minutes to index on first run. Subsequent syncs are incremental and much faster.

Embeddings & Vector Storage

Every connected source (codebase, Confluence, ADO) is turned into vector embeddings and stored so WorkspaceGPT can retrieve the right context. You control both halves: which model makes the embeddings, and where the vectors live.

Embedding provider

ProviderModelAPI keyBest for
Local DefaultXenova/all-MiniLM-L6-v2 (384-dim)Not neededFull privacy β€” runs on-device, nothing leaves your machine. First run downloads ~200Β MB.
Google Geminigemini-embedding-001 (768-dim)RequiredFaster, higher quality, and required for sharing to the Chrome extension.

Configure under Settings β†’ Embeddings. Keys are stored in VS Code's encrypted secret storage.

Vector storage

πŸ’Ύ

Local (on this machine)

Vectors are written to binary files in the extension's storage. Nothing leaves your machine. The default β€” ideal for solo, privacy-critical use.

☁️

Cloud β€” Qdrant

Vectors live in a Qdrant cluster (self-hosted or Qdrant Cloud). Provide the cluster URL and API key, then click Test connection. Enables sharing and larger datasets.

Configure under Settings β†’ Vector Storage. Cloud-Qdrant URLs from the dashboard are auto-normalized to include the :6333 port.

Re-index when you switch: changing the embedding provider or the storage location means existing vectors no longer match β€” WorkspaceGPT will prompt you to re-index your connected sources. (Different models also produce different vector dimensions.)

Confluence Integration

Connect your Atlassian Confluence space with one-click OAuth 2.0 authentication.

1

Open Confluence settings

In the WorkspaceGPT sidebar, navigate to Settings β†’ Confluence Integration.

2

Sign in with Atlassian

Click Sign In. A browser window will open to Atlassian's OAuth consent screen. Sign in and grant access β€” no passwords are stored.

The extension spins up a short-lived local HTTP server to capture the OAuth callback securely.

3

Select a space

After authentication, your accessible Confluence sites and spaces will load. Select the spaces you want to index.

4

Start Sync

Click Start Sync. Pages are fetched, converted to Markdown, embedded, and stored locally. Progress is shown in real-time.

5

Automatic background sync

The ConfluenceSyncScheduler starts automatically on extension activation and keeps your index up-to-date in the background.

Token security

OAuth access + refresh tokens are stored in VS Code's encrypted context.secrets β€” never in plaintext settings.

Disconnect anytime

Go to Settings β†’ Confluence β†’ Disconnect to revoke access and clear all synced data.

Azure DevOps Integration

Connect Azure DevOps to chat with work items, user stories, and pull requests.

1

Generate a Personal Access Token (PAT)

In Azure DevOps, go to User Settings β†’ Personal Access Tokens β†’ New Token.

Grant at minimum: Work Items β€” Read Code β€” Read

2

Open ADO settings

In the WorkspaceGPT sidebar, go to Settings β†’ Azure DevOps Integration.

3

Enter your organization URL and PAT

Provide your Azure DevOps organization URL (e.g. https://dev.azure.com/your-org) and the PAT you generated.

The PAT is stored in VS Code's context.secrets, never in globalState.

4

Select project and sync

Your ADO projects will load automatically. Select a project and click Start Sync.

Work items are embedded and indexed locally β€” no data is sent to third-party servers.

Auth format: The extension uses Basic base64(:PAT) (colon-prefixed PAT) as required by the Azure DevOps REST API.
Enterprise

Deployment Automation

Turn the manual release checklist β€” syncing feature flags, env vars, and component versions across environments β€” into a reviewable, one-click pipeline. The model is inspired by AWS CodePipeline: a pluggable Source feeds ordered Stages of Actions. Nothing is hardwired to one team's setup.

🧩

Pluggable

Pick a source, then add only the deploy actions your org actually uses. No provider is baked in.

πŸ›‘οΈ

Plan β†’ Approve β†’ Apply

Every change is previewed as a diff you approve before anything is written. Backend changes open a PR β€” never an auto-merge.

πŸ”

Discover & select

Repos, workflows, projects, and table columns are detected from your connected accounts β€” choose from dropdowns, don't type IDs.

Full deployment guide

Sources, actions, connections (PAT/SSO + Vercel gotchas), the Releases workflow, environments, security, troubleshooting & FAQ.

Read the guide β†’

MCP Server

WorkspaceGPT ships a built-in MCP (Model Context Protocol) server for GitHub Copilot and Claude Code integration.

1

Connect the MCP Server

Open the Command Palette (Cmd/Ctrl+Shift+P) and run:

vscode command
WorkspaceGPT: Connect MCP Server
2

Use with GitHub Copilot or Claude

The MCP server is registered as a definition provider for Copilot Chat (@mcp). Once connected, Copilot and Claude can query your indexed data directly via the WorkspaceGPT context.

Status bar indicator: After connecting, a WorkspaceGPT button appears in the VS Code status bar showing MCP connection health.
Companion app

Chrome Extension

A browser side-panel that lets you (or a teammate) chat with your indexed Confluence pages and Azure DevOps work items β€” without opening VS Code. It runs entirely in the browser, talking directly to your providers; there's no WorkspaceGPT server in between.

🧭

Side panel

Ask questions and read grounded answers from a panel docked in Chrome.

πŸ”—

One share code

Connect by pasting a single code generated in VS Code β€” no separate setup.

🚫

No server

Calls go browser β†’ Gemini / Qdrant / your chat model directly. Nothing is proxied.

Prerequisites

Because the browser needs cloud-reachable services, the share flow requires: Gemini embeddings, a Qdrant Cloud vector store, and a chat model with an API key β€” all configured in VS Code first (see Embeddings & Vector Storage).

Setup

1

Install from the Chrome Web Store

Add WorkspaceGPT for Chrome to your browser.

2

Create a share code in VS Code

In the WorkspaceGPT sidebar, open Settings β†’ Share to Chrome and click Create share code. It's copied to your clipboard.

If a prerequisite is missing, the button tells you exactly what to fix first.

3

Paste it into the extension

Open the Chrome side panel β†’ Settings β†’ paste the code β†’ Connect. You'll see a confirmation with your Qdrant URL.

4

Ask away

Close settings and chat. The extension mirrors VS Code's retrieval, so answers stay consistent across Confluence and ADO.

Treat the share code like a password

It contains your real Qdrant, Gemini, and chat-model API keys in plain form. Anyone with it can query your data and incur API costs. Share only with people you trust.

Write creds are never shared

GitHub, Vercel, Confluence, and ADO tokens stay in VS Code secret storage and are excluded from the bundle. The share is read-only knowledge access.

Scope: the extension covers Confluence and Azure DevOps knowledge. Local codebase indexing stays in VS Code and is not part of the share. Regenerate the code if you rotate your keys.

Commands & Keyboard Shortcuts

All commands are accessible from the Command Palette.

CommandShortcutDescription
WorkspaceGPT: AskCmd+Shift+R / Ctrl+Shift+ROpen & focus the WorkspaceGPT chat panel.
WorkspaceGPT: New Chatβ€”Start a fresh conversation, clearing history.
WorkspaceGPT: Settingsβ€”Open the settings panel inside the sidebar.
WorkspaceGPT: Chat Historyβ€”Browse and restore previous chat sessions.
WorkspaceGPT: Connect MCP Serverβ€”Register the MCP server for Copilot / Claude.
WorkspaceGPT: Clear All Data and Cacheβ€”Wipe all embeddings, state, and tokens.

Activity Bar & Title Bar Icons

βž•

New Chat

Click the + icon in the WorkspaceGPT title bar to start a new session.

βš™οΈ

Settings

The gear icon opens provider and integration configuration.

πŸ•

History

Browse, restore, or delete previous chat sessions.

Reset & Clear Data

WorkspaceGPT stores all data locally in VS Code's global storage. You can wipe everything at any time.

1

Via Command Palette

Run WorkspaceGPT: Clear All Data and Cache from the Command Palette. A confirmation prompt will appear.

2

Via Settings panel

Open Settings β†’ Reset VSCode State inside the WorkspaceGPT sidebar.

Warning: This action clears all embeddings, OAuth tokens, PATs, and chat history. It cannot be undone. Background schedulers are stopped automatically before the wipe.

Troubleshooting

Common issues and how to fix them.

⚠Extension not loading / sidebar not showing
Ensure VS Code β‰₯ 1.98.0. Check the Extensions panel for error banners. Try reloading the window (Cmd/Ctrl+Shift+P β†’ Reload Window).
⚠Ollama models not appearing
Make sure the Ollama server is running (ollama serve). The default endpoint is http://localhost:11434. Verify at least one model is pulled: ollama list.
⚠Codebase indexing is slow
Large repos with many files take longer. Indexing is incremental after the first run. Exclude large generated/build directories by adding them to .gitignore.
⚠Confluence sync fails
Re-authenticate: Settings β†’ Confluence β†’ Disconnect, then Sign In again. Ensure your Atlassian account has read access to the target space.
⚠ADO sync not working
Verify your PAT has Work Items β€” Read and Code β€” Read scopes. Re-enter the PAT in Settings β†’ Azure DevOps. Check the organization URL format: https://dev.azure.com/your-org.
⚠Chat returns no results or irrelevant answers
Confirm the relevant data source is indexed (check the sync status in Settings). Try re-syncing. For better quality answers, switch to a larger Ollama model or a cloud provider.
⚠MCP server not detected by Copilot
Run WorkspaceGPT: Connect MCP Server from the Command Palette. Reload the window after connecting.