[isodev]

I’m so happy our entire operation moved to a self hosted VCS (Forgejo). Two years ago, we started the migration (including client repos) and not only we saved tones of money on GitHub subscriptions, our system is dramatically more performant for the 30-40 developers working with it every day.

We also banned the use of VSCode and any editor with integrated LLM features. Folks can use CLI based coding agents of course, but only in isolated containers with careful selection of sources made available to the agents.

[frumplestlatz]

Banning VSCode — instead of the troublesome features/plug-ins — seems like a step too far. VSCode is the only IDE that supports a broad range of languages with poor support elsewhere, from Haskell to Lean 4 to F*.

I work at a major proprietary consumer product company, and even they don’t ban VSCode. We’re just responsible for not enabling the troublesome features.

[trenchpilgrim]

> VSCode is the only IDE that supports a broad range of languages with poor support elsewhere

I just checked Zed extensions and found the first two easily enough. The third I did not, since they don't seem to have a language server, just direct integrations for vim/emacs/vsc.

[frumplestlatz]

Not all the integrations are equal in quality/usability, and in the case of F*, the VSCode extension is by far the most advanced.

I switch between Emacs, VSCode, JetBrains IDEs, and Xcode regularly depending on what I am working on, and would be seriously annoyed if I could not use VSCode when it is most useful.

[hansmayer]

Just out of interest, what is your alternative IDE?

[isodev]

That depends a bit on the ecosystem too.

For editors: Zed recently added the disable_ai option, we have a couple of folks using more traditional options like Sublime, vim-based etc (that never had the kind of creepy telemetry we’re avoiding).

JetBrains tools are OK since their AI features are plugin based, their telemetry is also easy to disable. Xcode and Qt Creator are also in use.

[belter]

Did you look at VSCodium ?

https://vscodium.com/

[elevation]

With 30-40 devs each pulling a repository to their local machine, how do you prevent even one of them from accidentally exposing the entire repo to an LLM instead of “selected sources”?

And if a user were reluctant to tell you (fearing the professional consequences) how would you detect that a leak has happened?

[aitchnyu]

What do your CLIs connect to? To first-party OpenAI/Claude provider or AWS Bedrock?

[isodev]

Devs are free to choose, provided we can vet the model prover’s policy on training on prompts or user code. We’re also careful not to expose agents to documentation or test data that may be sensitive. It’s a trade off with convenience of course, but we believe that any information agents get access to should be a conscious opt-in. It will be cool if/when self hosting claude-like LLMs becomes pragmatic.

[aitchnyu]

What do you think about AWS Bedrock with Sonnet/R1/Qwen3?