Credentials & Browser Policy

Store the logins an agent needs, and limit where its browser can go.

Credentials

Store the logins an agent needs under Settings > Credentials rather than putting them in the task. Each credential has a key and a value.

• The key is formatted like an environment variable. It may contain letters, numbers, and underscores, and must start with a letter or underscore. PORTAL_USERNAME is valid, portal username is not.

• The value is the secret itself.

Your task must name the key for the agent to use it.

Log in with PORTAL_USERNAME and PORTAL_PASSWORD.

Feathery enters the stored value into the field directly. The agent never sees the secret, the run's activity log never records it, and it appears in the run recording only as dots.

Stored values can't be viewed again. Saving the section re-enters every secret, so type a new value for each credential you want to keep, and remove a row to delete that credential.

Browser Policy

Starting page

The URL each run opens before the agent does anything, such as https://portal.example.com/login.

Domain allowlist

The domains the agent's browser can navigate to, one per row. A leading *. covers subdomains.

portal.example.com
*.example.com

The browser enforces the allowlist itself, so a navigation outside the list fails regardless of what the agent attempts. Leave the list empty to allow any site.