AgentConnect
Agents

Update a repository authorization

Raise an existing repository grant to a stronger access tier after re-checking the provider’s authorization requirements, change how the repository is materialized (materialize: always, decision or on-demand; decision needs the agent’s repositorySelector and daemons serving the agent that advertise repo-selector-v1, else 409 with REPOSITORY_SELECTOR_MISSING or DAEMON_FEATURE_MISSING), or both. At least one field is required. Downgrades still require revoke and reauthorize so review-check cleanup remains explicit; materialize moves freely and re-projects the agent’s spec. Raising a GitHub or Azure DevOps grant makes the caller its attester, which also honors a stale grant again.

PATCH
/v1/orgs/{orgId}/agents/{agentId}/repos/{repoAuthId}

授权

bearerAuth
授权Bearer <token>

位置: header

路径参数

orgId*string
agentId*string
repoAuthId*string

请求主体

application/json

TypeScript 定义

在 TypeScript 中使用 request body 类型。

响应主体

application/json

application/json

application/json

application/json

application/json

application/json

application/json

curl -X PATCH "https://example.com/v1/orgs/string/agents/string/repos/string" \  -H "Content-Type: application/json" \  -d '{}'
{  "id": "string",  "provider": "github",  "repoId": "string",  "repoFullName": "string",  "access": "read",  "materialize": "always",  "createdBy": "string",  "createdAt": "string",  "stale": {    "since": "string",    "reason": "access_lost"  },  "connectionId": "string"}