aws / aws/aws-toolkit-vscode

If I click move the Amazon Q Panel to a secondary side panel, it loses all context in the current chat and will not let me reopen it.

Open
#7,590 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
2k
Forks
807
Avg merge
10h 12m
Merged PRs (30d)
7

Description

Type: Bug

Bug Report: Chat Context Lost When Moving Amazon Q Panel
Summary
Amazon Q chat loses all conversation context and history when the panel is moved to a different position in the IDE, making previous conversations inaccessible.

Steps to Reproduce
Open Amazon Q chat panel in IDE

Start a new conversation with Amazon Q

Have Amazon Q perform one or more actions (file operations, code generation, etc.)

Right-click on the Amazon Q panel and select "Move" option

Move the panel to a different position (e.g., from sidebar to bottom panel)

Observe that the chat interface appears blank/reset

Attempt to access previous chat from history sidebar

Expected Behavior
Chat context and conversation history should persist when panel is moved

Previous conversations should remain accessible from chat history

All performed actions and their results should still be visible

Actual Behavior
Chat panel appears completely reset after moving

All previous conversation context is lost

Chat history shows previous conversations but selecting them doesn't restore content

No way to recover the lost conversation or context

Impact
Severity: High - Complete loss of work context

Frequency: Reproducible every time panel is moved

Workaround: None - context cannot be recovered

Operating System: macOS

Workspace: Active project workspace

Additional Notes
This appears to be a state management issue where the panel relocation triggers a complete reinitialization of the chat component, clearing all stored conversation data.

Extension version: 1.79.0
VS Code version: Code 1.101.2 (2901c5ac6db8a986a5666c3af51ff804d05af0d4, 2025-06-24T20:27:15.391Z)
OS version: Darwin arm64 24.5.0
Modes:

System Info

|Item|Value|
|---|---|
|CPUs|Apple M3 Pro (11 x 2400)|
|GPU Status|2d_canvas: enabled
canvas_oop_rasterization: enabled_on
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_graphite: enabled_on
video_decode: enabled
video_encode: enabled
webgl: enabled
webgl2: enabled
webgpu: enabled
webnn: disabled_off|
|Load (avg)|3, 4, 4|
|Memory (System)|18.00GB (0.11GB free)|
|Process Argv|--crash-reporter-id 2a45da57-da8e-4f66-8d21-50cea47e2fcc|
|Screen Reader|yes|
|VM|0%|

A/B Experiments

```
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492:30256859
vscod805:30301674
binariesv615:30325510
c4g48928:30535728
azure-dev_surveyone:30548225
962ge761:30959799
2e7ec940:31000449
pythontbext0:30879054
cppperfnew:31000557
dwnewjupyter:31046869
pythonrstrctxt:31112756
nativeloc2:31192216
5fd0e150:31155592
dwcopilot:31170013
6074i472:31201624
dwoutputs:31242946
customenabled:31248079
9064b325:31222308
copilot_t_ci:31333650
e5gg6876:31282496
pythoneinst12:31285622
bgtreat:31268568
4gafe986:31271826
c7cif404:31314491
pythonpulldiagcf:31335740
7bh79656:31259953
996jf627:31283433
pythonrdcb7:31303018
usemplatestapi:31297334
0aa6g176:31307128
7bj51361:31289155
747dc170:31275177
6518g693:31334701
aj953862:31281341
generatesymbolt:31295002
convertfstringf:31295003
j6a0c355:31339598
0g0a1943:31338100
i851h500:31338111
usemarketplace:31336439
nesew2to5:31336538
agentclaude:31335814
nes-diff-11:31337487
nes-set-on:31339175
6abeh943:31336334
yijiwantestdri0626-c:31336931
hi92a955:31337023

```

Contributor guide

Open the contributing guide

Research direction

The report names no files, tests, or entry points. First reproduce the panel move on macOS with the reported Amazon Q and VS Code versions, then trace what is reinitialized when the panel changes position. Done means the active chat, history, actions, and results remain accessible after moving the panel.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript, vscode
Domain
ai, devtools
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.