Top-Ranking Issues (All Time) 📊

[JosephTLyons]

Updated on 05/22/2025 08:17 PM (EDT)

feature

1. Rainbow brackets #5259 (791 👍)
2. Codeium support #4726 (718 👍)
3. Test runner integration #5242 (418 👍)
4. Telescope-style search box #8279 (363 👍)
5. Support using ollama as an inline_completion_provider #15968 (321 👍)
6. Which-Key like menu #10910 (317 👍)
7. Add build time options to disable ML/AI features #6756 (241 👍)
8. Option to combine the tabs-bar into the titlebar #5066 (238 👍)
9. Make the Python experience wonderful #7808 (234 👍)
10. Add options to hide title and status bar #5120 (229 👍)
11. easymotion vim #4930 (228 👍)
12. Highlighting of special code comment types like TODO, INFO, etc. #11895 (185 👍)
13. Smooth scrolling #4355 (175 👍)
14. AI Assistant should have embedding context of the entire codebase #15924 (171 👍)
15. Support LSP Semantic Tokens #7450 (162 👍)
16. Pretty TypeScript errors #7844 (159 👍)
17. Git conflict highlighting/resolution #4964 (152 👍)
18. Code completion icons #4943 (133 👍)
19. "Smooth Caret" animation #4688 (132 👍)
20. Selection-first modal editing (like Kakoune, Helix editors - alternative to "vim mode") #4888 (127 👍)
21. Mermaid diagram rendering in Markdown preview #10696 (116 👍)
22. Support Difftastic for visualizing code diffs #9721 (112 👍)
23. Support opening .code-workspace files to open vs code type workspace directly #9459 (111 👍)
24. Flash.nvim style search in a document. #14801 (109 👍)
25. iOS support for iPad #11889 (107 👍)
26. Zen mode #4382 (91 👍)
27. Allow add custom AI assistant provider #15732 (83 👍)
28. Support for quarto's .qmd file format #12406 (81 👍)
29. can we have this app in flathub and snapstore #9922 (78 👍)
30. Support per-file tab (indentation) settings: tab_size, hard_tabs #4867 (77 👍)
31. Indentation conversion (tabs to spaces; spaces to tabs) #4291 (76 👍)
32. Drag tab to open new window #6722 (75 👍)
33. org-mode support #11138 (75 👍)
34. Add support for Tabnine #4504 (74 👍)
35. Better comments #4808 (69 👍)
36. Custom inline completion providers #18490 (69 👍)
37. User configurable mouse bindings (like keymap for key+mouse) #10647 (68 👍)
38. Webview via Extensions #21208 (66 👍)
39. Serialize the unsaved changes of files not associated with a worktrees #15098 (63 👍)
40. Implement kinetic / inertial scrolling for Linux (Wayland) #14473 (61 👍)
41. Implement file history viewing, including local and Git. #16827 (58 👍)
42. [Linux] Add option to disable client side decoration / enable native titlebar #14165 (57 👍)
43. Add support for jj SCM #21538 (57 👍)
44. Allow to hide the thought process of "thinking" models in the assistant panel #22373 (57 👍)
45. Better tab/buffer switcher a'la harpoon for when working without tabs #17353 (56 👍)
46. Add Flutter hot reload on save action #11107 (54 👍)
47. Assistant: render markdown inside assistant panel.  #15862 (52 👍)
48. [Feature] Tabless editing #6424 (51 👍)
49. Collapse folder in file explorer discoverability #6880 (50 👍)
50. Support code completion with Tabby #4421 (48 👍)

bug

1. Font rendering on LoDPI displays #7992 (315 👍)
2. Zed downloads NodeJS binary and npm packages from Internet without user’s consent #12589 (115 👍)
3. Fonts are blurry (Windows 11) #14113 (80 👍)
4. Linux Shortcuts don't work with non-latin / international keyboard layouts #14053 (58 👍)
5. Only some ligatures are being applied #12176 (56 👍)
6. GPUI overdraws too much #8043 (52 👍)
7. Prioritize exact matches in autocompletions #12698 (48 👍)
8. Zed not respecting tab size when saving file #4842 (34 👍)
9. blade: Text is rendered either too thick or too thin #13564 (33 👍)
10. linux: Keyboard shortcuts do not work on non-English keyboard layout #10972 (30 👍)
11. Surround with quotes does not work when using a keyboard layout that uses dead keys #13838 (29 👍)
12. Terminal input is slow #18263 (28 👍)
13. Project panel directory closes when installing project dependencies #13762 (27 👍)
14. pylsp running very slowly #21076 (27 👍)
15. Zed Python doesn't detect multiple venvs in project #20402 (26 👍)
16. Search project symbols not working on _python_ project #16749 (25 👍)
17. [linux] Vulkan ERROR_INITIALIZATION_FAILED #8168 (24 👍)
18. Zed refuses to use GPU (Nvidia) WSL 2 #15295 (24 👍)
19. Zed uses lot of RAM #18673 (23 👍)
20. Dark Text on Light Background is Rendered Weirdly #19100 (23 👍)
21. Leading slash with env::current_dir() in Windows #20559 (23 👍)
22. Incorrect spacing of terminal font #11744 (22 👍)
23. Cannot uninstall extension on windows #18153 (21 👍)
24. Characters spacing a bit too large #7621 (20 👍)
25. Downloaded C# OmniSharp language server does not start #8352 (20 👍)
26. JavaScript runnables expect to run Jest in every environment #12828 (20 👍)
27. Last manually-closed workspace reopens on Zed startup #7759 (19 👍)
28. unable to view eslint errors in the editor #13461 (19 👍)
29. inline code completion frequently leaves a {{INSERTED_CODE}} artifact at the top of the inserted code #19471 (19 👍)
30. LSP quickfix code actions fail to execute #19834 (19 👍)
31. C# Extension - Go to Definition opens blank file #11104 (17 👍)
32. Turning off soft wrap via command doesn't really work properly #13286 (17 👍)
33. Extremely high GPU usage with nothing open on Linux #14074 (16 👍)
34. Regression: TypeScript with Yarn PnP configuration not working in Zed v0.154.2 #18410 (16 👍)
35. copy paste not working on the latest linux update #20984 (16 👍)
36. Go to definition sometimes opens a new tab "Definitions for X" with a single snippet instead of actually going to the definition #6730 (15 👍)
37. gopls: packages.load error: JSON decoding failed : invalid character 'x' in string escape code  #11647 (15 👍)
38. Text rendering seems too thick #12835 (15 👍)
39. Zed is slow to start on linux #14222 (14 👍)
40. GPUI window resizes are very slow on Linux #15311 (14 👍)
41. Copilot autocomplete is ignored when there are trailing lines in a document, and no characters present on the line of the suggestion. The tab key inserts spaces instead #4549 (14 👍)
42. format_on_save does not work with autosave #16588 (13 👍)
43. Selecting New Model doesn't do anything. #17118 (13 👍)
44. [WINDOWS] Most LSPs give error: "Cannot read LSP message header" #12013 (12 👍)
45. High cpu usage on idle #14833 (12 👍)
46. Cannot type Japanese with Google Japanese IME #15409 (12 👍)
47. Cannot use fonts installed with home-manager #18982 (12 👍)
48. Python config: terminal.detect_venv.activate_script default should detect user's shell #11246 (11 👍)
49. Excessive display server repaints from missing damage/present regions #15166 (11 👍)
50. rust-analyzer: Failed to load workspaces. #21762 (11 👍)

meta

1. Make the Python experience wonderful #7808 (234 👍)
2. Zed Offline Support (Meta Tracking Issue) #24878 (64 👍)
3. Better Support LSP features / spec (Meta Tracking Issue) #26916 (21 👍)
4. Tracking - Linux non-QWERTY keyboard support #25469 (19 👍)
5. Python issues in Zed (Meta tracking issue) #26754 (11 👍)
6. Linux Mouse Cursor Problems (Meta Tracking Issue) #26141 (8 👍)
7. Audit and document Zed network connections #24804 (7 👍)
8. UI implications of hidden tabs #23930 (6 👍)
9. Tracking - Vim anybracket issues/inconsistencies #25560 (4 👍)
10. UI & Theme Contrast #23914 (2 👍)
11. Popover UI layering problems #23917 (0 👍)
12. Keyboard-First Picker (Meta Tracking Issue) #26202 (0 👍)
13. Improve flake.nix #26277 (0 👍)

unlabeled

