Access, credentials, and task safety

A coding task can run commands, edit repository files, and use the credentials supplied to its environment. Choose the repository, model account, execution machine, and secrets with that level of access in mind.

Limit the task's access

Use a repository connection scoped to the repositories your team needs. Provide only the environment secrets required by the task. Review the blueprint's commands and integration steps before using it against a sensitive system.

A container provides an execution environment. Do not treat it as a guarantee that code with credentials cannot act on the services those credentials authorize.

Understand where credentials go

Organization provider accounts are available through the organization's execution path. Local runner credentials are served by the connected machine. Explicit credential sync copies supported local credentials into organization storage and therefore changes who can use that execution capacity.

Runs record credential and environment snapshots for their execution. Disabling an account or removing a runner is not a guarantee that already-issued credentials or material held by a running process have vanished.

Protect chat access

A configured channel can authorize requests from its members and apps through the owner or admin who configured it. Restrict the channel's project assignments and review who can post there.

Treat read-only share links according to the access they grant. Ordinary dashboard links still require organization access, but a separately granted share has its own scope and revocation controls.

Inspect output before accepting it

Agent output, source comments, repository files, and retrieved content can contain mistakes or instructions that do not match your task. Review the diff, test evidence, and published results. A successful execution status is not an independent security review.

Stopping a run does not reverse changes already made to external systems. Use the repository or service's own recovery process when a published action must be undone.

Account and organization data

Use the account and organization controls for the export or deletion actions available to your role. Read the displayed consequences before confirming. Legal terms and privacy notices define the applicable commitments; this feature guide does not replace them.