ADO Lens 0.11.0

ADO Lens for Azure DevOps: work items, boards, wiki, Git and TFVC served to Claude (Desktop and Code) over MCP.

Install

Download ado-lens-0.11.0.zip, unzip it and run in a regular (non-admin) PowerShell:

powershell -ExecutionPolicy Bypass -File .\ado-lens\install.ps1

Self-contained build - no .NET required on the target machine. Already installed? Run install.ps1 from this
package: settings, PATs and the local metadata are kept. The SHA-256 of the package is in ado-lens-0.11.0.zip.sha256.

Changes

Settings in a window.

• Start menu ADO Lens - settings (or adolens setup --window) opens a window instead of a menu in a terminal:
  • General: who uses it (mode), tools at start, language, download folder;
  • Connections: the list with their PATs, add one (address or link, PAT, default project - checked before anything
    is saved), remove, make default, project, team, project with the code, required label languages;
  • Environments: per connection, the map in flow order as a table (repository, branch or release stage, name),
    "Find stages and branches", reorder, save for you or for the whole team (wiki page "ADO Lens");
  • Status: the same check as adolens status;
  • "Open in a terminal" starts the menu of adolens setup, which stays as it was.
• The program is now built for Windows with Windows Forms (net9.0-windows); the program file is larger.

Released under the MIT License. Not affiliated with or endorsed by Microsoft.

ADO Lens 0.10.1

ADO Lens for Azure DevOps: work items, boards, wiki, Git and TFVC served to Claude (Desktop and Code) over MCP.

Install

Download ado-lens-0.10.1.zip, unzip it and run in a regular (non-admin) PowerShell:

powershell -ExecutionPolicy Bypass -File .\ado-lens\install.ps1

Self-contained build - no .NET required on the target machine. Already installed? Run install.ps1 from this
package: settings, PATs and the local metadata are kept. The SHA-256 of the package is in ado-lens-0.10.1.zip.sha256.

Changes

• A Polish installation shows Polish texts people read: the descriptions of the skills in Claude Code and in the ZIPs
  for Claude Desktop (from description.pl.txt next to each skill; the instructions for Claude stay in English), and
  the titles and descriptions of the prompts. adolens skills writes both - the installer and install.ps1 call it,
  and changing the language in the settings menu writes them again.
• ado_create / ado_update with a parent: a parent of a lower or the same backlog level (a requirement under a task,
  a task under a task) gets a note "unusual parent" - the link is still made, but it is usually a mistaken id.
• A test for the warning about a required label language without a label file.

Released under the MIT License. Not affiliated with or endorsed by Microsoft.

ADO Lens 0.10.0

ADO Lens for Azure DevOps: work items, boards, wiki, Git and TFVC served to Claude (Desktop and Code) over MCP.

Install

Download ado-lens-0.10.0.zip, unzip it and run in a regular (non-admin) PowerShell:

powershell -ExecutionPolicy Bypass -File .\ado-lens\install.ps1

Self-contained build - no .NET required on the target machine. Already installed? Run install.ps1 from this
package: settings, PATs and the local metadata are kept. The SHA-256 of the package is in ado-lens-0.10.0.zip.sha256.

Changes

Environments per repository, code in another project, a tidier installer page.

• Environment map keys Repository:branch ("ERP:staging=UAT (sbx03)"): a repository with keys of its own uses only
  those, so the same branch name can mean different environments - or none - in different repositories. ado_trace
  no longer reports "NOT merged yet" for branches a repository does not use. Plain keys (staging=UAT) work as before.
• Detecting the flow (installer, adolens setup, ado_settings): with several repositories each branch is named with
  its repository; repositories without a commit in the last half year and work branches (000000_TestBranch,
  123456_LoginForm_…) are left out.
• adolens config --code-project <name> / ado_settings codeProject=<name>: the project with the code, pull requests
  and pipelines when it is not the work items' one; ado_file, the code part of ado_search, ado_pr,
  ado_pr_update, ado_pipeline, ado_changes and ado_label look there.
• Installer, environments page: a larger wizard, as many rows as fit (the rest is named, to set later in the settings),
  the repository shown next to each branch, and one drop-down for where to save instead of three options that did not
  fit.

Released under the MIT License. Not affiliated with or endorsed by Microsoft.

ADO Lens 0.9.5

ADO Lens for Azure DevOps: work items, boards, wiki, Git and TFVC served to Claude (Desktop and Code) over MCP.

Install

Download ado-lens-0.9.5.zip, unzip it and run in a regular (non-admin) PowerShell:

powershell -ExecutionPolicy Bypass -File .\ado-lens\install.ps1

Self-contained build - no .NET required on the target machine. Already installed? Run install.ps1 from this
package: settings, PATs and the local metadata are kept. The SHA-256 of the package is in ado-lens-0.9.5.zip.sha256.

Changes

• ado_file by name works without Code Search (not installed or failing): the file lists of the TFVC Metadata
  folders of the branches (also in another project of the organization) and of the Git repositories are searched, and
  the matches come as full paths ($/…/Main/…, $/…/Release/…) to call again with. Nothing found: an example full path.
  ADOLENS_NO_CODE_SEARCH=1 tries this way on purpose.
• ado_attachments file=all: every image of the item (pasted into its text or comments, or attached) in one answer;
  file="1;3" several files by number (e.g. three screenshots all called image.png).

Released under the MIT License. Not affiliated with or endorsed by Microsoft.

ADO Lens 0.9.4

ADO Lens for Azure DevOps: work items, boards, wiki, Git and TFVC served to Claude (Desktop and Code) over MCP.

Install

Download ado-lens-0.9.4.zip, unzip it and run in a regular (non-admin) PowerShell:

powershell -ExecutionPolicy Bypass -File .\ado-lens\install.ps1

Self-contained build - no .NET required on the target machine. Already installed? Run install.ps1 from this
package: settings, PATs and the local metadata are kept. The SHA-256 of the package is in ado-lens-0.9.4.zip.sha256.

Changes

• ado_trace: a branch earlier in the environment flow than the one a change was merged into is not reported as
  "NOT merged yet" (a change merged straight into master of a library repository says nothing about its dev branch).
• Before "not yet", one question per source branch: completed PRs from the same source branch into that branch that
  are not linked to the item ("merged by PRs not linked to the item: PR 31002 (2021-09-01, staging <- 243623_…)").

Released under the MIT License. Not affiliated with or endorsed by Microsoft.

ADO Lens 0.9.3

ADO Lens for Azure DevOps: work items, boards, wiki, Git and TFVC served to Claude (Desktop and Code) over MCP.

Install

Download ado-lens-0.9.3.zip, unzip it and run in a regular (non-admin) PowerShell:

powershell -ExecutionPolicy Bypass -File .\ado-lens\install.ps1

Self-contained build - no .NET required on the target machine. Already installed? Run install.ps1 from this
package: settings, PATs and the local metadata are kept. The SHA-256 of the package is in ado-lens-0.9.3.zip.sha256.

Changes

• ado_trace: "is the change in this branch / deployment" asks the history of the target around the day the change
  was merged (one cheap call) instead of a diff between the commits, which took 20-30 seconds each in a large
  repository; the diff stays as the fallback when the date is unknown.
• Code moves forward through the environments of the map (dev -> staging -> master): a change merged into a later
  one is not looked for in an earlier one.
• "not yet" leaves out a change whose work is already there through another PR from the same source branch (the same
  work merged into each environment by its own PR).

Released under the MIT License. Not affiliated with or endorsed by Microsoft.

ADO Lens 0.9.2

ADO Lens for Azure DevOps: work items, boards, wiki, Git and TFVC served to Claude (Desktop and Code) over MCP.

Install

Download ado-lens-0.9.2.zip, unzip it and run in a regular (non-admin) PowerShell:

powershell -ExecutionPolicy Bypass -File .\ado-lens\install.ps1

Self-contained build - no .NET required on the target machine. Already installed? Run install.ps1 from this
package: settings, PATs and the local metadata are kept. The SHA-256 of the package is in ado-lens-0.9.2.zip.sha256.

Changes

Fixes and additions from testing 0.9 on a real project.

• ado_create: fields with a default of the process (Value Area, Severity, Triage…) and fields Azure DevOps fills
  itself (Area ID, Iteration ID, State, Work Item Type) are no longer asked for - the rule check of 0.9.0 took the
  system rules of the process for fields to give. A rule "required while State was empty" is checked as "on create"
  instead of ending in a 400 from Azure DevOps.
• ado_fields type=<type>: fields required by rules are named as REQUIRED, and fields that are required but filled by
  Azure DevOps say so.
• ado_trace much faster on items with many pull requests: the files of a PR come from its last iteration instead of
  a diff of its merge commit, merge commits of linked PRs are not read twice, a completed PR into a branch answers
  "is it there" without asking, and only the newest change of each source -> target pair is checked. Reading the
  changes gets half of the time, so builds and deployments are still read.
