Stakpak + Azure DevOps (Microsoft Entra ID OAuth)
Stakpak runs the task; the Azure DevOps (Microsoft Entra ID OAuth) connector supplies only the operations and resources allowed by the account you authorize. The Composer selects Stakpak, asks for Azure DevOps (Microsoft Entra ID OAuth) access before sending, and keeps both choices in one task draft.
How the combination works
Stakpak plans and executes. Azure DevOps (Microsoft Entra ID OAuth) supplies authorized app access.
Runs the task through its ACP harness in a persistent cloud workspace while the selected AgentSky model supplies reasoning and generation.
Plan smarter, collaborate better, and ship faster with a set of modern dev services
Stakpak
Owns the task loop, model calls, cloud computer, tool choices, progress and final result.
Azure DevOps (Microsoft Entra ID OAuth) connector
Supplies the currently exposed operations for the authorized Azure DevOps (Microsoft Entra ID OAuth) account. It does not promise every feature in the Azure DevOps (Microsoft Entra ID OAuth) product.
Permission boundary
The connected identity, granted provider scopes, organization policy, resource sharing and the task's explicit instruction all constrain what Stakpak can do.
Setup and first task
Connect one Azure DevOps (Microsoft Entra ID OAuth) account and verify one known resource.
The Composer preselects Stakpak with Claude Sonnet 5. Start read-only when possible, then expand to write operations only after the account and resource boundary are clear.
Open the Stakpak Composer
The Composer above carries Stakpak, Claude Sonnet 5, and Azure DevOps (Microsoft Entra ID OAuth). Add a precise target and expected result; the draft stays on this page during sign-in or connector authorization.
Authorize the intended Azure DevOps (Microsoft Entra ID OAuth) account
Review the Azure DevOps (Microsoft Entra ID OAuth) account, workspace and permissions on the authorization screen. Your organization's policies or administrator approval may limit which resources the connection can access.
Run and verify a bounded task
Name one Azure DevOps (Microsoft Entra ID OAuth) resource you can already access and ask the agent to check whether a read operation is available. If it is, retrieve and summarize that resource without changing it. If it is not, ask the agent to explain the missing operation or permission. Open the same resource in Azure DevOps (Microsoft Entra ID OAuth) and compare it with the agent's result. Check the account, resource identifier and current content before using the output for another task.
Access, cost and limits
What to verify before scaling Stakpak + Azure DevOps (Microsoft Entra ID OAuth)
Tasks supported by this ACP harness through AgentSky's verified platform-model path.
Establish with the first run
- Stakpak and Claude Sonnet 5 remain selected after sign-in.
- Azure DevOps (Microsoft Entra ID OAuth) shows the intended connected account before the task is sent.
- The returned data matches one known source resource, with write actions excluded until separately authorized.
Still depends on your setup
- A catalog listing does not guarantee every Azure DevOps (Microsoft Entra ID OAuth) website feature is available as an agent operation.
- OAuth scopes do not replace organization policy, resource sharing or a precise task instruction.
- Total task cost can include model tokens, active computer time, paid tools, connectors and the provider's own plan or quota.
Verification and recovery
Check Azure DevOps (Microsoft Entra ID OAuth) itself before trusting the result.
Open the same resource in Azure DevOps (Microsoft Entra ID OAuth) and compare it with the agent's result. Check the account, resource identifier and current content before using the output for another task.
Connection troubleshooting
If Azure DevOps (Microsoft Entra ID OAuth) access fails, check the connected identity, resource sharing and requested permissions. Reconnect an expired or revoked account in connector settings. If the connection is healthy but an operation is unavailable, changing accounts may not resolve it.
Writes need explicit scope
Name the target record and exact allowed change. A request to summarize, analyze or draft does not authorize sending, publishing or deleting.
Re-check current state
For decisions or follow-up writes, open the resource in Azure DevOps (Microsoft Entra ID OAuth) and check its current state. A successful earlier read may already be stale.
Common questions
Related resources
Stakpak
Review Stakpak's supported models, capabilities and browser Composer.
Azure DevOps (Microsoft Entra ID OAuth) connector
Review the application-specific authorization and first-task guide.
Stakpak + Claude Sonnet 5
Review the current default agent and model combination.
Pricing
Review model, active-computer, tool and connector charges.