2.5.0 (2026-09-09)
Features Added
- Added preview
BetaAgentInsightMonitorsClientandBetaAgentInsightMonitorsAsyncClient, available throughAIProjectClientBuilder.beta().buildBetaAgentInsightMonitorsClient()andbuildBetaAgentInsightMonitorsAsyncClient(). These clients automatically opt in toFoundry-Features: AgentInsights=V1Previewusing the newFoundryFeaturesOptInKeys.AGENT_INSIGHTS_V1_PREVIEWvalue and support:- Managing monitors with
createAgentInsightMonitor,getAgentInsightMonitor,listAgentInsightMonitors,updateAgentInsightMonitor,deleteAgentInsightMonitor, andresetAgentInsightMonitor. - Starting and tracking runs with
beginCreateAgentInsightRun,listAgentInsightRuns,getAgentInsightRun, andcancelAgentInsightRun. - Reading and updating insights with
listAgentInsights,getAgentInsight, andupdateAgentInsight, including optional expanded details throughgetAgentInsight(monitorId, insightId, includeDetails). - New models for monitors, runs, and insights, including
AgentInsightMonitor,AgentInsightMonitorCreate,AgentInsightMonitorUpdate,AgentInsightRun,AgentInsightRunCreate,AgentInsightRunResult,AgentInsight,AgentInsightDetails,AgentInsightUpdate,AgentInsightsOverview,AgentInsightProposedFix, and related types.
- Managing monitors with
- Added optional routine dispatch authorization through
RoutineAuthorization.setIdentity(RoutineDispatchIdentity). Dispatch defaults toRoutineDispatchIdentity.AGENT; useRoutineDispatchIdentity.CREATORto explicitly dispatch as the principal that created a new routine. Authorization is ignored when updating an existing routine.
Breaking Changes
-
BetaRoutinesClient.createOrUpdateRoutine(String, String, Boolean, Map<String, RoutineTrigger>, RoutineAction)and itsBetaRoutinesAsyncClientcounterpart now require an additional trailingRoutineAuthorization authorizationparameter. Passnullto retain the previous agent-identity dispatch behavior. -
Regenerated client from the updated TypeSpec specification.