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

まず、docker compose ps と docker compose config が作業ディレクトリ外のディレクトリにアクセスする際の権限プロンプトを再現します。CLI が必要なアクセス権をどのように判断するかを追跡し、読み取り専用アクセスと書き込みまたは実行アクセスを区別する、あるいは実際に行われたアクセスレベルを明確に示すために、「完了」の定義を決めます。