Copilot CLI non-interactive runs can fail all writes/shell but still exit 0 as “success”

[VeryComplexAndLongName]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Copilot in GitHub

Body

I’m seeing a potentially serious reliability issue in Copilot CLI non-interactive mode.

Using:

copilot -p "<task>" --allow-all-tools

some runs deny every write/shell action with:

Permission denied and could not request permission from user

while read-only tools still work. Despite that, the run exits with code 0, prints a normal completion summary, and reports Changes +0 -0 (no work done), after consuming significant credits/tokens.

Why this is problematic

For automation, this is indistinguishable from success unless output is deeply parsed. Pipelines can silently pass while nothing was changed.

What I’d like

• Non-zero exit code (or explicit machine-readable status) when tool denials prevent actual work.
• Clear denial reason in logs from the permission layer.

If maintainers prefer, I can post full repro/environment details in github/copilot-cli as a bug report (already prepared).

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