You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
copilot login auto-enters 'y/N' keychain prompt in v1.0.16 (regression: does not wait for user input) #2494
After upgrading to version 1.0.16, running copilot login when the System Keychain is unavailable no longer prompts the user for (y/N) input as expected. Instead, the CLI auto-"enters" on behalf of the user without waiting for input, causing the authentication process to end/fail prematurely. This did not occur with version 1.0.14, which properly waited for user input.
This appears to be a regression or unintended side effect introduced in v1.0.16.
Affected version
1.0.16 (regression from 1.0.14, which worked correctly)
Steps to reproduce the behavior
Ensure your environment triggers the 'System Keychain unavailable' prompt (e.g., on Linux or a system without a keychain, or when permission is denied).
Run copilot login in the terminal.
Observe that version 1.0.16 does not wait for user input at the (y/N) prompt and auto-submits it, causing the authentication process to terminate.
In version 1.0.14, the prompt waits for user input and continues as expected.
Expected behavior
CLI should always wait for explicit user input (y or N) at the "System Keychain unavailable" prompt and not proceed automatically. The authentication/login process should function as it did in 1.0.14.
Additional context
OS: Debian Distro, WSL
Shell: /bin/bash
Terminal emulator: Microsoft Terminal
Regression coincides with changes introduced in 1.0.15 and 1.0.16 (input handling, mouse reporting, etc.)
@lovato@ChiliJohnson Hi, try adding "store_token_plaintext": true to your copilot config.json , as mentioned in #89 (comment). I was able to skip the y prompt successfully.
@dasoumao confirmed that this workaround works.
However, as per the config.json file now in August/26, there is a comment saying that the file is managed automatically, and user settings should go in "settings.json", which I did. And it worked.
This however isn't the solution to the original problem.
This appears to be resolved as of GitHub Copilot CLI v1.0.95. 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.
Activity
alkutn123-tech commentedon Apr 3, 2026
#2484 السماح بالدخول من بينانس عبر الرابط الخاص بي
alkutn123-tech commentedon Apr 3, 2026
السماح بالنسخ #2484
alkutn123-tech commentedon Apr 3, 2026
طلب الإثبات عند الدخول الى الحساب عبر كلمة مرور او المصادقة الثنائية من جوجل او مفاتيح دخول
lovato commentedon Apr 3, 2026
So sad seeing we are trying to do serious work here, while @alkutn123-tech is acting like that.
It took me 2h to debug this and isolate this problem.
alkutn123-tech commentedon Apr 3, 2026
اعتذر عن التأخير لأسباب خاصه شكرا عزيزي
lovato commentedon Apr 3, 2026
@alkutn123-tech were you hacked?
alkutn123-tech commentedon Apr 3, 2026
لا
ChiliJohnson commentedon Apr 7, 2026
I can confirm that this is affecting all versions from 1.0.15 onwards
It doesn't appear to be accepting anything from stdin at all because not even
yes | copilot loginworks as a workarounddasoumao commentedon Apr 22, 2026
@lovato @ChiliJohnson Hi, try adding
"store_token_plaintext": trueto your copilot config.json , as mentioned in #89 (comment). I was able to skip the y prompt successfully.lovato commentedon Aug 7, 2026
I will try that and get back to you @dasoumao
lovato commentedon Aug 7, 2026
@dasoumao confirmed that this workaround works.
However, as per the config.json file now in August/26, there is a comment saying that the file is managed automatically, and user settings should go in "settings.json", which I did. And it worked.
This however isn't the solution to the original problem.
copilot-cli-bot commentedon Oct 10, 2026
This appears to be resolved as of GitHub Copilot CLI v1.0.95. 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.