v0.3.4 — Concrete gaps and one finding per place

Azure DevOps PR Review for OpenCode — 0.3.4

This release changes what reviewers report. Concrete gaps the change leaves,
such as an untested change or a document that now contradicts the code, become
findings, and a mistake repeated in several places is reported at each place
that needs its own fix. Settings, commands, comment previews, adjustments and
publication work as in 0.3.3, and the tested host stays OpenCode 2.2.4.

What changed

• Concrete gaps are findings. Reviewers file, usually as low: a changed or
  added behavior that no test would catch where the project already tests
  comparable code (naming the missing case and the tests it belongs with), a
  test that cannot fail or checks the wrong thing, a comment, document,
  example, schema or configuration that now contradicts the code, and
  duplicated, dead, misleading or inconsistent code the change introduces.
  These used to appear only as advice in the report. Design trade-offs and
  general advice without a specific defect or location still go to the report
  and the summary's improvement suggestions.
• One finding per place that needs its own fix. When the same mistake is
  written separately in several functions, files or routes, for example three
  routes that each build a URL from the internal request origin, each place is
  its own finding at its own lines, with the sibling places in its evidence.
  Reviewers check their other assigned files for the same mistake. One wrong
  piece of shared code is still one finding at that code.
• Identical copies count once per reviewer. A template, example, document
  or vendored file repeated with identical content in several directories is
  one place among one reviewer's assigned files: one finding at one copy that
  lists the other copies. A large PR is reviewed in shards cut by path, so
  copies in different shards can each produce a finding. Files whose content
  differs, such as each package's own manifest, stay separate places.

Publication is unchanged: inline comments go to high and medium findings, and
low findings stay in the summary index. A review therefore shows more low
findings in the summary and, for a repeated high or medium mistake, one inline
comment at each place. /pr-review, /pr-deep and /pr-quick share these
rules.

Measured effect

Before release, the new instructions were compared with 0.3.3 on the public
ReviewBench test set, served to
OpenCode 2.2.4 through a local fixture of the Azure DevOps API and scored with
the benchmark's matcher and classifier rubric by Claude Opus subagents rather
than its official judge. The comparison shows the direction of the change, not
a leaderboard result:

• With /pr-deep and gpt-6.1-sol, reviews matched more of the high- and
  medium-severity reference issues, including high ones. A mistake repeated in
  several routes was reported, and matched, at each route.
• Reviews produce more findings, mostly low, which stay in the summary index,
  and take somewhat longer; the share of findings judged valid stayed about the
  same.
• With /pr-review and gpt-6-luna, reviews matched slightly more, within the
  variation between runs.

The
validation record
describes the method and its limits.

Installation

opencode plugin add opencode-azure-devops-pr-review@0.3.4

Alternatively, install the same release from Git:

opencode plugin add 'github:WTLAIB/opencode-azure-devops-pr-review-v2#v0.3.4'

Add only one of them. Follow the
quickstart
for a private PAT file, /pr-setup, a service restart and the first review.

Upgrading AZPR

For an entry that opencode plugin add created, add 0.3.4 and remove the
previous version only when the download succeeded. Replace PREVIOUS_VERSION
with the version in your plugins entry, such as 0.3.3:

opencode plugin add opencode-azure-devops-pr-review@0.3.4 &&
  opencode plugin remove opencode-azure-devops-pr-review@PREVIOUS_VERSION

Run them when no AZPR command is running: OpenCode 2.2.4 switches the running
service to 0.3.4 within seconds, without a restart, and
opencode plugin list should then show a single azpr row with 0.3.4. Running
only the first command leaves the previous version running. For an entry with
options, change only its package value; the OpenCode service then downloads
0.3.4 with its own network settings. See
upgrading
for the details. External settings, the PAT file and review records remain in
place, and this release adds no settings or required migration.

For a source installation, extract the new archive and run its installer with
--replace to retain settings:

sh install.sh --config-dir /absolute/path/to/v2-opencode-config --replace

Compatibility and validation

The tested target is OpenCode CLI 2.2.4 (V2 plugin API), Node.js
22.23.3, Ubuntu 22.04.5 under WSL2, and Azure DevOps Services REST API
7.1. OpenCode 1.x and Azure DevOps Server are not supported; other operating
systems remain unvalidated.

The runtime code is that of 0.3.3; only the reviewer instructions changed. The
validation record
lists the offline and real-host checks with fake services and the comparison
above. Live runs with openai/gpt-6-luna on the 1-file test PR, in a service on
OpenCode 2.2.4, completed without publishing comments: /pr-review confirmed
the PR's three known defects, and /pr-quick reported the same three.

