Skip to content

Commit 1950a4c

Browse files
committed
docs: stop promising top placement for a fresh thread pin
Environments without pin reordering keep keyless pins in newest-first order below arranged ones, so an older thread pinned there lands below newer pins. Point at the sidebar doc, which already owns those rules.
1 parent 0b7a09f commit 1950a4c

1 file changed

Lines changed: 3 additions & 3 deletions

File tree

‎docs/user/keybindings.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -55,9 +55,9 @@ so add one in **Settings** → **Keybindings** if you want to use it.
5555
`thread.settle` settles the active thread or restores it when it is already settled. Its default
5656
shortcut is `mod+shift+s`, and it does not run while the terminal has focus.
5757

58-
`thread.pin` pins the active thread to the top of the sidebar, or unpins it when it is already
59-
pinned. A fresh pin lands at the top of the pinned list. Its default shortcut is `mod+shift+p`, and
60-
it does not run while the terminal has focus.
58+
`thread.pin` pins the active thread to the pinned section of the sidebar, or unpins it when it is
59+
already pinned. Its default shortcut is `mod+shift+p`, and it does not run while the terminal has
60+
focus. See [Organizing threads](./thread-sidebar.md) for how pinned threads are ordered.
6161

6262
The command palette searches active thread titles, projects, branches, user messages, and final
6363
agent responses across connected environments. Message matches show one labeled excerpt while

0 commit comments

Comments
 (0)