[dpoloncsak]

>Treat the repo you point it at as already leaked

I don't mean this to downplay your experience, and I agree it should be opt-in by default, but any software engineer using these tools should understand completely that in order to 'read' your repo it needs to copy it all to the provider's servers. Using anything short of a local model has ALWAYS been a complete leak.

[gruez]

I think the sane take here is that if you let loose a coding agent in a project, you should assume it can read everything, because at any point it can issue a read tool command to read arbitrary file. If you want to be selective in what you share, a coding harness is probably a bad tool for the job. That said, AI companies still shouldn't be intentionally building features that upload code wholesale because it betrays the users trust. It's like if you hired a cleaner and the first thing it did was go to every room and opened every closet/cabinet. If you let a cleaner in your house, you're basically giving them full access, and if you're not comfortable with that, maybe you shouldn't be hiring a cleaner, but that doesn't excuse the cleaner rummaging through your stuff without a good reason.

Same principle applies to the grok build fiasco a few weeks ago.

[aarondong]

You could definitely tighten a harness to an extent that a coding agent would only be able to read files that you directly give as context.

But the truth is, much of the utility of the model is allowing it to grep across the codebase and explore for context.

I have great interest in zero knowledge inference, but as far as we know, it is difficult to build any sort of efficient representation.

[npmn]

Lovely example - Thank you for sharing this.

[carljungslabtek]

It doesn’t “need” to “copy it all”. Of course it has to (temporarily) send necessary code, but the coding agents I use have never just gone and read the entire repo from the first prompt. The whole thing doesn’t even fit in the context window.

I get what you’re saying about how you’re inherently trusting them by using their LLMs, but it’s different from pushing up the entire repo and git history to some server I didn’t ask for. The skill should ask if the user wants to upload to openAI “sites” or whatever the feature is called.

[Eddy_Viscosity2]

Getting a copy of everyone's code bases is part of the ai business. Use it for training, see what ideas people are developing to either copy or know where to invest. The list goes on. All to be fully monitized later on. No different than Facebook scooping up everyone's personal information.

[cyanydeez]

using anything other than a Local model is insecure. Your business agreement is meaningless.