Passing init from the command line no longer works

[troydjones]

Describe the bug

When performing an init from the command line such as: copilot init

The .github folder is creating, but no .md file is created and powershell window returns back to a PS prompt within a couple of seconds. The /init from within copilot still works however.

Affected version

GitHub Copilot CLI 1.0.4.

Steps to reproduce the behavior

copilot init

Expected behavior

the copilot-instructions.md file is written in the .github folder

Additional context

No response

[tmclaugh]

I'm on 1.0.5 and landed on this bug after googling why copilot init stopped responding in a directory just now. It started after i ran copilot for interactive mode to change the model I use from Claude Sonnet 4.6 to GPT-5.3-Codex. Still have issue after switching back. Running /init in interactive mode works fine.

EDIT:

• Changed to a new project directory and same issue.
• Closed VSCode to ensure that wasn't causing issues; no change

[troydjones]

I didn't think about it, but I also switched from Claude Sonnet 4.6 to GPT-5.3-Codex and this issue occurred after that.

[troydjones]

FYI this is still an issue on GitHub Copilot CLI 1.0.5 for me, but slightly different.

Now, instead of just getting the PS prompt back, it starts copilot, but acts like the init parameter was never passed in. Just starts up as if I didn't pass any parameters at all.

[copilot-cli-bot]

This appears to be resolved as of GitHub Copilot CLI v1.0.88. Please update to that release or a newer stable version. We're closing this as completed. If it still happens, please comment with your version and reproduction steps.