Repository navigation
[FEATURE]: show pinned sessions in the session list when tabs are enabled #60236
Description
Feature hasn't been suggested before.
- I have verified this feature I'm about to request hasn't been suggested before.
Describe the enhancement you want to request
#39396 hid the Pinned category and the ctrl+f pin action in the session list when tabs are enabled. Only the quick slots (<leader>1-9) collide with tab keys (ctrl+1-9), not the category. Pins saved before enabling tabs stay in session.json but cannot be seen or edited. Independently, a pin outside the 50 most recent sessions disappears from the list, because the list only shows pins that are in the fetched page.
I use tabs with many sessions. I want to close tabs but keep a few sessions at the top of the session list, like favorite models in the model picker.
Proposed approach: keep the Pinned category and pin action available with tabs. Load pins that are outside the fetched page from the session store. Keep quick slots disabled with tabs and keep the existing scope and search filters.
Related closed issues: #10854 (original pin feature, completed) and #36193 (pinned session shortcuts).
An implementation PR is attached.
Activity
opencodejr commentedon Oct 29, 2026
Thanks for the request and the PR (#60237)!
To restate it: you'd like the Pinned category and the
ctrl+fpin/unpin action to stay in the session list when session tabs are on. Only the<leader>1-9quick slots would stay disabled, since they clash with the tab keys. Pinned sessions outside the loaded list would also still show up. Right now the session list deliberately hides pinning whenever tabs are on, so this is a change to how it was designed, not a bug. The maintainers will consider it.Related issues:
/sessionsbecause tabs are on by default). The workaround there is"tabs": { "mode": "off" }incli.json.sitole commentedon Oct 29, 2026
Tabs default to
autoinpackages/tui/src/config/index.tsx, which enables them unlessHERDR_ENV=1. Default installs therefore cannot reach the Pinned section or the documentedctrl+fkeybind. Existing pins insession.jsonare unreachable. #52794 reports this symptom.The PR keeps quick slots off under tabs, so there is no keybind conflict. This is why I think pinning belongs in the list dialog: plugins cannot extend built-in dialogs either (#57938).