Introducing Vaults in Roamkiln Functions

Mara Velde & Jonah Price
Engineering
6 min read

TL;DR: Vaults give Roamkiln Functions a safe place to keep the passwords, API tokens and one time codes an agent needs, so secrets never sit in your prompts or your code.
Functions let you deploy agent code next to the browsers it drives. As soon as those functions touched real accounts, the same question came up in every review: where do the credentials live, and who can see them?
Why secrets need their own home
Before Vaults, teams passed credentials as environment variables or pasted them into task inputs. Both work, but both make it easy for a secret to end up in a log, a replay or a model’s context window.
Secrets are encrypted at rest and only decrypted inside the function that asks for them.
Values are masked in logs, replays and session recordings.
Each vault has its own access list, so one team’s tokens stay out of another team’s runs.
Reading a secret from a function
Create a vault in the dashboard, add a secret, then read it at run time with vault.get("crm-login"). The value goes straight into the page field, and the model only ever sees a placeholder.
Rotating a secret is a single update in the vault. Every function that reads it picks up the new value on its next run, with no redeploy.
What we are working on
Vaults start with Functions. We are looking at hosted browser sessions next, and we would like to hear which kinds of secrets your agents need most.
Talk to us about Roamkiln for your team
Get started with sessions for your agents
Get in touch
Keep reading

What is Agent Passport?
Ilse Moreau
Engineering

How to design long running browser tasks with Roamkiln
Theo Brandt, Nia Okafor & Lena Sato
Engineering

Roamkiln and Keystone: shared sign in for browser agents across every app your team uses
Roamkiln Team
Company

What is Kiln Script?
Mara Velde
Engineering
View all blog posts