1. assistant:InlineAssist is always: failed to stream completion. #28958 (17 👍)
2. python .venvs not recognized in nested directories #27331 (14 👍)
3. Zed Crashes When Loading Django-Templates Grammar #29827 (14 👍)
4. format_on_save is ignored when saving a remote YAML file #23489 (13 👍)
5. Permalinks support enterprise git repository with custom root domain #23103 (12 👍)
6. Python virtual environment dropdown does not work #29807 (12 👍)
7. The entire UI is too low contrast, no matter which theme I choose. #30780 (12 👍)
8. editor fails to pick python .venv correctly or accept the path when entered. #30135 (11 👍)
9. Language server logs not showing up in remote development #28557 (10 👍)
10. Failed to detect Python venv correctly #29323 (10 👍)
11. Add shortcuts for answering dialogs #23106 (9 👍)
12. Hotkeys not working on Ubuntu 20.04 when Cyrillic locale is used #24499 (9 👍)
13. Expanding Syntax Highlighting Customization #23277 (8 👍)
14. Zed doesn't have graphical acceleration, and errors about this on startup - Tegra X1 L4T #27741 (8 👍)
15. Disable border in centered layout #22971 (7 👍)
16. Different color / font for AI and user text #23676 (7 👍)
17. Git Blame links to wrong PR #25044 (7 👍)
18. Error when trying to format on save using Prettier #26882 (7 👍)
19. ESLint is a major version behind (with consequences) #29757 (7 👍)
20. Yanking and pasting in vim mode will automatically switch back to normal mode #26859 (6 👍)
21. Tailwind autocomplete stopped working in ERB tags #27118 (6 👍)
22. Can't manually add python venv path #27332 (6 👍)
23. Inline code folding display issues #28679 (6 👍)
24. AI autocomplete breaks context menu completion #22925 (5 👍)
25. LINUX | Signature help in completion doesn't render consistently #23692 (5 👍)
26. Zed conflates tab_width and indent_size in editorconfig #24108 (5 👍)
27. Broken image in browser support info for CSS features #28266 (5 👍)
28. Format not working on Rust files #29300 (5 👍)
29. Prisma Language Server crash on startup #30767 (5 👍)
30. vim:repeat doesn't repeat completions well #30758 (5 👍)
31. No way to configure the minimap's font-size and width. #31141 (5 👍)
32. close diagnostics buffer when empty #22986 (4 👍)
33. Nested outline for (javascript) functions  #23075 (4 👍)
34. Updating to v0.168.2 breaks GPU support on Linux #23057 (4 👍)
35. remove_trailing_whitespace_on_save shouldn't remove whitespace in string literal #23126 (4 👍)
36. Automatically convert strings with template expressions into template strings #23232 (4 👍)
37. Add editor::ToggleAllFold #23397 (4 👍)
38. Zed grab all shortcuts even if terminal is focussed #26018 (4 👍)
39. Option to auto-close deleted files with no unsaved edits #27982 (4 👍)
40. Crash in gpui X11 when running with custom display #28385 (4 👍)
41. Vim mode: Go To Definition only adds to jumplist if the jump is 10 lines or more #30183 (4 👍)
42. Frequent Disconnects / Doesn't automatically reconnect #30272 (4 👍)
43. Populate Outline Panel from language server textDocument/documentSymbol #23095 (3 👍)
44. changing pwsh through terminal->shell->program setting on windows to new powershell causes a panic on launch #23872 (3 👍)
45. Wrong keyboard behavior on Windows #28351 (3 👍)
46. Highlight looks identical for selected and unselected find results #28617 (3 👍)
47. Sign in error #28932 (3 👍)
48. [Linux] Open File/Folder dialog appears in background #29655 (3 👍)
49. Using Git Panel to initialise new repository doesn't populate available branches #30214 (3 👍)
50. Zed opens large dirs much slower than VS Code/Sublime (hanging for 5 minutes) #30466 (3 👍)

crash

1. crash after compile on windows minigw #13575 (14 👍)
2. Crash on linux: Aquire image error ERROR_SURFACE_LOST_KHR #14225 (10 👍)
3. Zed won't even start on Linux for me anymore. #18573 (4 👍)
4. Ruff extension: language server error #19408 (3 👍)
5. Excessive memory consumption on project search with large files present #20970 (3 👍)
6. unable to run zed error info Instance extension "VK_KHR_get_physical_device_properties2" is not supported. #17598 (2 👍)
7. unresponsive on startup checking for update #19699 (1 👍)
8. Panics on first start with flatpak #20014 (1 👍)
9. Linux: Zed causes brief system freezes when opening new windows #22320 (1 👍)
10. Panic when pasting /default context over full selection #22675 (0 👍)
11. [Linux] Toggle back full-screen crash window [F11] #16117 (0 👍)
12. Snippet with nested location with same order [gif inside] #22157 (0 👍)

---

For details on how this issue is generated, see the script

[exalted]

:two-cents: You'll know better, but a GitHub project sounds like a better solution.

[JosephTLyons]

:two-cents: You'll know better, but a GitHub project sounds like a better solution.

It would be nice to have something that is more directly supported by GitHub with less custom code involved, but I don't know if GitHub Projects support sorting on the fields I need. I checked it out and wasn't able to find a way to sort on reactions and comments and such. You can create custom fields in the project table, but you'd have to manually update those, or write another script to tap into them. I'm not sure what the best solution is for generating a list like this - this is just my first attempt.

[maxbrunsfeld]

This is very cool @JosephTLyons; thanks for setting it up.

[JosephTLyons]

This is very cool @JosephTLyons; thanks for setting it up.

Yeah no problem

I'm currently running it manually; I don't have any experience with GitHub actions and I don't know want to assume there are enough Action Minutes to go around, but if I spent some time to learn it and if there were enough minutes to spare, I could try to automate it to run once a day.

