Allow pinning/unpinning Copilot Chat sessions from within the session itself
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 58/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- typescript
Research direction
The issue names no files or tests; start by locating the existing pin/unpin action in the chat session list and tracing how the active session view and command palette expose actions. Done means the current session can be pinned or unpinned without leaving the session, with the action reflecting its current state.
Written by the indexing model from the issue text.
Description
Feature Request
Is your feature request related to a problem?
Currently, pinning and unpinning chat sessions can only be done from the session list view. If I'm actively working within a session and want to pin it (to preserve it), I have to navigate away to the session list, find the session, and pin it from there. This breaks my flow.
Describe the solution you'd like
Add a pin/unpin action accessible from within an active chat session — for example, as an icon button in the session header/toolbar, or as a command palette entry (e.g., "Chat: Pin Current Session" / "Chat: Unpin Current Session"). This would allow users to pin or unpin the session they're currently viewing without leaving it.
Describe alternatives you've considered
- Navigating to the session list to pin/unpin (current behavior — requires context switching)
- Using the command palette to pin by session name (doesn't exist currently)
Additional context
This is a small UX improvement that reduces friction for users who frequently pin sessions to keep important context available.
- Dominant language
- TypeScript
- Stars
- 193k
- Forks
- 42.9k
- PR merge metrics
- PR metrics pending
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/vscode
-
testplan-item
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
new release
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
testplan-item
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
testplan-item
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
All issues in microsoft/vscode
Similar issues
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 76/100
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
vercel/react-tweet#225 ·