Your data stays on your machine
Indexing and embeddings run on-device, and the vector index is written to local files. We never upload your documents or your code.
Zero data retention
We store no prompts, no answers, no documents — not even in logs. In Remote mode your question is processed in memory and discarded.
Never used for training
Nothing you ask is used to train a model, sold, or shared. Anonymous feature-usage counts are all we measure — never your content.
Read the full privacy policy — it lists every byte we hold.
Two modes, one guarantee
The mode changes exactly one thing: where the answer is generated. Your documents, your code, and the search index built from them stay local either way.
Everything runs locally
Your model, your hardware. With Ollama, none of your content leaves your computer — no account, no cloud round-trip. Prefer a bigger model? Plug in your own provider key and you still decide exactly where your data goes.
- ✓ Chat model on your machine via Ollama — or your own API key
- ✓ Embeddings generated on-device
- ✓ Vector index in local files
- ✓ No account — runs offline with a local model
We run the infrastructure
We host the inference and choose the model, so there is nothing to configure and no model key to buy. Your data still stays local: only your question and the snippets retrieved for it reach our endpoint — and we keep none of it.
- ✓ Managed model — no provider keys, no setup
- ✓ Embeddings still generated on-device
- ✓ Vector index still in local files
- ✓ Sign in with GitHub; every request re-verified
- ✓ Zero retention — nothing stored, nothing logged
Capabilities designed for builders
A full agent that reads, edits and verifies — with the docs and tickets that explain why already in reach.
Agentic coding
The agent searches and reads your code, makes multi-file edits, then runs your linter, type-checker and tests to verify its own work before handing it back.
Confluence One-Click
Connect your space in one click and your team's documentation becomes context the agent can pull mid-task — the design page, not just the file.
Azure DevOps (ADO)
Work items, user stories and PR context synced and searchable, so a run can be grounded in the ticket that asked for it.
Review before it writes
Every file change arrives as a diff you approve or reject. A checkpoint is taken before the first write, so one click reverts the whole turn.
Codebase understanding
ripgrep search plus symbol, definition and reference lookup through your editor's own language server.
Your work, on open
The sidebar lists the ADO items assigned to you with their state and sprint — start a run straight from a ticket.
Web search mid-task
Lets the agent look up what your code and docs can't tell it: a new library, an unfamiliar API, current release notes.
@-mentions
Pull a specific file or folder into the conversation instead of hoping retrieval finds it.
Release automation
Config-sync and hotfix pipelines with a plan → approve → apply flow, so work doesn't stop at “PR opened”.
MCP server
Ships an MCP server that exposes your Confluence and ADO search to Claude Desktop, Cursor and other MCP clients.
Runs offline
In Local mode with Ollama there are no remote APIs at all — the whole loop works on a plane.
Chat where you want it
Run it in the sidebar or open it as a full editor tab, with several sessions going at once.
Ready in minutes
Installation
WorkspaceGPT is available directly through the marketplace. Install it for VS Code, Cursor, or Antigravity.
Pick your mode
Open Settings > Mode. Either way, indexing stays on your machine.
- Local — bring your own model. Ollama for fully offline (default
llama3.2:1b), or your own OpenAI / Claude / Gemini / Groq / OpenRouter key — or any OpenAI-compatible endpoint. - Remote (preview) — sign in with GitHub and we handle the model. No keys, nothing to configure.
No re-index when you switch — the mode only moves inference, never your index.
Connect Contexts
Confluence Start
Go to Settings > Confluence. Click Sign in for one-click auth, and hit Sync.
ADO Synchronization
Go to Settings > ADO Integration. Enter PAT to sync pull requests, tickets, and work items.