• ado_trace with no code linked looks for configuration words in every text field of the item and its tasks.
• ado_sprint: a "Done" state that the process puts in the Resolved category counts as done.
• ado_work_item: names of up to 40 linked releases (was 10); a release deleted by retention or not readable says so.
• Numbered lists keep their numbering (<ol start="3">).
• ado_pr_update: update adds reviewers, requiredReviewers (on create and update) makes them required,
  autocomplete (merge strategy, delete source branch, text = merge message) and cancel_autocomplete.
• A parameter a tool does not have is reported with the tool's parameters instead of being dropped (a conversation
  started before an update still sees the old tool descriptions).

Released under the MIT License. Not affiliated with or endorsed by Microsoft.

ADO Lens 0.9.1

ADO Lens for Azure DevOps: work items, boards, wiki, Git and TFVC served to Claude (Desktop and Code) over MCP.

Install

Download ado-lens-0.9.1.zip, unzip it and run in a regular (non-admin) PowerShell:

powershell -ExecutionPolicy Bypass -File .\ado-lens\install.ps1

Self-contained build - no .NET required on the target machine. Already installed? Run install.ps1 from this
package: settings, PATs and the local metadata are kept. The SHA-256 of the package is in ado-lens-0.9.1.zip.sha256.

Changes

• ado_trace always answers: on an item with many links (pull requests, commits, builds, releases) the slow parts
  stop after 40 seconds and an INCOMPLETE section says what was not checked, instead of the client giving up with a
  timeout. At most 8 branch and deployment checks run at the same time (more were throttled), and the TFVC branch of
  changesets is asked once per folder, all at once.
• adolens trace <id> --timing: how long each part took, to find what is slow on a given project.

Released under the MIT License. Not affiliated with or endorsed by Microsoft.

ADO Lens 0.9.0

ADO Lens for Azure DevOps: work items, boards, wiki, Git and TFVC served to Claude (Desktop and Code) over MCP.

Install

Download ado-lens-0.9.0.zip, unzip it and run in a regular (non-admin) PowerShell:

powershell -ExecutionPolicy Bypass -File .\ado-lens\install.ps1

Self-contained build - no .NET required on the target machine. Already installed? Run install.ps1 from this
package: settings, PATs and the local metadata are kept. The SHA-256 of the package is in ado-lens-0.9.0.zip.sha256.

Changes

Improvements from testing on a real project.

• ado_pr_update action=update: change the title or description of a pull request and link work items to it after it
  was created (branch policies often require a linked work item), instead of abandoning it and opening a new one.
• People are found by name, e-mail or a display name with a company suffix ("Anna Nowak (Contoso)"); when the identity
  search finds nobody, the people picker of the web is asked too.
• Fields required by rules of an inherited process ("required when moving to Resolved") are checked before writing
  and listed in ado_fields type=<type>, instead of a 400 from Azure DevOps.
• ado_sprint detail=full: who has what - open items, tasks and hours left per person.
• ado_file on a table, table extension, view or map: a skeleton of properties, fields (type, label, mandatory),
  indexes, relations and field groups instead of only the methods.
• ado_work_item: links to release stages name the release, the stage, its status and date; commit links give the
  full commit id.
• ado_trace: with no code linked, an item that speaks of configuration (ER, parameters, setup…) is reported as a
  probable change in the system's setup that can be checked only there.

Released under the MIT License. Not affiliated with or endorsed by Microsoft.

ADO Lens 0.8.2

ADO Lens for Azure DevOps: work items, boards, wiki, Git and TFVC served to Claude (Desktop and Code) over MCP.

Install

Download ado-lens-0.8.2.zip, unzip it and run in a regular (non-admin) PowerShell:

powershell -ExecutionPolicy Bypass -File .\ado-lens\install.ps1

Self-contained build - no .NET required on the target machine. Already installed? Run install.ps1 from this
package: settings, PATs and the local metadata are kept. The SHA-256 of the package is in ado-lens-0.8.2.zip.sha256.

Changes

Fewer false alarms in sprints and checks.

• ado_sprint: no "fits, N h spare" when most open tasks have no Remaining Work - it says how many have it instead;
  the attention count says how many are items and how many their tasks.
• "no acceptance criteria" only for types that have the field (a process that keeps criteria in the description is not
  flagged, in ado_sprint and ado_trace alike); "no estimate" and "no acceptance criteria" only for items not
  started or in the first state of the work, not for items in test or waiting for production.
• ado_create / ado_update: for a type without a criteria field the criteria are part of the description, so the
  length hint allows twice as many words and no "no acceptance criteria given" note.

Released under the MIT License. Not affiliated with or endorsed by Microsoft.