Credentials, AI models, and integrations

Secure credentials

Credentials store provider secrets for reuse without exposing the raw value in normal product responses. Create a named credential, select its provider or purpose, enter the secret, and associate it with the relevant model, integration, or resource.

Secret values are encrypted at rest. After saving, the UI shows metadata rather than the plaintext value.

Credential metadata and secret material have different exposure rules. Names, provider types, status, and last-updated timestamps can be displayed; decrypted values should exist only for the shortest runtime path needed to call the provider.

Rotate a credential when it expires or may have been exposed. Dependent workflows can fail until the replacement is connected.

AI models and providers

Venture AI settings define model providers, defaults, and workflow/phase overrides. Organization credentials determine which provider paths can actually authenticate, while agent records can supply a compatible model fallback.

Model availability, context limits, pricing, and provider behavior can change. Select models based on the current provider account and the workflow's needs.

Resolution follows the most specific valid configuration: a per-launch workflow-phase override can refine venture workflow and global settings. System workflow defaults and a compatible agent model fill gaps. The resolved model still requires a usable provider credential and sufficient context/output limits.

Changing a provider clears the selected model to prevent an invalid cross-provider pair. Active workflows keep their configuration snapshot; changing venture settings affects newly created runs.

See Compute, tokens, and model selection for the complete precedence tree, model-selection guidance, token formulas, prompt caching, and billing relationship.

Source control

Three source-control paths are supported: GitHub, GitLab, and platform-hosted repositories. Platform-hosted repositories are Beta — pull requests, review, and merge work, but there are no provider-side CI checks, and export or recovery can require support. No other source-control provider can be connected.

Source-control settings hold organization-level connections; venture resources identify the actual repository.

Keep the two layers distinct:

• the connection identifies provider credentials and organization-level integration state;
• the repository resource identifies the venture-owned repository, URL, provider, and workflow context;
• the workflow input selects the repository and base branch for one run.

Project management

Linear is the only supported integration for task-driven developer workflows. No other tracker can be connected, and workflows that are not task-driven do not need one at all.

Use the providers offered in the current Settings and launch forms as the source of truth. If a provider is not selectable there, it is not supported — do not plan a workflow around it.