starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

"unauthorized: unauthorized: AuthenticateToken authentication failed" error with GitHub Copilot #22647

New Issue
Open
opened 2026-01-31 08:19:29 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 08:19:29 +00:00
Owner
Copy Link

Originally created by @adrastogi on GitHub (Dec 11, 2024).

Originally assigned to: @PankajBhojwani on GitHub.

Windows Terminal version

1.23.3401.0

Windows build number

10.0.26338.5000

Other Software

No response

Steps to reproduce

On my build:

  1. Launched Terminal Canary
  2. Opened the chat pane, which had GitHub Copilot as the active provider, and typed a query to GitHub (I was using Ubuntu)

Expected Behavior

I was expecting GitHub Copilot to give me a response

Actual Behavior

The chat bubble with the model's response gave me back an error reading, "unauthorized: unauthorized: AuthenticateToken authentication failed".

I haven't tried as yet but am assuming I can work around this by clearing the token and trying again.

One thing to note is that around the same time I was messing with clearing out the token on a Win10 device, so I'm not sure if this is potentially caused by roaming + merge weirdness w/ the data in Credential Manager. That could be a total red herring, but mentioning here for completeness.

Originally created by @adrastogi on GitHub (Dec 11, 2024). Originally assigned to: @PankajBhojwani on GitHub. ### Windows Terminal version 1.23.3401.0 ### Windows build number 10.0.26338.5000 ### Other Software _No response_ ### Steps to reproduce On my build: 1. Launched Terminal Canary 2. Opened the chat pane, which had GitHub Copilot as the active provider, and typed a query to GitHub (I was using Ubuntu) ### Expected Behavior I was expecting GitHub Copilot to give me a response ### Actual Behavior The chat bubble with the model's response gave me back an error reading, "unauthorized: unauthorized: AuthenticateToken authentication failed". I haven't tried as yet but am assuming I can work around this by clearing the token and trying again. One thing to note is that around the same time I was messing with clearing out the token on a Win10 device, so I'm not sure if this is potentially caused by roaming + merge weirdness w/ the data in Credential Manager. That could be a total red herring, but mentioning here for completeness.
claunia added the Issue-BugNeeds-Tag-FixProduct-TerminalArea-Chat labels 2026-01-31 08:19:29 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Area-Chat Issue-Bug Needs-Tag-Fix Product-Terminal
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#22647
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?