Prompt mode asks for user input

[alexneyler]

Describe the bug

When using -p, copilot still asks for user input and hangs (user would not be able to input anything in prompt mode). It reproduces on 0.0.348 and does not reproduce on version 0.0.339, so the regression appears to have been introduced at some point between those two versions.

Affected version

0.0.348

Steps to reproduce the behavior

Prompt something like this: copilot -p "Write a file to /tmp with the content 'hello world'"
Expected result is something like:

Write to tmp with the content 'hello world'.
Permission denied and could not request permission from user

Actual result:

I'll create a file in /tmp with the content 'hello world'.

The following paths are outside the allowed directories:

• /tmp/hello.txt

Allow access to these paths? (y/n):

Expected behavior

Expected result is something like:

Write to tmp with the content 'hello world'.
Permission denied and could not request permission from user

Previously, copilot would catch these errors and try different things instead

Additional context

OS: Linux (Debian GNU/Linux 12 (bookworm))
Model: claude-sonnet-4.5
Logs (generated with --log-level all): logs.log

[alexneyler]

In case anyone else is stuck on this for automation purposes, you can pass in --allow-all-paths to YOLO the path approval as well.

[RyanHecht]

We've since added documentation and several new modes that should prevent other folks from running into this. Thanks for the report!