The Read tool is blocked for .env files but, I noticed that, if it reasons that the only possible explanation for something not working has to be that I forgot to fill in the .env file, it runs a script to inspect the file… And then I see my secrets in the logs. Some secrets get redacted, but when the environment variable is a URL with parameters, like the username and password for a Postgres connection, it’s displayed in plain text. And even if they’re redacted from the logs, it still had access to them. What’s stopping it from attempting to use one of my passwords to try to break through some authorization issue? What are you all doing to work around this problem? For additional context… I have 23 services running on individual stacks, 37 docker containers. submitted by /u/JerryZaz
Originally posted by u/JerryZaz on r/ClaudeCode
You must log in or # to comment.