I've done my best to optimize the script, it still takes about 5 seconds to run it because I can't seem to find a way to limit the query size using the GitHub Search syntax, so even though I only display 5 items per label, I have to pull all open issues per label and slice the list down to size locally.

[clo4]

I have to pull all open issues per label and slice the list down to size locally

@JosephTLyons I think you should be able to use ?per_page=5 in the query, eg. https://api.github.com/search/issues?per_page=5&q=... -- I've had to fight the API to get more than 100 issues for the fig support dashboard 😄

Also, should be possible to do this concurrently - if the script is public, I'd be happy to optimize it :)

It can probably just run in a repo on your user account, using a gh actions schedule. If the repo is public, you don't need to worry about it using up your minutes!

[JosephTLyons]

I have to pull all open issues per label and slice the list down to size locally

@JosephTLyons I think you should be able to use ?per_page=5 in the query, eg. https://api.github.com/search/issues?per_page=5&q=... -- I've had to fight the API to get more than 100 issues for the fig support dashboard 😄

Also, should be possible to do this concurrently - if the script is public, I'd be happy to optimize it :)

It can probably just run in a repo on your user account, using a gh actions schedule. If the repo is public, you don't need to worry about it using up your minutes!

I'm currently using PyGitHub in a Python script. I haven't found how to limit the results using it, as the search uses the search syntax that you have on the frontend on the issues page. I probably missed something, but I felt like I couldn't get the "per_page" filter (or any other limit to the final query) to work there:

https://github.com/zed-industries/feedback/blob/347ecc15c8b0f4f696d91075f9d9f2f558cad5d0/scripts/update_top_ranking_issues/main.py#L41

[JosephTLyons]

Need some opinions here. Previously, I was just skipping all issues with these tags ("discussed", "meta", "needs info", "triage"}, as these type of labels are just optional ones; all issues with these labels have other "core" labels that are required.
We are adding more more labels now and it seems issues can now have multiple "core" labels, which means issues can end up in multiple label groups in the generated markdown above. I'm not sure how to handle this. I could either filter out duplicate issues, but this would be a bit misleading, since issues would just not show up in places they technically should, or maybe I just get rid of the label exclusion list all together and allow all duplicates to surface in all label groups, but this would probably result in a bunch of noise.

Until I get some feedback on this, I will just generate the list assuming that all issues will at least have one of the following labels: "enhancement", "defect", "polish, and "documentation".

[iamnbutler]

Honestly, tags will probably be fast and loose for a bit while we figure out how to parse feedback.

In the coming few weeks the fire hose will probably open up a lot, as I think we'll be increasing the amount of people with access by triple digits.

Suggestions are welcome for a framework to organize/parse feedback.

[JosephTLyons]

Honestly, tags will probably be fast and loose for a bit while we figure out how to parse feedback.

In the coming few weeks the fire hose will probably open up a lot, as I think we'll be increasing the amount of people with access by triple digits.

Suggestions are welcome for a framework to organize/parse feedback.

Yeah, this was just something I tossed together randomly without much thought; if it ends up not working with however the repository is ultimately organized, it can be tossed.

[JosephTLyons]

This issue should be auto-generating now, every 12 hours UTC (the cron scheduler can't be set to any timezone specifically). I also set it to rebuild after issues close. Feel free to change the triggers, cron schedule, or timezones in the script to your liking.

[JosephTLyons]

I'm thinking it might make sense to remove comments from the sorting mechanism. With likes, users can only add one, and no one can change the creation datetime, but anyone can comment multiple times to boost the issue up (to the top of the group of issues with the same number of likes). I'm thinking just likes and creation datetime is enough to stabilize the sort and prevent others from artificially boosting an issue's importance. It also might help to reduce some of the noise in this issue. Let me know what you think about this.

As a note, I did experiment with having the script generate a table, to reduce the amount of repeated emojis showing, but GitHub does not render the dynamic issue links (the ones that show the name of the issue and whether its closed or open) inside of markdown tables, so that idea was tossed.

[jamesmunns]

Hey there! Apologies if this is off-topic, is there somewhere I can 👍 linux support as a blocking issue? I do have a Mac, but don't use it as a primary development machine, which means that I probably won't have a chance to test out Zed until there is some kind of Linux client.

I can open an issue, but it seems explicitly documented that is a WIP feature :)

[JosephTLyons]

Hey there! Apologies if this is off-topic, is there somewhere I can 👍 linux support as a blocking issue? I do have a Mac, but don't use it as a primary development machine, which means that I probably won't have a chance to test out Zed until there is some kind of Linux client.

I can open an issue, but it seems explicitly documented that is a WIP feature :)

Sure, I went ahead and made a meta issue here:

• https://github.com/zed-industries/feedback/issues/174