The npm package, Git package and source archive contain the same runtime, with
no npm dependencies or install scripts; the source archive also contains the
documentation, installers and settings example. The release source artifact is
opencode-azure-devops-pr-review-v2-0.3.4.tar.gz, with checksums in SHA256SUMS.

v0.3.3 — Tested with OpenCode 2.2.4, used-up limits stop at once

Azure DevOps PR Review for OpenCode — 0.3.3

This release moves the tested host to OpenCode 2.2.4, stops at once when a
model's usage or spend limit is used up, and shows the OpenCode version in
/pr-check instead of a notice on every receipt. Reviews, comment previews,
adjustments and publication work as in 0.3.2.

What changed

• Tested with OpenCode 2.2.4. AZPR is validated with OpenCode CLI 2.2.4
  instead of 2.1.4. The runtime needed no change: with the same fake provider,
  a review sends byte-identical model requests on both hosts. OpenCode 2.2.x
  offers new tools to every agent, such as image generation when a provider has
  an image model; private reviewers still see only AZPR's tools and the native
  read tools.
• OpenCode version in /pr-check. A new OpenCode row names the host
  version and is a WARNING when it is not the tested one; reviews still run,
  and AZPR still refuses to start if OpenCode lacks something it needs.
  Receipts no longer end with a host notice after every OpenCode update.
• Used-up limits stop at once. When a model's usage or spend limit is used
  up, AZPR refuses OpenCode's retries, starts no new session, and the receipt
  names the limit. Besides the provider quota and the OpenCode free-model
  limit, this covers the ChatGPT and OpenCode Go usage limits that OpenCode
  2.2.3 reports and OpenCode's spend limits; a used-up ChatGPT limit was
  previously retried as a rate limit.
• Fewer host events. AZPR subscribes only to the session events that show
  a review progressing; OpenCode 2.2.0 and later deliver no others.
• Proxies. OpenCode 2.2.4 always adds 127.0.0.1, localhost and ::1
  to NO_PROXY, and Bun honours NO_PROXY even for azure.proxy. Azure
  DevOps requests are unaffected; the
  company-network guide
  now says to keep dev.azure.com out of NO_PROXY when it must use the
  proxy.

Upgrading OpenCode

OpenCode 2.2.0 and later migrate OpenCode's database when they first start,
and the migration cannot be undone. Stop the service and back up the database
before installing 2.2.4:

opencode service stop
mkdir -p ~/opencode-db-backup && cp -p ~/.local/share/opencode/opencode.db* ~/opencode-db-backup/
npm install -g @opencode/cli@2.2.4
opencode service start

Use sudo for the global install if your npm prefix needs it. To go back,
stop the service, reinstall the previous OpenCode and restore the backup.
AZPR 0.3.3 also runs on OpenCode 2.1.4 (/pr-check then shows the OpenCode
WARNING row), so the two upgrades can happen in either order.

Installation

opencode plugin add opencode-azure-devops-pr-review@0.3.3

Alternatively, install the same release from Git:

opencode plugin add 'github:WTLAIB/opencode-azure-devops-pr-review-v2#v0.3.3'

Add only one of them. Follow the
quickstart
for a private PAT file, /pr-setup, a service restart and the first review.

Upgrading AZPR

For an entry that opencode plugin add created, add 0.3.3 and remove the
previous version only when the download succeeded. Replace PREVIOUS_VERSION
with the version in your plugins entry, such as 0.3.2:

opencode plugin add opencode-azure-devops-pr-review@0.3.3 &&
  opencode plugin remove opencode-azure-devops-pr-review@PREVIOUS_VERSION

Run them when no AZPR command is running: OpenCode 2.1.4 and 2.2.4 switch the
running service to 0.3.3 within seconds, without a restart, and
opencode plugin list should then show a single azpr row with 0.3.3. Running
only the first command leaves the previous version running. For an entry with
options, change only its package value; the OpenCode service then downloads
0.3.3 with its own network settings. See
upgrading
for the details. External settings, the PAT file and review records remain in
place, and this release adds no settings or required migration.

For a source installation, extract the new archive and run its installer with
--replace to retain settings:

sh install.sh --config-dir /absolute/path/to/v2-opencode-config --replace

Compatibility and validation

The tested target is OpenCode CLI 2.2.4 (V2 plugin API), Node.js
22.23.3, Ubuntu 22.04.5 under WSL2, and Azure DevOps Services REST API
7.1. OpenCode 1.x and Azure DevOps Server are not supported; other operating
systems remain unvalidated.

The validation record
describes the comparison of OpenCode 2.1.4 and 2.2.4 and the release checks
with fake services. A review-only live run of the candidate with
openai/gpt-6-luna on the 1-file test PR, in a service still on OpenCode
2.1.4, completed and confirmed the PR's three known defects.

The npm package, Git package and source archive contain the same runtime, with
no npm dependencies or install scripts; the source archive also contains the
documentation, installers and settings example. The release source artifact is
opencode-azure-devops-pr-review-v2-0.3.3.tar.gz, with checksums in SHA256SUMS.

v0.3.2 — Results first, precise receipts, smaller npm package

Azure DevOps PR Review for OpenCode — 0.3.2

This release shows AZPR's actual Azure DevOps output at the top of the README,
states the COMPLETE status more precisely in receipts, and slims the npm
package to the runtime. Reviews, comment previews, adjustments and publication
work as in 0.3.1.

What changed

• See the output first. The README opens with an actual inline comment on
  a dedicated test PR, shown with its code context, and the complete PR summary
  from the same review. The first-review steps follow, then the 15-second
  recording of adjusting findings and publishing. The
  demo
  records the capture run and its editing, and lists the pictured comments as
  text.
• Precise status. COMPLETE in a receipt now means that no source-commit
  change was detected. When the final version recheck itself fails, the review
  stays COMPLETE and its report lists a warning; publication still rechecks
  that the PR is active and its source commit is unchanged before posting.
• Smaller npm package. The package holds the runtime (server.js and
  src/), the README, the changelog and the license: 32 files and about 170 KB
  instead of 76 files and 1.35 MB. Documentation, media, installers and the
  settings example and schema remain in the repository and the source archive,
  and npmjs.com shows the README's links and images from GitHub.
• Documentation. The README and the architecture guide list the commands
  that answer directly instead of starting a background run, and the README
  and the commenting guide state that repeating the saved adjustments plans
  nothing.

Installation

opencode plugin add opencode-azure-devops-pr-review@0.3.2

Alternatively, install the same release from Git:

opencode plugin add 'github:WTLAIB/opencode-azure-devops-pr-review-v2#v0.3.2'

Add only one of them. Follow the
quickstart
for a private PAT file, /pr-setup, a service restart and the first review.

Upgrading

For an entry that opencode plugin add created, add 0.3.2 and remove the
previous version only when the download succeeded. Replace PREVIOUS_VERSION
with the version in your plugins entry, such as 0.3.1:

opencode plugin add opencode-azure-devops-pr-review@0.3.2 &&
  opencode plugin remove opencode-azure-devops-pr-review@PREVIOUS_VERSION

Run them when no AZPR command is running: OpenCode 2.1.4 switches the running
service to 0.3.2 within seconds, without a restart, and opencode plugin list
should then show a single azpr row with 0.3.2. Running only the first command
leaves the previous version running. For an entry with options, change only
its package value; the OpenCode service then downloads 0.3.2 with its own
network settings. See
upgrading
for the details. External settings, the PAT file and review records remain in
place, and this release adds no settings or required migration.

For a source installation, extract the new archive and run its installer with
--replace to retain settings:

sh install.sh --config-dir /absolute/path/to/v2-opencode-config --replace

Compatibility and validation

The tested target remains OpenCode CLI 2.1.4 (V2 plugin API), Node.js
22.23.3, Ubuntu 22.04.5 under WSL2, and Azure DevOps Services REST API
7.1. OpenCode 1.x and Azure DevOps Server are not supported; other operating
systems remain unvalidated.

The validation record
describes the release checks with fake services. The runtime changes only the
receipt's status sentence, so this release needed no new live model run; the
README screenshots come from a live run with 0.3.1 on 2026-10-29.

The npm package, Git package and source archive contain the same runtime, with
no npm dependencies or install scripts; the source archive also contains the
documentation, installers and settings example. The release source artifact is
opencode-azure-devops-pr-review-v2-0.3.2.tar.gz, with checksums in SHA256SUMS.

v0.3.1 — Easier installation, setup and upgrades

Azure DevOps PR Review for OpenCode — 0.3.1

This release makes installation, first-run setup and upgrades easier to
follow on OpenCode 2.1.4, and lets /pr-check show which AZPR is running.
Reviews, comment previews, adjustments and publication work as in 0.3.0.

What changed

• Shorter setup. /pr-setup --organization YOUR_ORGANIZATION --model PROVIDER/MODEL uses the PAT file the quickstart creates,
  ${XDG_CONFIG_HOME:-~/.config}/azpr/pat, and --organization also accepts
  your PR's URL. With --replace, setup keeps the PAT file already set unless
  you name another one. The receipt names the organization and the PAT file.
