Chat: Unsent (draft) input should not surface when navigating back to the session list
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- typescript
- Domain
- frontend
Research direction
Reproduce the issue in the Chat UI by entering unsent text, navigating back to the session list, and re-entering the session. Trace the session-list navigation and chat input state to identify where the draft becomes visible; done means the draft is hidden at the list level and restored unchanged in its original session.
Written by the indexing model from the issue text.
Description
Describe the behavior you'd like:
When I have unsent/draft text in a chat session's input box and navigate "back" to the session list (the panel that lists all chat sessions), the draft text should remain scoped to that session — it should not appear or carry over at the session-list level.
When I re-enter that specific session, the draft text should be restored as expected.
Current behavior:
Navigating back to the session list exposes or interacts with the unsent input in a way that feels like the draft is "leaking" out of its session context.
Expected behavior:
Draft input is strictly scoped to its session
Navigating up to the session list: draft is hidden / not surfaced
Re-entering the session: draft is restored exactly as left
Why this matters:
When managing multiple chat sessions, navigating between them or starting a new session from the list should be a clean action. Unsent content from a previous session creates confusion about which session's context is active.
Environment:
VS Code version: (fill in)
OS: macOS
Extension: GitHub Copilot Chat
- 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 ·