claude-code - 💡(How to fix) Fix [BUG] VS Code Extension: Initial Large Prompt Hides Response [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#55013Fetched 2026-05-01 05:48:30
View on GitHub
Comments
1
Participants
2
Timeline
6
Reactions
0
Timeline (top)
labeled ×5commented ×1

Error Message

Error Messages/Logs

Root Cause

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:

Code Example



---

/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
RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • 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" />

extent analysis

TL;DR

The issue can be resolved by modifying the VS Code extension to make the prompt box collapsible or to force the response to be displayed below the prompt box.

Guidance

  • The problem seems to be related to the rendering of the response in the VS Code extension, where larger prompts cause the response to be printed behind the prompt window.
  • To verify the issue, try using a smaller prompt and see if the response is displayed correctly.
  • A possible mitigation could be to limit the size of the prompt or to add a scrollbar to the response area.
  • The extension may need to be modified to handle larger prompts and responses correctly, possibly by adding a collapsible prompt box or a new line/container to force the response to be displayed below the prompt box.

Example

No code snippet is provided as the issue is related to the VS Code extension and not a specific code snippet.

Notes

The issue may be specific to the VS Code extension and the Anthropic API, and may not be a general problem with the Claude Code version 2.1.123.

Recommendation

Apply a workaround, such as limiting the size of the prompt or adding a scrollbar to the response area, until a fix is available for the VS Code extension.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING