Credentials

Overview

Credentials are encrypted secrets — passwords, API keys, access tokens — that agents can use without ever seeing the raw values. This is a core security feature: even if an AI model behaves unexpectedly, it literally cannot leak credentials it doesn't have access to.

How It Works

The credential system uses a placeholder injection model:

1. You create a credential with a name and value (e.g., name: "Gmail Password", value: "my-secret-pass")
2. The value is encrypted and stored securely — it never appears in chat, logs, or the AI model's context
3. When the agent needs to authenticate, it calls the use_credential tool with the credential name and the target form field
4. The system (not the AI) fills the value directly into the form field on the sandbox desktop
5. The agent sees only a confirmation that the credential was applied — never the raw value

Agent sees:  "Credential 'Gmail Password' applied to password field"
Agent NEVER sees:  "my-secret-pass"

This means the AI model cannot echo, print, log, or transmit your secrets. The credential value exists only in the encrypted store and in the form field on the sandbox — never in the AI's context window.

Creating a Credential

1. Go to the Credentials tab on your agent's detail page
2. Click Add Credential
3. Fill in:
   • Name — A descriptive label (e.g., "GitHub Token", "CRM Login")
   • Value — The secret itself (password, API key, token)
4. Click Save

The value is encrypted immediately and won't be shown again. Only the name is visible in the UI.

Managing Credentials

Each credential appears as a card in the Credentials tab showing:

• Name — The credential's label
• Created date — When it was added
• Edit button — Update the name or replace the value
• Delete button — Remove the credential (with confirmation dialog)

Editing a Credential

Click Edit on a credential card to:

• Change the name (for better organization)
• Replace the value (the old value is overwritten)

The current value is never displayed — you can only replace it with a new one.

Deleting a Credential

Click Delete to remove a credential. A confirmation dialog appears since this action cannot be undone. If the agent tries to use a deleted credential, it will receive an error.

How the Agent Uses Credentials

When your agent encounters a login form or authentication prompt, it uses the use_credential tool:

1. The agent identifies the form field that needs a password/key
2. It calls use_credential with the credential name and field location
3. The system injects the value directly into the field
4. The agent proceeds with the workflow

You can tell your agent which credential to use: "Log into GitHub using my 'GitHub Token' credential" — or the agent can list available credentials and choose the right one.

Security Model

The AI sees only credential names — never values. Even if you asked the agent "What's my GitHub password?", it would have no way to answer because the value doesn't exist in its context.

Best Practices

• Use descriptive names — "Salesforce Production Login" is better than "cred1"
• One credential per service — Don't reuse the same credential across different services
• Rotate regularly — Update credential values when you change passwords or rotate API keys
• Don't put secrets in instructions — Use credentials instead of typing passwords into custom instructions or skill files
• Test after creating — Ask the agent to use the credential on the target login form to verify it works

What's Next?

• Datasets — Learn how agents capture and manage structured data
• Files — Understand session files and persistent storage
• Mail — Configure your agent's email capabilities