Skip to content

copilot login auto-enters 'y/N' keychain prompt in v1.0.16 (regression: does not wait for user input) #2494

Closed

Description

@lovato

Describe the bug

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

  1. Ensure your environment triggers the 'System Keychain unavailable' prompt (e.g., on Linux or a system without a keychain, or when permission is denied).
  2. Run copilot login in the terminal.
  3. 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.
  4. 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.)
  • Possibly related: issue Copy-on-select broken since v1.0.15 due to mouse reporting #2472 reports input/mouse handling changes in this timeframe, though for a different context.
  • No open issues found that match this login prompt regression.

Please advise if you need any more debugging or logs.

Activity

  1. added theissue type on Apr 3, 2026
  2. alkutn123-tech commented on Apr 3, 2026

    @alkutn123-tech

    #2484 السماح بالدخول من بينانس عبر الرابط الخاص بي

  3. alkutn123-tech commented on Apr 3, 2026

    @alkutn123-tech

    السماح بالنسخ #2484

  4. alkutn123-tech commented on Apr 3, 2026

    @alkutn123-tech

    طلب الإثبات عند الدخول الى الحساب عبر كلمة مرور او المصادقة الثنائية من جوجل او مفاتيح دخول

  5. lovato commented on Apr 3, 2026

    @lovato
    ContributorAuthor

    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.

  6. alkutn123-tech commented on Apr 3, 2026

    @alkutn123-tech

    من المحزن أن نرى أننا نحاول القيام بعمل جاد هنا، بينما@alkutn123-techيتصرف على هذا النحو. استغرق مني الأمر ساعتين لتصحيح هذا الخطأ وعزل هذه المشكلة.

    اعتذر عن التأخير لأسباب خاصه شكرا عزيزي

  7. lovato commented on Apr 3, 2026

    @lovato
    ContributorAuthor

    @alkutn123-tech were you hacked?

  8. alkutn123-tech commented on Apr 3, 2026

    @alkutn123-tech

    لا

  9. added
    area:authenticationLogin, OAuth, device auth, token management, and keychain integration
    on Apr 6, 2026
  10. ChiliJohnson commented on Apr 7, 2026

    @ChiliJohnson

    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 login works as a workaround

  11. dasoumao commented on Apr 22, 2026

    @dasoumao

    @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.

  12. lovato commented on Aug 7, 2026

    @lovato
    ContributorAuthor

    I will try that and get back to you @dasoumao

  13. lovato commented on Aug 7, 2026

    @lovato
    ContributorAuthor

    @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.

  14. copilot-cli-bot commented on Oct 10, 2026

    @copilot-cli-bot

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:authenticationLogin, OAuth, device auth, token management, and keychain integration

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions