Secrets
Keep credentials out of tests, stored encrypted on your machine, hidden from the model, redacted from logs and reports.
Test files are shared, reviewed, and versioned, credentials must never be in them. Named secrets keep the value on your machine only.
Add a secret
- Open Utils → Secrets.
- Click Add secret.
- Name it (e.g.
QA_PASSWORD), enter the Value, optionally a Description. - Enable Agent may use this secret if tests type it.
Values are stored encrypted on this machine, never in the project folder, never in version control. A colleague sees which names the project expects and enters their own values once.
Use it in a test
Reference the name, not the value:
Sign in with the QA credentials — the secrets named
`QA_USERNAME` and `QA_PASSWORD`.The agent sees only the name. It types a placeholder; the real value is substituted at execution time, hidden from the model, redacted from the conversation log and the reports.
Use it in a tool config
A tool, custom tool,
or MCP header references ${QA_PASSWORD} and gets the
value at run start.
One limit: a value typed into a visible field appears on screenshots, redaction covers text, not pixels. Use masked password fields for genuinely sensitive data.