Zed installed inside WSL can no longer authenticate with Copilot

[Komposten]

Reproduction steps

• Install Zed inside WSL, using the standard installation instructions (curl -f https://zed.dev/install.sh | sh)
• Go to the LLM providers setting in Zed
• Click "Sign In" for GitHub Copilot Chat

Current vs. Expected behavior

Upon clicking "Sign In" a window pops up with an 8-character code and a button to open a link in the browser:

Clicking "Connect to GitHub" opens the browser page and the button's text changes to "Waiting for connection".

Upon authenticating Zed in the GitHub browser page, the pop-up box in Zed settings closes but GitHub Copilot Chat has not been authenticated:

I expect it to sign me in upon completing the flow in the web browser, or at the very least show an error message that can be used to figure out why it is not working. It worked last time I did it, several months ago. I only had to login again today because Zed v1.15.0 forces all GitHub Copilot Chat users to re-authenticate after updating.

Zed version and system specs

Zed: v1.15.0+stable.339.e17dc4f9d50db73a458b64dcce50ecd4878b98a3 (Zed)
OS: Linux Wayland ubuntu 24.04 (WSL profile "Ubuntu 24.04")
Memory: 15.3 GiB
Architecture: x86_64
GPU: D3D12 (NVIDIA RTX PRO 2000 Blackwell Generation Laptop GPU) || || 4.6 (Core Profile) Mesa 26.1.5 - kisak-mesa PPA

Attach Zed log file

Zed.log

2026-08-14T15:47:24+02:00 ERROR [copilot_chat] Copilot agent sign-in failed: writing Copilot agent credentials to the keychain: DBus error service error org.freedesktop.zbus.Error: The name org.freedesktop.secrets was not provided by any .service files

Relevant Zed settings

No relevant settings changed

Relevant Keymap

Key mappings are not relevant

(for AI issues) Model provider details

No response

If you are using WSL on Windows, what flavor of Linux are you using?

Ubuntu

[zed-community-bot]

This issue appears to be a duplicate of:

• Github Copilot fails to authenticate in WSL #56022

If this is indeed a duplicate:
Please close this issue and subscribe to the linked issue for updates (select "Close as not planned" → "Duplicate")

If this is a different issue:
No action needed. A maintainer will review this shortly.

Why were these issues selected?

#56022: Both issues describe GitHub Copilot authentication failing in WSL after completing the OAuth flow — the user completes the browser auth but Copilot remains unauthenticated. The new issue's log shows the exact root cause: 'writing Copilot agent credentials to the keychain: DBus error service error org.freedesktop.zbus.Error: The name org.freedesktop.secrets was not provided by any .service files'. The comments on #56022 explicitly reference this same secret service issue and a workaround involving installing a secret service provider, confirming the shared root cause.

Shared root cause: Zed cannot persist Copilot credentials in WSL because no org.freedesktop.secrets D-Bus service (e.g., gnome-keyring, kwallet) is available, causing the credential write to fail silently and leaving Copilot unauthenticated after OAuth completion.

Additional recent context for triagers

Possibly related open issues:

• Linux/Artix: URLs fail to open when launched via desktop entry (daemon lacks D-Bus/XDG session env) #58154 — Issue Linux/Artix: URLs fail to open when launched via desktop entry (daemon lacks D-Bus/XDG session env) #58154 shows the identical error line in its log: 'DBus error service error org.freedesktop.zbus.Error: The name org.freedesktop.secrets was not provided by any .service files' from crates/client/src/client.rs:391. The trigger differs (desktop entry daemon lacking D-Bus env on Artix Linux vs. WSL), but the underlying mechanism — Zed failing to access the secret service — is the same. The new issue's error comes from copilot_chat credential writing rather than Zed account auth, so there is some uncertainty about whether fixing one would fix the other.
  • Possible shared root cause: Zed's credential storage fails with the same DBus/org.freedesktop.secrets error when no secret service provider is available in the environment.

---

_{This is an automated analysis and might be incorrect.}