• See what runs. /pr-check has an AZPR row that names the running
  package and version. When another AZPR entry is configured but not running,
  for example after opencode plugin add with a new version, which leaves the
  old one running, the row is a WARNING. User names, passwords and query
  strings in package specifications are masked.
• Restart only for settings. On OpenCode 2.1.4, adding or changing the
  plugin entry loads it into the running service within seconds. Saved
  settings still need a restart, and AZPR's messages now name
  opencode service restart.
• Documentation. The quickstart runs the terminal steps first. The README
  has an Upgrading section. The team guide explains proxies and certificates
  for package downloads, model providers and Azure DevOps separately, and the
  Azure DevOps guide names the actual settings locations.

Installation

opencode plugin add opencode-azure-devops-pr-review@0.3.1

Alternatively, install the same release from Git:

opencode plugin add 'github:WTLAIB/opencode-azure-devops-pr-review-v2#v0.3.1'

Add only one of them. Follow the
quickstart
for a private PAT file, /pr-setup, a service restart and the first review.

Upgrading

For an entry that opencode plugin add created, add 0.3.1 and remove the
previous version only when the download succeeded. Replace PREVIOUS_VERSION
with the version in your plugins entry, such as 0.3.0:

opencode plugin add opencode-azure-devops-pr-review@0.3.1 &&
  opencode plugin remove opencode-azure-devops-pr-review@PREVIOUS_VERSION

Run them when no AZPR command is running: OpenCode 2.1.4 switches the running
service to 0.3.1 within seconds, without a restart, and opencode plugin list
should then show a single azpr row with 0.3.1. Running only the first command
leaves the previous version running. For an entry with options, change only
its package value; the OpenCode service then downloads 0.3.1 with its own
network settings. See
upgrading
for the details. External settings, the PAT file and review records remain in
place, and this release adds no settings or required migration.

For a source installation, extract the new archive and run its installer with
--replace to retain settings:

sh install.sh --config-dir /absolute/path/to/v2-opencode-config --replace

Compatibility and validation

The tested target remains OpenCode CLI 2.1.4 (V2 plugin API), Node.js
22.23.3, Ubuntu 22.04.5 under WSL2, and Azure DevOps Services REST API
7.1. OpenCode 1.x and Azure DevOps Server are not supported; other operating
systems remain unvalidated.

The validation record
describes the installation and upgrade behaviour measured on OpenCode 2.1.4
and the release checks with fake services. Setup and the AZPR row make no model
or Azure request, and reviews and publication are unchanged, so this release
needed no live model run.

The npm package, Git package and source archive contain the same runtime, with
no npm dependencies or install scripts. The release source artifact is
opencode-azure-devops-pr-review-v2-0.3.1.tar.gz, with checksums in SHA256SUMS.

v0.3.0 — Adjust findings before publishing

Azure DevOps PR Review for OpenCode — 0.3.0

AI reviews. You decide what gets posted. This release lets you exclude findings
or change their severity after reading a comment preview. AZPR prepares a new
preview without rerunning the review, while keeping the original findings and
report intact.

Try it after a preview

Use your review ID and finding IDs from its report:

/pr-comment <review-id> --exclude F-1 --severity F-2=low

F-1 is excluded from the new preview; F-2 appears as low in the summary, with no
new inline comment. Comment planning uses a model again, so other wording may
change. Read the whole new preview, then publish from the same conversation:

/pr-comment <review-id> --publish

What changed

• Choose the findings and severity. --exclude and --severity each
  replace their own saved list; none empties that list. For example,
  --exclude F-1 followed by --exclude F-2 excludes only F-2. Name both to
  keep both out. --reset clears both lists and plans again. A changed
  severity changes publication, not the evidence or verification of a finding.
  Excluding every finding plans and posts nothing (NOTHING_TO_POST).
• Reopen the saved preview. /pr-comment [review-id] --show displays it
  without a model or Azure DevOps request. It includes the saved adjustments.
• Read the new preview before publishing. An adjusted review, including
  one reset since, needs a saved preview planned after its latest adjustment.
  Adjustments are saved together with dropping the earlier preview; a failed
  save changes nothing. A new preview whose save fails is dropped. After a
  stop or restart during planning, prepare a new preview before publishing.
  Once publication starts, the review cannot be adjusted or planned again;
  --publish retries the same saved content.
• Excluded IDs stay out of new comments. The planner receives the adjusted
  findings, and the assembled preview is checked too. When a retained
  finding's summary names an excluded ID, publication is held until you
  exclude that finding as well or restore the other. References without the
  ID cannot be detected by this check.
• Earlier PR comments keep their text. AZPR still skips comments it already
  posted and never edits them. An adjusted review's receipt names items whose
  actual text differs from the preview, including comments that appear only
  when AZPR reads the threads back. It also counts other AZPR comments on the
  PR, where an excluded finding may still be visible.
• The README opens with a real OpenCode 2.1.4 recording of adjusting findings
  and publishing, and the README and quickstart show the adjustment workflow.
  The npm package includes the code of conduct. CI actions are pinned by commit
  and updated with Dependabot.

The options work with review, deep and quick results. Quick findings remain
not independently verified. Without adjustments, comment planning and
publication retain their existing behavior. See the
commenting guide
for the complete rules.

Installation

opencode plugin add opencode-azure-devops-pr-review@0.3.0

Alternatively, install the same release from Git:

opencode plugin add 'github:WTLAIB/opencode-azure-devops-pr-review-v2#v0.3.0'

Add only one of them. Follow the
quickstart
for a private PAT file, /pr-setup, a service restart and the first review.

Upgrading

For a native installation, edit its existing entry in the OpenCode
configuration's plugins list:

• For npm, change the package specification to
  opencode-azure-devops-pr-review@0.3.0.
• For Git, change the tag suffix to #v0.3.0.

If the entry is an object, change only package; preserve options.settingsFile
and any other options. Keep one AZPR entry and restart the OpenCode service.
External settings, the PAT file and review records remain in place; a working
configuration needs no new /pr-setup. Exact version pins are not advanced by
opencode plugin update. This release adds no settings or required migration.

For a source installation, extract the new archive and run its installer with
--replace to retain settings:

sh install.sh --config-dir /absolute/path/to/v2-opencode-config --replace

Automatic comments remain opt-in through afterReview or a review command
flag. Use /pr-review <PR URL> --preview when you want to inspect and adjust
findings before publication.

Compatibility and validation

The tested target remains OpenCode CLI 2.1.4 (V2 plugin API), Node.js
22.23.3, Ubuntu 22.04.5 under WSL2, and Azure DevOps Services REST API
7.1. OpenCode 1.x and Azure DevOps Server are not supported; other operating
systems remain unvalidated.

The validation record
separates release checks with fake services from live runs. The earlier live
adjustment runs on 1-file and 316-file Azure DevOps test PRs preceded the final
persistence and read-back fixes; a recorded live run on the 1-file test PR used
this release's runtime. None of them establish a general review accuracy score.

The npm package, Git package and source archive contain the same runtime, with
no npm dependencies or install scripts. The release source artifact is
opencode-azure-devops-pr-review-v2-0.3.0.tar.gz, with checksums in SHA256SUMS.
The README's 15-second recording of adjusting findings and publishing comes
from that live run. The earlier walkthrough of the review, preview and
publication workflow remains attached to
v0.2.0.
The demo guide
describes both recordings.

v0.2.3 — OpenCode 2.1.4 compatibility

Azure DevOps PR Review for OpenCode — 0.2.3

This release moves the tested host to OpenCode CLI 2.1.4 and fixes three
behaviors that OpenCode 2.1.3 and later expose: how a refused proxy tunnel is
reported, how long a silent Azure DevOps call may wait, and how a refused
background summary affects a failed stage. Prompts, settings and installation
are unchanged.

What changed

• Proxy refusals are explained again. OpenCode 2.1.3 and later embed Bun
  1.4.4, which rejects a request with ERR_PROXY_TUNNEL when a proxy refuses
  the CONNECT tunnel, where Bun 1.4.2 returned the proxy's answer. AZPR treated
  the rejection as a network error and retried it. It now gives the earlier
  messages and retry rules: a missing proxy password is explained as HTTP 407
  without retries, a blocked destination names the proxy, and a refused tunnel
  never leaves a comment write uncertain.
• Azure DevOps calls keep their configured timeout. The runtime's fetch
  ended a request that received nothing for about six minutes by itself, while
  azure.callTimeoutSeconds accepts up to 1,800 seconds. AZPR now switches that
  limit off for its requests, so the configured timeout decides.
• Background compaction no longer splits a failed stage. With OpenCode's
  opt-in experimental.background_compaction, the host asks for a summary
  before a reviewer's context is full. AZPR refuses it as before, but the
  refusal also marked the stage as overflowing: a later permanent failure,
  such as an expired provider key, split the shard into new sessions that
  failed the same way, and a failed follow-up discarded the answer it
  followed. Overflow is now read from the failed turn itself.
• The README states that AZPR is an independent community project, not built
  by or affiliated with the OpenCode team.

Installation

opencode plugin add opencode-azure-devops-pr-review@0.2.3

Alternatively, install the same release from Git:

opencode plugin add 'github:WTLAIB/opencode-azure-devops-pr-review-v2#v0.2.3'

Add only one of them. Follow the
quickstart
for a private PAT file, /pr-setup, a service restart and the first review.

Upgrading

Upgrade OpenCode to 2.1.4 first if you can: the receipts of other versions add
a host notice, and those versions are not validated. Stop the OpenCode service
and copy its database before upgrading OpenCode, so that you can go back.

To update a native installation, edit its existing entry in the OpenCode
configuration's plugins list:

• For npm, change the package specification to
  opencode-azure-devops-pr-review@0.2.3.
• For Git, change the tag suffix to #v0.2.3.

If the entry is an object, change only package; preserve options.settingsFile
and any other options. Keep one AZPR entry and restart the OpenCode service.
External settings, the PAT file and review records remain in place; a working
configuration needs no new /pr-setup. Exact version pins are not advanced by
opencode plugin update.

For a source installation, extract the new archive and run its installer with
--replace to retain settings:

sh install.sh --config-dir /absolute/path/to/v2-opencode-config --replace

Coming from 0.1.0, see the
0.2.0 upgrade notes
for automatic comments, which remain disabled unless configured or requested.

Compatibility and release assets

The tested target is OpenCode CLI 2.1.4 (V2 plugin API), Node.js
22.23.3, Ubuntu 22.04.5 under WSL2, and Azure DevOps Services REST API
7.1. OpenCode 1.x and Azure DevOps Server are not supported; other operating
systems remain unvalidated. See the
validation record,
including live reviews on OpenCode 2.1.4.

The npm package comes from this tag and has no dependencies or install scripts.
Release assets are opencode-azure-devops-pr-review-v2-0.2.3.tar.gz and
SHA256SUMS; verify the source archive with sha256sum -c SHA256SUMS. The
existing demonstration remains attached to
v0.2.0,
with its original recording context documented in the
demo guide.

v0.2.2 — Documentation and discovery metadata

Azure DevOps PR Review for OpenCode — 0.2.2

This release brings the revised README and discovery metadata to npm. It
explains reviewing Azure DevOps PRs from a URL without maintaining a checkout,
model choices, separate verification, and comment previews. The runtime,
prompts, settings and installation behavior are unchanged from 0.2.1.

What changed

• The README and quickstart share one first-review path:
  /pr-review <PR URL> --preview, with quick review as a lighter alternative.
• Compatibility explicitly excludes OpenCode 1.x. Detailed reference sections
  have visible navigation targets, and archive limits link to their actual guide.
• Azure Code Search is described as searching indexed branches; AZPR searches
  the selected commit snapshot. Model and performance claims stay within the
  documented evidence.
• The package has an updated description and the opencode-v2 keyword.

Installation

opencode plugin add opencode-azure-devops-pr-review@0.2.2

Alternatively, install the same release from Git:

opencode plugin add 'github:WTLAIB/opencode-azure-devops-pr-review-v2#v0.2.2'

Add only one of them. Follow the
quickstart
for a private PAT file, /pr-setup, a service restart and the first review.

Upgrading

Existing 0.2.1 installations do not need an update to receive a runtime fix;
this is a documentation and metadata release. To update a native installation,
edit its existing entry in the OpenCode configuration's plugins list:

• For npm, change the package specification to
  opencode-azure-devops-pr-review@0.2.2.
• For Git, change the tag suffix to #v0.2.2.

If the entry is an object, change only package; preserve options.settingsFile
and any other options. Keep one AZPR entry and restart the OpenCode service.
External settings, the PAT file and review records remain in place; a working
configuration needs no new /pr-setup. Exact version pins are not advanced by
opencode plugin update.

For a source installation, extract the new archive and run its installer with
--replace to retain settings:

sh install.sh --config-dir /absolute/path/to/v2-opencode-config --replace

Coming from 0.1.0, see the
0.2.0 upgrade notes
for automatic comments, which remain disabled unless configured or requested.

Compatibility and release assets

The tested target remains OpenCode CLI 2.1.2 (V2 plugin API), Node.js
22.23.3, Ubuntu 22.04.5 under WSL2, and Azure DevOps Services REST API
7.1. OpenCode 1.x and Azure DevOps Server are not supported; other operating
systems remain unvalidated. See the
validation record.

The npm package comes from this tag and has no dependencies or install scripts.
Release assets are opencode-azure-devops-pr-review-v2-0.2.2.tar.gz and
SHA256SUMS; verify the source archive with sha256sum -c SHA256SUMS. The
existing demonstration remains attached to
v0.2.0,
with its original recording context documented in the
demo guide.

v0.2.1 — Install from npm

OpenCode Azure DevOps PR Review V2 — 0.2.1

