VS Code Extensions
Azure DevOps Relay

Azure DevOps Relay

by semick-dev

Access Azure DevOps projects, builds, task logs, timelines, and build artifacts directly from VS Code with local caching and secure PAT storage.

Downloads

19

Rating

— (0)

Version

0.0.14

Last updated

Apr 20, 2026

An Azure DevOps interface that allows easy access to build artifacts and task details.

Demo

Azure DevOps Relay interface

Video Link:

What It Does

  • Loads Azure DevOps projects from a target organization URL
  • Browses build definitions and recent builds
  • Opens build details, timeline records, and task logs
  • Downloads large logs idempotently instead of forcing inline loads. If you click a task, don't worry about the "oh crap now my vscode will crash."
  • Downloads build artifacts to a local folder
  • Caches data locally for faster repeat access, allows easy cache popping at will

UI Flow

  1. Install semick-dev.ado-relay.
  2. Open the Azure DevOps Relay activity bar view.
  3. If prompted, run Azure DevOps Relay: Set Token from the Command Palette and save an Azure DevOps PAT with at least Build:Read.
  4. Enter the target Azure DevOps organization URL and load projects.
  5. Choose a project and open its definitions or artifacts view.
  6. Select a definition to inspect recent builds.
  7. Open a build to inspect timeline steps, task logs, and artifacts.

Notes

  • Relay stores the Azure DevOps PAT in VS Code secrets after you run Azure DevOps Relay: Set Token.
  • Use Azure DevOps Relay: Clear Token to remove a stale or invalid token, then run Azure DevOps Relay: Set Token again.
  • Large task logs are gated behind an idempotent download action. Repeated clicks will simply load previously downloaded file.
  • Contributor and local debugging instructions live in CONTRIBUTING.md.

Data Storage

Azure DevOps Relay usually stores its local raw data under VS Code's extension globalStorageUri, rooted at:

  • .relay/cache/ for cached API responses
  • .relay/build/<buildId>/ for build-specific data such as timestamps, downloaded logs, timeline data, artifact metadata, and related cached files

The exact parent location depends on your VS Code platform/profile, but the extension-managed data is typically organized under a .relay folder inside the extension's global storage area.