[BUG] VS Code Extension: Initial Large Prompt Hides Response

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

When using the VS Code extension, if I use larger prompts, it will often start printing the response behind the prompt window. This does not allow for scrolling to see the responses. It then requires me to prompt to trigger another response so I can see the output.

What Should Happen?

A. Make the prompt box collapsible.
B. Fire whatever you need for a new line or container that will force the response to be below the prompt box and not hidden by it.

Error Messages/Logs

Steps to Reproduce

This prompt was big enough to trigger this behavior.

/bmad-agent-dev 
Context Handoff: Fix Tests for Story 3.6 Header Updates
Branch: epic-3/app-shell-b3ddcfd4
Worktree: D:/Development/Mixify-worktrees/epic-3-app-shell-b3ddcfd4

Completed
✅ Fixed story-3.1.test.js - Changed router-link stub from true to { template: '<a><slot /></a>' } so slot content renders inside the router-link stub. All 21 tests pass.

✅ Implementation changes were already applied:

AppLayout.vue: Added clickable logo link to dashboard with data-testid="header-logo-link"
PlaylistDetailView.vue: Added artwork header, scrollable track list container
usePlaylistDetail.js: Composable already implemented
Remaining Issues
story-3.3.test.js (1 failing)

Test 3.3-COMP-002: fetchPlaylists 401 triggers redirect to connect
The test uses vi.importActual('../composables/usePlaylists.js') which bypasses the mock on ../router/index.js
Need to fix by importing the mocked router directly and checking its push method was called
story-3.6.test.js (7 failing in composable tests)

Tests 4.3, 4.5, 4.6, 4.7, 4.8, 4.9 in the usePlaylistDetail composable describe block fail
Root cause: vi.importActual bypasses the mock on ../router/index.js, so:
The 401 redirect test can't verify mockRouterPush was called
Tests checking errorStatus.value show wrong values (stale state from module-level refs)
The mock values aren't being read correctly
The Vue warnings about router-link are just warnings - component tests actually pass
Files to Modify
frontend/src/__tests__/story-3.3.test.js - fix the 401 redirect assertion
frontend/src/__tests__/story-3.6.test.js - fix composable tests to properly verify router interaction and state management
Key Pattern
Instead of:

expect(mockRouterPush).toHaveBeenCalledWith({ ... })
Use:

const router = await import('../router/index.js')
expect(router.default.push).toHaveBeenCalledWith({ ... })
Or refactor to not use vi.importActual and properly mock dependencies.

Run tests with: cd frontend && npm test -- --run

Claude Model

Sonnet (default)

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.123

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Other

Additional Information

<img width="903" height="289" alt="Image" src="https://github.com/user-attachments/assets/bc9a5bdd-b6f2-4592-a0d7-1d4110b2a70e" />