Permission prompts don't distinguish read-only from write operations outside cwd

Describe the feature or problem you'd like to solve

When the agent runs any shell command touching a directory outside the working directory, the CLI prompts for full approval of that path — even for provably read-only commands like  docker compose ps  or  docker compose config . This forces users to either grant broader access than needed or manually run harmless diagnostic commands themselves. Please consider a tiered permission model (read vs. write/execute scope), or at minimum surface in the prompt what level of access is actually being exercised.

Proposed solution

Copilot should only ask for the permissions it actually needs. If doesn't need to write to a directory then it shouldn't escalate to get that permission.

Example prompts or workflows

No response

Additional context

No response

Inizia riproducendo la richiesta di autorizzazione per docker compose ps e docker compose config quando accedono a una directory al di fuori della directory di lavoro. Traccia il modo in cui la CLI determina l’accesso richiesto e definisci cosa significa “completato” per distinguere l’accesso in sola lettura dall’accesso in scrittura o esecuzione, oppure per rendere chiaramente visibile il livello di accesso esercitato.