AZPR is now available from the npm registry. This release changes packaging
and documentation only: the runtime, prompts and settings are the same as in
0.2.0.

Installation

opencode plugin add opencode-azure-devops-pr-review@0.2.1

The same release remains available as a versioned Git package, which needs
Git but not the npm registry:

opencode plugin add 'github:WTLAIB/opencode-azure-devops-pr-review-v2#v0.2.1'

Add only one of them. Follow the quickstart
for /pr-setup, a private PAT file, service restart and your first review.
The source archive includes install.sh for manual installation. Use one
installation method per OpenCode profile.

Upgrading

For a native installation, edit the existing AZPR entry in the OpenCode
configuration's plugins list:

• To stay on Git, change #v0.2.0 (or #v0.1.0) to #v0.2.1.
• To move to npm, replace the Git specification with
  opencode-azure-devops-pr-review@0.2.1.

If the entry is an object, change only its package value; preserve
options.settingsFile and other options. Keep one AZPR entry, then restart the
OpenCode service. npm and Git installations read the same external settings, so
the settings, PAT file and review records stay in place and a working
configuration needs no new /pr-setup. Exact versions stay pinned:
opencode plugin update leaves them unchanged, so change the version yourself
for later releases.

Coming from 0.1.0, you also gain automatic comments, which stay disabled until
you configure them; see the
0.2.0 notes.

For a source installation, extract the new archive and run its installer with
--replace. Only documentation differs from 0.2.0 there, so this is optional.

sh install.sh --config-dir /absolute/path/to/v2-opencode-config --replace

Compatibility and release assets

The tested target remains OpenCode CLI 2.1.2, Node.js 22.23.3, Ubuntu
22.04.5 under WSL2, and Azure DevOps Services REST API 7.1.
Validation
records the release checks. Azure DevOps Server and other operating systems
remain unvalidated.

The npm package is built from this tag with npm pack and has no
dependencies or install scripts. Release assets are the source archive
opencode-azure-devops-pr-review-v2-0.2.1.tar.gz and SHA256SUMS; verify
downloads with sha256sum -c SHA256SUMS. The demonstration video stays
attached to v0.2.0.

v0.2.0 — Opt-in comments after review

OpenCode Azure DevOps PR Review V2 — 0.2.0

A completed review can now preview or publish its comments automatically,
without another /pr-comment command. This is opt-in: existing installations
keep the manual workflow until you select a setting or command flag.

What changed

• afterReview selects none, preview or publish separately for quick,
  review and deep. Every mode defaults to none.
• One flag immediately after the PR URL (--preview, --publish or
  --no-comment) overrides that setting for a single review. Mistyped flags
  there produce an error; they do not fall back to automatic publication.
• A COMPLETE review starts the comment step as its own run, with a STARTED
  notice and receipt. /pr-stop cancels it. A stopped review starts no step;
  a review without findings needs no extra planning or model request. A busy
  conversation or PR skips the step and gives the command to run manually.
• Automatic publication holds individual items containing mentions, images,
  active HTML or script/private-file links in the saved preview. Other items
  are posted and read back. Ordinary links and unambiguous literal code are
  allowed; mentions are checked in code too. Inspect held items before using
  the explicit /pr-comment <review-id> --publish command.
• When every finding is already discussed on the PR, automatic publication
  reports NOTHING_TO_POST instead of adding another summary.
• Quick comments keep their "not independently verified" disclosure;
  severity and incomplete coverage do not block the whole publication.
• /pr-check shows the configured automatic action and posting identity as
  information. Setup errors identify the settings problem without values.
• The automatic-publication HTML checks read long tag-like text in linear
  time, avoiding the slowdown found during review of this feature.

For a one-off preview, substitute your own authorized Azure PR URL:

/pr-review https://dev.azure.com/YOUR_ORGANIZATION/YOUR_PROJECT/_git/YOUR_REPO/pullrequest/123 --preview

Use --publish in the same position to request automatic publication, or
--no-comment to suppress a configured automatic action for that run.
To default to previews, add this to AZPR's settings and restart the service:

{
  "afterReview": {
    "quick": "preview",
    "review": "preview",
    "deep": "preview"
  }
}

See automatic comments
for the per-item checks, cancellation and publication receipts. Review prompts
and the verified versus quick review methods are unchanged.

Installation

opencode plugin add 'github:WTLAIB/opencode-azure-devops-pr-review-v2#v0.2.0'

Follow the quickstart
for /pr-setup, a private PAT file, service restart and your first review.
The source archive includes install.sh for manual installation. Use one
installation method per OpenCode profile. This is a Git package release; it
does not publish an npm registry package.

Upgrading from 0.1.0

