>However, personally, I prefer to have it configured to talk directly to Anthropic, to limit the number of intermediaries seeing my code, but in general I can see myself using this in the future.
Same. I can kind of feel OK about my code going to Anthropic, but I can't have it going through another third party as well.
This is unfortunately IT/security's worst nightmare. Thousands of excitable developers are going to be pumping proprietary code through this without approval.
(I have been daily driving Zed for a few months now - I want to try this, I'm just sceptical for the reason above.)
Once this is done, you should be able to use Anthropic if you have an API key. (This was available before today's announcement and still works today as of Zed 0.149.3)
That was a part of the reasoning of open sourcing my AI assistant/software dev project. Companies like Google have strict procedures around access to customer data. The same can't always be said about a startup racing to not run out of cash.
I really wanted to try this out with a difficult bug, as I've had Zed installed for a while and haven't actually used it. But I have no idea if I'd get in trouble for that... even though our whole team uses VSCode which I'm sure has scanned all our codebases anyway.
Same. I can kind of feel OK about my code going to Anthropic, but I can't have it going through another third party as well.
This is unfortunately IT/security's worst nightmare. Thousands of excitable developers are going to be pumping proprietary code through this without approval.
(I have been daily driving Zed for a few months now - I want to try this, I'm just sceptical for the reason above.)