Add launch flag to bypass trust folder prompt

[DamianEdwards]

When automating copilot CLI from scripts it would be very helpful to have a way to opt-in to trusting the folder via a launch flag so that the folder doesn't first have to be trusted via an interactive session and answering the prompt manually, or by directly editing the ~\.copilot\config.json file.

I'm imagining something like:

$ copilot --trust-folder --allow-all-tools

Related #1121

[danmoseley]

@DamianEdwards to be clear then if this flag just edited copilot config.json (and also applied to the session you're starting) that would work for you? ie., you want persistent.

[DamianEdwards]

I wouldn't expect it to be persistent honestly. I expect flags to only apply to the current session I think? But not sure how strongly I feel about that.

[danmoseley]

Ah gotcha. Yes, seems like a clear omission of a flag matching the user prompt. I agree with not persistent.

There is no concept of per-path trust I see, so --trust-path meaning cwd makes sense. Also I think --trust-path rather than --trust-folder even though it's "trustedFolders" in the config file, as that's consistent with --allow-all-paths and paths is more the non Windows term.

Unrelated to trust, but I notice that for some reason we are missing --allow-path. And there are no --always-allow-* variants currently.

[danmoseley]

In normal interactive mode if you later /cwd it will pop the question again. I think it's OK for --trust-path to just handle the initial cwd, can always be made laxer later.

[danmoseley]

I put up a PR