File explorer removed and /snippet command broken — snippet workflows now harder
#5674
JohnGluck
started this conversation in
Feature Requests
Replies: 1 comment 1 reply
-
|
Hey @JohnGluck I'm one of the engineers working on the Editor. We are restoring the File explorer feature this week. We recently released a Live collaboration feature and removed the file tree due to complexity without looking at usage numbers. Apologies for the disruption of your workflow |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
The updated web editor has two issues that together make snippet-heavy workflows significantly harder:
The file explorer is gone. Without the file tree, there's no way to browse the snippets folder to find and reference snippet files. What used to be a two-step process is now four steps.
The
/snippetcommand doesn't work. This was presumably the intended replacement for file tree navigation, but it doesn't function in the current editor.For projects that rely heavily on snippets for content reuse, these two issues compound each other. There's no working path to snippet insertion short of manually remembering or looking up file paths elsewhere.
Your January 2026 blog post on the improved editor described the ability to "still see it as a file tree" — if that toggle still exists, it's not surfaced in the current UI.
Requesting:
/snippetcommand, or restore the file tree, or both/snippetis the intended path forward, it needs to be reliably functional before removing the file treeBeta Was this translation helpful? Give feedback.
All reactions