The AI coding agent that starts from your Azure DevOps ticket
Your work starts as a work item, not a prompt. WorkspaceGPT opens on the Azure DevOps items assigned to you, so you can start a run straight from a bug or user story — with the ticket, its history and the related design docs already in context.
A ticket isn't a prompt
Copying a work item into a chat window loses the acceptance criteria, the linked discussion and the design page the ticket assumes you've read. The agent builds the wrong thing quickly.
WorkspaceGPT reads the work item itself, searches your connected Confluence and Jira knowledge for the context around it, and works through the change in the open: analyse, plan, implement, run the checks, verify.
How it works
1. Connect Azure DevOps
Your assigned work items appear in the sidebar with their type, state and sprint when you open it.
2. Start from the ticket
Pick an item and start a run. The agent reads the work item, then searches your docs and code for the rest of the picture.
3. Verify, then hand it back
It runs your linter, type-checker and tests, writes a report of what changed and what passed, and can post that report on the ticket. Create PR commits only what the agent changed to a fresh branch.
What you get
Your work, on open
No pasting ticket numbers. The sidebar lists what is assigned to you and suggests the next action.
Checked, not just generated
A run isn't finished when the code is written. It runs your project's own checks and reports which passed, so you start review from evidence.
As hands-off as you want
Let it edit on its own, have it plan first, or review every diff. A checkpoint is taken before the first write, so one click reverts the whole turn.
Private by architecture
Work items are indexed on your machine. We store no prompts, answers or documents, and nothing you ask is used to train a model.
Frequently asked questions
- Can an AI agent work on Azure DevOps work items?
- Yes. WorkspaceGPT reads the Azure DevOps items assigned to you, starts a run from one, and grounds the work in the ticket and the related Confluence and Jira knowledge you've connected.
- Is this an alternative to GitHub Copilot for Azure DevOps teams?
- It is a different tool for a different starting point: WorkspaceGPT is built around the ticket and your org's documentation rather than the open file. It can also use your GitHub Copilot plan as its model in Local mode.
- Does it open pull requests?
- Create PR commits only what the agent changed to a fresh branch, pushes it, and opens your host's new-pull-request page with the run's report filled in.
- Where does my Azure DevOps data go?
- Work items are synced to your machine and indexed there. The index never leaves it, and WorkspaceGPT retains nothing server-side.