For a native installation, edit the existing AZPR entry in the OpenCode
configuration's plugins list: change
github:WTLAIB/opencode-azure-devops-pr-review-v2#v0.1.0 to
github:WTLAIB/opencode-azure-devops-pr-review-v2#v0.2.0. If the entry is an
object, change only its package value; preserve options.settingsFile and
other options. Keep one AZPR entry, then restart the OpenCode service. Native
settings remain outside the package cache, and missing afterReview values
default to none.

For a source installation, extract the new archive and run its installer:

sh install.sh --config-dir /absolute/path/to/v2-opencode-config --replace

This preserves operational settings and adds missing defaults. Keep the PAT
file and private state directory in place. Neither installation method needs
you to repeat /pr-setup for an already working configuration. For the usual
managed OpenCode service, restart with opencode service restart; if you run
opencode serve yourself, restart that process instead.

Compatibility and release assets

The tested target remains OpenCode CLI 2.1.2, Node.js 22.23.3, Ubuntu
22.04.5 under WSL2, and Azure DevOps Services REST API 7.1.
Validation
separates offline tests, real-host fixtures using fake services, and earlier
live Azure/model evidence. Release acceptance uses isolated profiles; it does
not run live models or publish Azure test comments. Azure DevOps Server and
other operating systems remain unvalidated.

Release assets are the source archive
opencode-azure-devops-pr-review-v2-0.2.0.tar.gz, azpr-live-demo.mp4, and
SHA256SUMS. Verify downloaded assets with sha256sum -c SHA256SUMS.
The video is the unchanged recording from v0.1.0 on 2026-10-22; it shows the
manual review, preview and publication workflow, not the new automatic step.
The demo guide
records its source commit, model, edits and limitations.

AZPR v0.1.0

OpenCode Azure DevOps PR Review V2 — 0.1.0

Review Azure DevOps pull requests in OpenCode, preview the resulting comments,
and choose when to publish them.

Included

• /pr-setup: configure your organization, one model and an existing private
  PAT file. Settings stay outside a native package's cache and survive updates.
• /pr-check: check Azure access, source reads and model readiness without
  calling a model.
• /pr-quick: one reviewer per shard covers function and risk. Findings are
  reported, not independently verified.
• /pr-review and /pr-deep: separate functional and risk reviews, followed
  by independent verification sessions. /pr-deep runs the same review with
  the stronger models configured in models.deep.
• /pr-comment: preview the summary and inline comments. Add --publish to
  post the saved plan; publication checks the PR head, skips existing markers
  and reads posted comments back.
• /pr-stop: cancel the active command in your conversation.
• Large-PR sharding, overflow recovery, bounded retries and two concurrent
  comment-planning pages.
• Private saved reviews and publication records, and Azure proxy/CA settings.
• The PAT kept alone in an owner-only file (azure.patFile), so
  settings.json holds no secret.

Installation

Install with OpenCode V2's plugin manager:

opencode plugin add 'github:WTLAIB/opencode-azure-devops-pr-review-v2#v0.1.0'

Follow the quickstart
to create a private PAT file, run /pr-setup with one model and your Azure
organization, then restart the OpenCode service. Review, preview and publication
are separate explicit commands.

The source archive also includes install.sh for manual installation into the
configuration directory used by your OpenCode V2 instance.

For an existing AZPR V2 installation, use the documented --replace option;
it preserves settings and adds defaults. Do not enable both installation methods
in one profile. This release does not require an npm registry package.

Compatibility and evidence

• Tested host: @opencode/cli 2.1.2.
• Tested OS: Ubuntu 22.04; the recorded environment uses WSL2.
• Azure: Azure DevOps Services, REST API 7.1.
• Native installer: OpenCode's Git package manager. Alternative source installer:
  POSIX sh and Python 3 standard library. No plugin build step or npm dependencies.

docs/VALIDATION.md records the offline tests, real-host tests with fake
services, and separate live Azure/model runs. Model quality and runtime
correctness are different claims; test counts do not establish review accuracy.

The release includes a real OpenCode terminal demonstration and Azure comment
read-back recording; see the demo guide
for the source, environment, edits and limitations.

Before using it with a team

Read docs/ENTERPRISE.md for data sent to the selected model, PAT permissions,
private retention, network configuration and publication behavior.

Quick findings are not independently verified. Preview generation uses a model
and can incur cost. A session can make multiple model requests; no fixed cost
or accuracy is promised. Azure DevOps Server is not supported; operating
systems other than the tested Linux environment remain unvalidated. The minimum
recommended PAT scopes and quick-review publication have been confirmed on the
dedicated Azure test repository; other organizations and repositories still need
their own acceptance checks.