Hi folks,Very excited to try out local Environments on my macOS system, but unfortunately I can't mount the .env on my local file system.Created new environment and added two keysChose "Local .env file" as my destinationChose my project directory, and chose `.` Opened new terminal window. `op` active.In my project directory, tried `ls -la` and do not see `.env`.Tried `cat .env` and get file not found error.Software:Latest macOS 261Password for Mac 8.11.16 (81116035)op 2.31.1op account is logged inAny thoughts?

Solved

.env not mounting on filesystem

Forum|Forum|8 months ago
October 29, 2025
2 replies
213 views

Hi folks,

Very excited to try out local Environments on my macOS system, but unfortunately I can't mount the .env on my local file system.

Created new environment and added two keys
Chose "Local .env file" as my destination
Chose my project directory, and chose `.`
Opened new terminal window. `op` active.
In my project directory, tried `ls -la` and do not see `.env`.
Tried `cat .env` and get file not found error.

Software:

Latest macOS 26
1Password for Mac 8.11.16 (81116035)
op 2.31.1
- op account is logged in

Any thoughts?

Best answer by PBAdams

OK, not sure what happened the first two times.

I successfully created and mounted a test .env in a test directory. I then went back and tried remounting the original environment into my original directory, and success!

@sid

`.` is the macOS Finder prompt asking if I really want to use the leading `.` in .env.

A

Anonymous

Hi @PBAdams ,

Thanks for sharing, sometimes just after enabling / updating the app, the backend service does not get updated (the one running in your menu bar). You might try restarting or (logging out and logging back in) with your Mac user account.

Let me know if that clears it up.

Regards,
Phil

PBAdamsAuthor

Hi @1P_Phil ,

I just did a full reboot and it's still not in the directory.

sid

1Password Employee

Hey @PBAdams ,

Our local .env files don’t actually depend on `op`, so I doubt this issue is related to that. Just to confirm, when you open the Destinations tab for your environment, is the local .env file you created enabled?

Also, could you double-check the file path and name shown there? It’s possible it was saved or named differently by mistake.

Additionally, in step 3, could you clarify what you meant by:

and chose `.`

PBAdamsAuthorAnswer

OK, not sure what happened the first two times.

I successfully created and mounted a test .env in a test directory. I then went back and tried remounting the original environment into my original directory, and success!

@sid

`.` is the macOS Finder prompt asking if I really want to use the leading `.` in .env.

Sign up

1Password employees: Sign in with SSO

Login to the community

1Password employees: Sign in with SSO

Scanning file for viruses.

This file cannot be downloaded