Forum Discussion

timchambers's avatar
timchambers
Occasional Contributor
1 month ago

1Password Environments issue with VSCode and Claude Code Extension

I've noticed a curious issue in testing 1Password Environments in a repository where I'm editing with VSCode and using the Claude Code extension in VSCode. Since enabling 1P Environments, I've notic...
beta environments
macos
secrets management
troubleshooting
1P_Phil's avatar
1P_Phil
Icon for Moderator rankModerator
1 month ago

Hi timchambers​ ,

Thanks for reaching out. VSCode does some funky caching on their side and we have seen scenarios where VSCode paired with Environments gets wonky, but we have been doing our best to tune out the issues on our side.

Were you having the same user experience without Claude Code?  Is this specific to Claude Code or VSCode or only when they are used togther?

Thanks,
Phil

andeke07's avatar
andeke07
New Contributor
1 month ago

I am finding this as well:

  • Open VSCode
  • look at my .env file 
    • 1Password prompts me for my password, once authorised I can see my .env file
  • Close the .env file and open something else in the directory
  • Launch Claude Code
    • At this point, I can't open my .env file any more. Claude Code seems to have opened it and made it inaccessible to any other process 
    • My source control icon in the sidebar gets a permanent "refreshing" icon even if I close the .env and close the Claude Code chat
  • Only solution is to Quit VS Code and open again
  • timchambers's avatar
    timchambers
    Occasional Contributor
    29 days ago

    andeke07​ thanks for these repro steps, these reproduce for me today, too!

    1P_Phil​ to answer your question, the source control spinning indicator happens with and without Claude Code. The Claude Code slowness happens after the above repro steps with any action/prompt in Claude Code. Claude Code is basically unusable at this point, and it appears the .env file is continually trying to regenerate after this until quitting VSCode.