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.