Browser Use Got Rid of .env Files With a Two-Minute Infisical Setup

Browser Use builds infrastructure that makes websites accessible to AI agents. Its engineering team was moving quickly, but local development still depended on manual secret sharing. They kept local copies of credentials so their environments would run.

When a key changed, developers had to figure out who changed it, identify which secret was missing, and ask someone to send over the latest .env file. The process was frustrating and easy to lose track of.

“There was some pain of, ‘Come on, who changed the secret? Why doesn’t it work anymore? I’m missing some secrets. Which one am I missing?’” says Larsen Cundric, a founding engineer at Browser Use. “There are too many. Just send me the whole .env file.”

Everyone on the engineering team needed a straightforward way to use the same secrets for local development without putting credentials on individual machines.

Browser Use’s CTO asked Larsen to investigate whether Infisical could improve the team’s developer experience. Larsen evaluated the product against one specific need: store the team’s development secrets centrally, then make them available automatically when a developer starts the local environment.

Browser Use joined Infisical Cloud and created a project. The team then connected its Docker Compose workflow to Infisical so the environment pulls the current secrets before starting.

The implementation took about two minutes. Larsen asked an AI coding agent how to set up Infisical, and the agent configured the local workflow. The only manual step was logging in through the Infisical CLI.

“The agent went on and did it in two minutes, and then we had our dev environment saved,” Larsen says. “I logged in, and it just worked out of the box.”

The team’s operating rule is simple: if a developer needs a new local secret or needs to change one, they add or update it in Infisical. The next developer who pulls the local environment receives the current value automatically. Everyone on the team has access to the shared development secrets, so no one has to search through chat history for credentials or request a private copy.

After moving local development to Infisical, the recurring conversations about missing or outdated secrets stopped. Developers know where to find the values, and changes flow into the Docker Compose environment without manual distribution.

“We don’t think about that anymore,” Larsen says. “Ever since we switched to Infisical for local development, this discussion has not come up.”

The team has not needed a new platform process or a central administrator. Developers can open the Infisical dashboard, add or update a secret, and continue working. That simplicity has also made adoption quiet. Larsen says there have been zero complaints about secrets (which used to be a source of friction) since their adoption of Infisical.

For Larsen, the biggest benefit was closing a problem that had been sitting in the back of his mind without adding another system that engineers resist.

“It was a mental load,” he says. “I knew we’d need to solve this at some point. Infisical came along and solved it immediately, and I could finally close that chapter.”