Skip to main content
Capability: Vault credentials
Use this when the form itself needs real data — a name, an address, a resume field — and the site it’s on needs a login first. Put the login credentials in Vault, not in the goal text: the agent never sees the password, and it isn’t left sitting in your run history as plain text.
1

Connect your vault

Connect a supported password manager once. See Connect Your Vault for the setup flow.
2

Run the agent with vault access and the form goal together

The agent logs in with the Vault-stored credential first, then works through the form fields in the goal. Nothing sensitive needs to appear in the goal text itself — only the form data that isn’t secret.
Output:

Multi-Step Forms

A form that spans several pages — personal info, then details, then a review step — works the same way: describe every step in one goal, and the agent carries state across the whole flow.
Python

Common Mistakes

Writing "log in with password XYZ" in the goal works, but the password then sits in plain text in your run history. Use use_vault: true with a connected credential instead — see Scrape Content Behind a Login Using Vault for the setup, same mechanism, different task.
The credential’s domain has to match the site the agent navigates to. Full matching rules: Vault Credentials Troubleshooting.
“Fill in my info” doesn’t tell the agent what your info is. Spell out every field value explicitly, the same way the Goal Prompting Guide recommends for any task.

Scrape Content Behind a Login Using Vault

The same Vault mechanism, for reading instead of submitting

Vault Credentials

Domain matching, security model, and troubleshooting

Build a Google Form With a Browser Context Profile

A saved-session alternative when Vault isn’t the right fit

Goal Prompting Guide

Write goals that succeed on the first try