The stuck PR
A developer asks why PR 412 has not merged. Memtro reads the reviewers' votes, the unresolved comment threads with file and line, and the failed build on the branch, then says who is waiting on whom.
Work items, pull requests and builds from Azure DevOps, remembered alongside the rest.
Connect Azure DevOps Services with an organisation-scoped personal access token and Memtro lists projects and repositories, reads pull requests with votes and comment threads, finds work items by filter or WIQL, and sees builds. The hourly sync writes each changed work item into memory. When you ask, and once an administrator has granted the action by name, it can create, update, comment on or delete work items, open, vote on, comment on and complete pull requests, and run pipelines or cancel builds. Completing a pull request merges it for good, and a pipeline run spends pipeline minutes.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Azure DevOps tool, reads what it needs, and answers with the source cited.
These tools change something in Azure DevOps. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.
Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Azure DevOps, choosing the same kinds; the tab shows Azure DevOps's own steps. Each event can start a job, with the event as its input. Azure DevOps sends a secret with every delivery, and one without it is refused.
Events and webhooksOnce Azure DevOps is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
Which pull requests into main are waiting for a reviewer vote?
What did reviewers say on PR 412 in the web-platform repo?
Show me the open bugs in Sprint 42 assigned to Priya Sharma
Did any builds fail on main today, and which pipeline?
Add a comment to work item 8831 saying the fix shipped in release 3.14
A developer asks why PR 412 has not merged. Memtro reads the reviewers' votes, the unresolved comment threads with file and line, and the failed build on the branch, then says who is waiting on whom.
Priya Sharma at Globex ships the login fix and asks Memtro to resolve bug 8831 and note the release. Memtro sets the work item's state to Resolved and comments that the fix went out in release 3.14 under her token's name, and Azure DevOps notifies the item's followers.
The teams that lean on Azure DevOps most, a question each of them asks, and what they connect beside it.
A record in Azure DevOps is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
In Azure DevOps open User settings (top right) → Personal access tokens → New Token, scoped to this organisation with an expiry. Global PATs are being retired
Tick Project and Team (Read), Code (Read), Build (Read) and Work Items (Read & write, or Read if you want no work item action). For the pull request actions use Code (Read & write) and User Profile (Read), and Build (Read & execute) to run pipelines
In Memtro open Connections → Azure DevOps, paste the Personal access token with the Organization name (dev.azure.com/acme → acme), and optionally set a Default project to scope questions and the sync
Ask what is assigned to you this sprint
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Azure DevOps tools are the same everywhere.
Only when you ask, and only what it has been granted: add a comment to a work item's discussion; create a work item (bug, task, user story...) with title, description, assignee, priority, area, iteration and tags; change a work item's title, state, assignee, priority, area, iteration, tags or description; delete a work item to the recycle bin; open a pull request from one branch into another; approve, reject or otherwise vote on a pull request as the token's owner; start a comment thread on a pull request, on the whole change or a line of a file; retitle, redescribe, abandon or reactivate a pull request; complete (merge) a pull request; run a pipeline on a named branch; cancel a running build. Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded. An hourly sync anchors recently changed Azure DevOps records into memory as entities.
Organization and personal access token. In Azure DevOps open User settings (top right) → Personal access tokens → New Token, scoped to this organisation with an expiry. Global PATs are being retired.
Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Azure DevOps, choosing the same kinds; the tab shows Azure DevOps's own steps. A job set to start "When an event arrives" then runs once for each matching event, with the event as its input. The run treats the event as outside data, never as instructions, and anything the run remembers is kept as unverified.
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.
Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.
7-day free trial · card on file, nothing charged until it ends · cancel any time