-
Notifications
You must be signed in to change notification settings - Fork 3.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Supermaven stuck in "Supermaven initializing" and not downloading binary #15653
Comments
I was able to solve it deleting the folder It took some time to Zed to download the Sueprmaven binary, so I think it's a good idea to wait for a few minutes before trying. You can check the download in the I'm on macOS Sonoma. |
Did a similar thing on Debian Linux, and it worked. |
Some recent update fixed it for me. |
any one got this working? i already added
to my config, but nothing happened, i don't get any new icon or any initializing message Please help |
closing since it's working for me now. |
It's really not working for me |
What OS are you using and did you delete the Supermaven folder? |
On my side it works ONCE if I delete both After each restart of Zed however, the Supermaven plugin is again stuck on initializing and have delete again all the folders. |
In my case, this issue was resolved with the latest update. macOS Sequoia Developer Beta |
none of the solutions in this thread has worked for me nixos 24.05, zed 0.155.2 |
I can get stuck in “Supermaven initializing” in a reproducible way:
To get Supermaven working again:
|
@omegaatt36 's solution is the only thing that worked for me. I'm on Arch Linux. It appears the 'supermaven' folder isn't created with sufficient permissions for 'sm-agent-26' to get downloaded into it. |
@quinncomendant 's solution works for one reboot, and then if I quit and restart Zed, I get stuck again. MacOS Sequoia 15.1.1, Apple Silicon (M4 Pro), Zed 0.166.1 |
The problem that occurs on Macs is that the Supermaven configuration file is marked as “downloaded from the internet”, that means the config.json file is marked with the special attribute “com.apple.provenance”. You can check it with this command in the terminal: It is solved by removing the attribute from the terminal and restarting Zed: |
Closing zed and deleting:
|
➜ ~ xattr -l .supermaven/config.json
com.apple.provenance:
➜ ~ xattr -d com.apple.provenance .supermaven/config.json
➜ ~ xattr -l .supermaven/config.json
com.apple.provenance: In my case looks like this key has no value and so deleting it does nothing. Also does not solve the issue for me. |
Check for existing issues
Describe the bug / provide steps to reproduce it
When installing a fresh version of Zed Preview and enabling "supermaven"
The status stays on "Supermaven initializing" and it won't download the required binaries sm-agent binary.
My
~/.supermaven/config.json
is also present and I'm on the paid plan:{"api_key":"XXX","api_key_obtained_at":"XXX","link_id":"XXX","machine_id":"XXX"}
There is no Zed Log information about supermaven and why it might fail whatsoever.
Environment
Zed: v0.147.1 (Zed Preview)
OS: macOS 15.0.0
Memory: 16 GiB
Architecture: aarch64
If applicable, add mockups / screenshots to help explain present your vision of the feature
If applicable, attach your Zed.log file to this issue.
Zed.log
The text was updated successfully, but these errors were encountered: