Skip to main content

Project Secrets

Use Secrets to store protected values that agents need without exposing them in agent code.

Before You Begin​

  • You have a project.
  • You know which secret key the agent expects.

How Secrets Fit Into the Workflow​

  • Secrets are project-scoped.
  • Agents can declare required secret keys.
  • Agent detail pages show whether required secrets are present or missing.
  • Missing secrets can block preview and execution until they are created.

Add a Project Secret​

  1. Open Secrets inside the project.
  2. Create a new secret using the required key name.
  3. Save the value.
  4. Return to the agent detail page or run page that was blocked.
  5. Confirm that the missing-secret warning is resolved.
  6. Retry the preview or run.

Confirm That the Secret Resolved the Blocker​

After you add the missing secret, review the related agent page again. If the key name matches what the agent expects, the agent should be able to preview or run without the earlier secret-related error.

Management Guidance​

  • Secrets are managed at the project level.
  • Agent detail pages can show when a required secret is missing.
  • Creating the missing secret can unblock preview and execution flows immediately.
  • If you are unsure which key to create, start from the agent detail page instead of guessing.