Unable get output of the copilot execution in CI pipeline

[doggy8088]

Describe the bug

I run copilot in the Hosted Agent on Azure Pipelines. I'm using ubuntu-latest agent.

I noticed it executed everything, but all the output text vanished. Why would that happen? Does this occur in non-TTY mode?

Can you add a --output option for GitHub Copilot CLI?

Affected version

0.0.356

Steps to reproduce the behavior

copilot --agent code-review -p "$(cat code-review-prompt.txt))" | \
  tee $(Build.ArtifactStagingDirectory)/github-copilot-cli-result.md

Expected behavior

I expect the output of the GitHub Copilot CLI should be full and complete.

Additional context

• Logs using --log-level and --log-file flags: Yes, I see the logs with complete output. I just can't see output in the STDOUT.
• Operating system (e.g., Windows, macOS, Linux): Linux
• CPU architecture (e.g., x86_64, ARM): x86_64
• Terminal emulator (e.g., Terminal, iTerm2, Windows Terminal): Not a terminal
• Shell (e.g., bash, zsh, fish): bash

[EvanBoyle]

@doggy8088 this is a bug with -p mode and codex / other models that use the responses API.

@jmoseley can you add this to your plate to fix as a part of the streaming PR (or at least verify that -p works properly with thinking text when we move to streaming)

[examon]

This has been fixed in v0.0.422. The output-vanishing bug when piping in non-TTY CI environments is resolved, and a new --output-format json flag was introduced for programmatic pipeline integrations — running with --output-format json emits each response event as a JSON line to stdout, making it straightforward to capture output in CI. If you're still seeing issues, please feel free to reopen.