You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[FEATURE]: Bring back the original left sidebar / Option to disable top navbar sessions #48972
I have verified this feature I''m about to request hasn''t been suggested before.
Describe the enhancement you want to request
I am writing to urgently request an option to restore the original left sidebar layout for project and session management. Currently, I am managing 14 active projects with 4 to 5 open sessions each. Forcing these sessions into a top navbar makes it impossible to work efficiently. The top navbar lacks the vertical screen real estate required to display this many concurrent items, leading to severe clutter and a highly degraded user experience. While I understand the drive for UI modernization, a top navbar simply does not scale for power users with heavy multitasking workflows. Please consider adding a toggle setting to move sessions back to a traditional vertical left sidebar. Thank you for your time and for your continuous work on the editor.
Related issues
Possibly related: #48882, #48956, #48966, #48802, #37012, #36942. Keeping this one open for the power-user scaling angle (14 active projects x 4-5 sessions each do not fit a top tab strip).
Reacted by German Gimenez, Florian Buenzli, Witold Brzozowski, Killerbee440, Kirill Lebedinov, Zhell, Alberto G. Rodriguez, dasebinox, Vlad L. and Daniel Hillmann
Feature requests must use the Feature Request template, which requires a title starting with [FEATURE]: and a verification checkbox confirming you've searched for existing issues.
Please edit this issue to address the above within 2 hours, or it will be automatically closed.
This issue might be a duplicate of existing issues. Please check:
changed the title [-]Feature Request: Bring back the original left sidebar / Option to disable top navbar sessions[/-][+][FEATURE]: Bring back the original left sidebar / Option to disable top navbar sessions[/+]on Sep 14, 2026
Thank you for updating your issue! It now meets our contributing guidelines. We appreciate the clear description of your use case. Your request has been noted.
If you fork a version prior to the removal of the V1 layout then you can find the following variable in the settings.tsx: export const oldInterfaceSunset = new Date(2026, 8, 14)
That is what made it so the old interface toggle disappeared from the settings (it's a zero-based month) and you can just set that date to something way in the future (I set mine to 2099) and then re-build the source and voila your toggle will be back.
Activity
github-actions commentedon Sep 14, 2026
This issue doesn't fully meet our contributing guidelines.
What needs to be fixed:
[FEATURE]:and a verification checkbox confirming you've searched for existing issues.Please edit this issue to address the above within 2 hours, or it will be automatically closed.
This issue might be a duplicate of existing issues. Please check:
If you believe this was flagged incorrectly, please let a maintainer know.
[-]Feature Request: Bring back the original left sidebar / Option to disable top navbar sessions[/-][+][FEATURE]: Bring back the original left sidebar / Option to disable top navbar sessions[/+]github-actions commentedon Sep 14, 2026
Thank you for updating your issue! It now meets our contributing guidelines. We appreciate the clear description of your use case. Your request has been noted.
aithos commentedon Sep 14, 2026
If you fork a version prior to the removal of the V1 layout then you can find the following variable in the settings.tsx:
export const oldInterfaceSunset = new Date(2026, 8, 14)That is what made it so the old interface toggle disappeared from the settings (it's a zero-based month) and you can just set that date to something way in the future (I set mine to 2099) and then re-build the source and voila your toggle will be back.
aa2013 commentedon Sep 14, 2026
#48882 (comment)
Tarquinen commentedon Oct 20, 2026
We're tracking this in #48882, so I'm closing this as a duplicate. Please follow that issue for updates.
— from 𝕺𝖕𝖊𝖓𝕮𝖔𝖉𝖊