Skip to content

When new files are being created, GH Copilot CLI often tries to read them first and outputs failed Read operations #2749

@dcominottim

Description

@dcominottim

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

  1. Run prompts/flows that create new files ('/openspec-propose' is the one I used this time)
  2. See the "Read" errors in the terminal output.

Expected behavior

No "Read" error should appear.

Additional context

Image

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:terminal-renderingDisplay and rendering: flickering, scrolling, line wrapping, output formattingarea:toolsBuilt-in tools: file editing, shell, search, LSP, git, and tool call behavior

    Type

    No fields configured for Bug.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions