Yes, some code is sent to Anthropic. We're hoping to: find initial users that are comfortable with software copilots (github copilot, cursor, etc) -> iterate on their feedback to make diagram generation require less sophisticated LLMs -> move everything locally

This will be a no go for more and more large companies.

We just had a major incident because someone accidentally uploaded our codebase via a VS code extension, lawyers, everything involved. I expect that non local AI tools will be banned soon.

Think about it, what 3rd party tool would you let scrape your whole codebase and send it to their server?

Makes total sense, and sorry to hear about the incident. At the moment, closed source models are the only viable way to generate high quality diagrams. Once that changes, we'd prefer to switch to open source too for many of the reasons you mentioned.

Sent via your servers, I assume, since you are providing the Anthropic api key.

So we must trust both Anthropic's and your infrastructure with our code.

I agree that a local LLM is the way to go.

That's correct, our server just routes calls directly to Anthropic. Some users requested an option to input their own API key and talk to Anthropic directly. I'll add this by the end of the week, maybe today if time.

Local LLM is still the end goal

Ok. I think you should be more transparent about this, until everything is local.

I mean, more than stating "We don't store any of your code."

Got it, how about a manual trigger for diagram creation and an explicit description of LLM/server usage on the page with the trigger?

Maybe just the truth in plain text, up front?

There seems to be a bug or comment depth limit, I can't reply to your comment below. I just published an update to extension description explaining that code moves through our servers. It may take a few minutes to appear. Since this post, we added a privacy policy to our website and the ability to input your own API key, circumventing our servers altogether. I will list this feature in the extension description once we have time to require manual triggering of architecture generation

Sure thing - we'll plainly state this in the extension's description, the extension itself, and our website

Hi again. I just checked the VS Code extension description - it hasn't changed.