Azure DevOps

Azure DevOps needs two things: a personal access token and your organization URL (or collection URL for Azure DevOps Server). In return you get pull requests with checks and reviews, and your assigned work items in the Inbox.

Creating the PAT

In Settings → Integrations, click the Azure DevOps tile and then Create a token in Azure DevOps ↗. With your organization URL filled in, the link opens that organization’s token page (https://dev.azure.com/your-org/_usersSettings/tokens); with the URL empty it opens the Azure DevOps home page, where your organizations are listed after sign-in.

Grant the PAT the ability to read your projects’ code, pull requests, and work items; creating and merging PRs from Birch needs pull-request write access. Azure DevOps does not let Birch name an exact scope preset — pick the narrowest scopes that cover those areas.

Adding the account

1. Open Settings → Integrations (⌘, / Ctrl+,) and click the Azure DevOps tile.

2. Fill the form:

   Field	What to enter
   Personal access token	Your Azure DevOps PAT
   Organization URL	Required. https://dev.azure.com/your-org — or your collection URL on Azure DevOps Server

3. Click Verify & connect. Birch verifies the PAT before storing it; on success the account appears with a Connected badge and Sync now / Remove buttons.

The token is stored in the system keychain, and multiple organizations can be connected as separate accounts. See the providers overview for the shared connection model.

What you get

• Pull requests — on the repository page and the workspace PR card, with state and checks; review requests and activity on your PRs land in the Inbox.
• Assigned work items — synced into the Inbox Tasks tab, nested under their parent work items; Birch resolves a parent’s title even when the parent itself isn’t assigned to you, so children don’t render as orphaned roots. Images embedded in a work item’s description are downloaded as thumbnails and handed to the agent when you start a workspace from the task.
• Work item status updates on workspace launch / PR creation — see status transitions.
• AI code review of new PRs — see AI code review, an Anthropic API feature.

Supported PR operations

• Create a PR from a workspace (with Create as draft) or via birch pr create — see Create a pull request.
• Check out a PR into a new workspace: birch pr checkout <url-or-id>.
• Merge with birch pr merge <url-or-id> (--strategy, --delete-source).
• List PRs with birch pr list.

Full flag reference: CLI — pr.

Troubleshooting

• Verification fails with a correct-looking PAT — check the URL. It must include your organization: https://dev.azure.com/your-org, not a bare https://dev.azure.com. On Azure DevOps Server, use the collection URL — the collection lives in the URL path and Birch keeps it.
• PAT expired — Azure DevOps PATs always carry an expiry date, and many organizations cap the maximum lifetime. Recreate the token and reconnect the account.
• Some projects are missing — the PAT’s organization and scope selection controls what it can see. A PAT created for a single organization cannot read another, and work items or PRs in projects outside the PAT’s scope won’t sync.