not sure we should commit this into an open source repo – seems like a vulnerability for prompt injection :)
We could pass a --settingsagentic/{{name}}.settings.json file ?

Also, I'm curious: Why do you unset the API key here? To force somebody to login?

how would that be an attack vector?

I am removing the env because otherwise it doesn't pick up the Max subscription but the API key (which is usage based)

I am removing the env because otherwise it doesn't pick up the Max subscription but the API key (which is usage based)

ah i see! that makes sense.

how would that be an attack vector?

for example if a malicious contributor adds something into a build script that replaces the contents of youragentic/ file. If you then run the agentic file, claude might dostuff you don't expect – with GH permissions, claude might even push unreviewd commits to master etc

If we review everything closely, that won't be an issue, but I could see that someone contributes aC file or something that we just gloss over

Of course, this would still happen if you run--dangerously-skip-permissions via your own terminal, but then at least nobody would know that we use that param 😇

Your call!

good point, I just commented them out for now with a node 'use at your own risk'