← Back to context Comment by drchaim 5 days ago and all their keys, because sooner or later, the harness is gonna read them 4 comments drchaim Reply ai-x 5 days ago One company's irrational fear is a competitive advantage for someone else. fastball 4 days ago Claude code is actually very good at not reading your keys these days. drchaim 4 days ago Not the case for me. I tried .envs, ansible-vault and sops, and it always ends up reading the unencrypted ones for some reason, usually in debugging sessions, it finds a way to read them. fastball 4 days ago Well it reads them, but (at least for me) it reads them in a way where it filters out the actual key values.
fastball 4 days ago Claude code is actually very good at not reading your keys these days. drchaim 4 days ago Not the case for me. I tried .envs, ansible-vault and sops, and it always ends up reading the unencrypted ones for some reason, usually in debugging sessions, it finds a way to read them. fastball 4 days ago Well it reads them, but (at least for me) it reads them in a way where it filters out the actual key values.
drchaim 4 days ago Not the case for me. I tried .envs, ansible-vault and sops, and it always ends up reading the unencrypted ones for some reason, usually in debugging sessions, it finds a way to read them. fastball 4 days ago Well it reads them, but (at least for me) it reads them in a way where it filters out the actual key values.
fastball 4 days ago Well it reads them, but (at least for me) it reads them in a way where it filters out the actual key values.
One company's irrational fear is a competitive advantage for someone else.
Claude code is actually very good at not reading your keys these days.
Not the case for me. I tried .envs, ansible-vault and sops, and it always ends up reading the unencrypted ones for some reason, usually in debugging sessions, it finds a way to read them.
Well it reads them, but (at least for me) it reads them in a way where it filters out the actual key values.