Describe the bug
For many prompts that result in new files being created, the harness first tries to read the still nonexistent files (probably as a safety measure); but instead of that being a hidden/silent operation, the terminal output shows "Read" errors, which makes it seem like the CLI has bugs even though it's expected behavior.
Affected version
GitHub Copilot CLI 1.0.28
Steps to reproduce the behavior
- Run prompts/flows that create new files ('/openspec-propose' is the one I used this time)
- See the "Read" errors in the terminal output.
Expected behavior
No "Read" error should appear.
Additional context

Describe the bug
For many prompts that result in new files being created, the harness first tries to read the still nonexistent files (probably as a safety measure); but instead of that being a hidden/silent operation, the terminal output shows "Read" errors, which makes it seem like the CLI has bugs even though it's expected behavior.
Affected version
GitHub Copilot CLI 1.0.28
Steps to reproduce the behavior
Expected behavior
No "Read" error should appear.
Additional context