Connections
Save model-provider and repository credentials, then choose which runs can use them.
Save a connection
Open Connections in your organization. Choose User for your credentials or Org for credentials shared with members. Owners and admins manage Org connections; saved values cannot be read back in the console.
Select a provider and save its required fields. A profile declares the connection names and fields its agents need. For user-started runs, complete values from the invoking process take priority, followed by User connections, then Org connections. Partial explicit values fail rather than borrowing missing fields. Organization automation uses Org connections only.
OpenAI, Anthropic, OpenRouter | Save the provider API key. These rows check the connection. |
|---|---|
Amazon Bedrock | Save a Bedrock API key and AWS region together. The row checks the connection. |
Microsoft Foundry | Save the API key and resource name. Models use your deployment names. |
Gateway | Save its HTTPS endpoint and API key. Codex uses Responses; Claude Code uses Messages. |
Decision Provider | Save the full System One endpoint and key. Choose its model in the profile. |
Foundry, Gateway, and Decision Provider show Configured after saving; the run checks them when used. For gateway protocols, field names, and supported provider pairs, use the Zeroshot connection reference.
Connect GitHub
On the User tab, choose Connect your GitHub account and approve Zeroshot Repository Access. This uses your repository grants and works without an App installation. Platform sign-in and your local gh login do not supply this connection.
Alternatively, choose Use a personal access token. Code delivery needs Contents and Pull requests read/write; issue comments need Issues read/write. GitHub organization approval and SSO policies still apply. Saving a PAT replaces the current User connection. For Copilot's GitHub runtime, use OAuth or a fine-grained personal PAT with Copilot Requests permission and a Copilot entitlement; classic PATs cannot authenticate it.
Organization GitHub access always uses the GitHub App. An owner or admin chooses Install App on the Org tab, approves installation, and selects repositories. This also enables shared GitHub comment automation. Personal access tokens are available only on the User tab. Installing the App does not replace the personal connection. Runs and preparation scripts inherit the repositories and permissions granted to the selected connection.
Custom connections and allowed destinations
Choose New connection under Custom connections, name it, and add its field names and values. Put nonsecret configuration in environment variables.
Allowed destinations optionally restricts custom credentials to up to sixteen HTTPS origins, one per line: for example, https://api.example.com. A port is allowed; paths, queries, and embedded credentials are not. This is connection metadata, so it does not belong in scripts or a node's environment-field declaration.
Provider credentials automatically bind to their configured endpoint or provider defaults; the custom list cannot broaden that binding. The proxy does not change provider permissions, and approved services can return sensitive tokens. SSH private keys and AWS signing credentials are unsupported while credential egress is enabled.
Credential destinations and allowed network hosts are separate. Both must permit the request. Allowing a host never authorizes a credential there.
Replace or disconnect
Replace the complete set of fields when updating a connection. Queued runs retain the values and destinations captured at acceptance; resumed attempts resolve them again. Managed GitHub credentials can refresh during a run. Disconnecting a connection does not stop accepted work; use Stop when needed.