Skip to content

Continue panel gets cropped/cut off in VSCodium sidebar #13055

Open

Description

@carlosrodan

Before submitting your bug report

Relevant environment info

- OS: Fedora
- Continue version: 2.0.0 (extension)
- IDE version: VSCodium 1.126.04524
- Model: DeepSeek Coder

Description

Image Image

When the side panel is narrow the contents of the Continue extension get cropped. Resizing the window to make it wider solves the issue. I have the impression there is some kind of CSS limit (min width) somewhere. I've uploaded two screenshots, one with the side panel taking up roughtly half of my scren (1920px) where everything is visble and another one, narrower with the contents cut off.

I tried the following commands without success on VSCodium:
"Developer: Reload Window"
"View: Reset Zoom"
"View: Reset View Locations"

To reproduce

  1. Install VSCodium
  2. Install Continue Extensions V2.0.0
  3. Open the side panel
  4. Resize the side panel

Log output

INFO Started local extension host with pid 16677.
workbench.desktop.main.js:sourcemap:38  INFO [Continue.continue]: Command `continue.focusContinueInput` already registered by Continue - open-source AI code agent (Continue.continue)
workbench.desktop.main.js:sourcemap:5057 Unrecognized feature: 'local-network-access'.
_createElement @ workbench.desktop.main.js:sourcemap:5057
workbench.desktop.main.js:sourcemap:5057 An iframe which has both allow-scripts and allow-same-origin for its sandbox attribute can escape its sandboxing.
mountTo @ workbench.desktop.main.js:sourcemap:5057
workbench.desktop.main.js:sourcemap:38  INFO [AccountPolicyGate] apply: state=inactive, reason=undefined, isRestricted=false
workbench.desktop.main.js:sourcemap:38  INFO Auto updating outdated extensions. anthropic.claude-code
workbench.desktop.main.js:sourcemap:38  INFO [perf] Render performance baseline is 60ms
workbench.desktop.main.js:sourcemap:38   ERR [Extension Host] Failed to register Continue config.yaml schema, most likely, YAML extension is not installed CodeExpectedError: Unable to write to User Settings because yaml.schemas is not a registered configuration.
    at b8t.toConfigurationEditingError (vscode-file://vscode-app/usr/share/codium/resources/app/out/vs/workbench/workbench.desktop.main.js:4684:8353)
    at b8t.validate (vscode-file://vscode-app/usr/share/codium/resources/app/out/vs/workbench/workbench.desktop.main.js:4684:11133)
    at b8t.doWriteConfiguration (vscode-file://vscode-app/usr/share/codium/resources/app/out/vs/workbench/workbench.desktop.main.js:4684:4722)
    at Object.factory (vscode-file://vscode-app/usr/share/codium/resources/app/out/vs/workbench/workbench.desktop.main.js:4684:4578)
    at Ly.consume (vscode-file://vscode-app/usr/share/codium/resources/app/out/vs/workbench/workbench.desktop.main.js:30:78400)
    at vscode-file://vscode-app/usr/share/codium/resources/app/out/vs/workbench/workbench.desktop.main.js:30:78215
    at new Promise (<anonymous>)
    at Ly.queue (vscode-file://vscode-app/usr/share/codium/resources/app/out/vs/workbench/workbench.desktop.main.js:30:78139)
    at b8t.writeConfiguration (vscode-file://vscode-app/usr/share/codium/resources/app/out/vs/workbench/workbench.desktop.main.js:4684:4547)
    at wfo.writeConfigurationValue (vscode-file://vscode-app/usr/share/codium/resources/app/out/vs/workbench/workbench.desktop.main.js:4684:61687)
    at async Promise.all (index 0)
    at async Object.e [as settled] (vscode-file://vscode-app/usr/share/codium/resources/app/out/vs/workbench/workbench.desktop.main.js:30:85669)
    at async wfo.updateValue (vscode-file://vscode-app/usr/share/codium/resources/app/out/vs/workbench/workbench.desktop.main.js:4684:44632)

Activity

  1. bluemoehre commented on Aug 1, 2026

    @bluemoehre

    I can confirm this using:

    VSCode
    Version: 1.131.0 (system setup)
    Commit: e4c7e7b1d6d060162f4aa7f8225271b67ce1df75
    Date: 2026-07-28T10:51:25Z
    Electron: 42.7.0
    ElectronBuildId: 14710161
    Chromium: 148.0.7778.280
    Node.js: 24.18.0
    V8: 14.8.178.38-electron.0
    OS: Windows_NT x64 10.0.19045
    
    ---
    
    Identifier: continue.continue
    Version: 2.1.0
    Last Updated: 1 month ago
    Size: 229.76MB
    

    Using DevTools it's obviously a stacked up padding combo:

    Image

    Removing the inline padding on either the parent (grey highlight) or inner element (blue highlight) fixes it.

  2. Perritu commented on Aug 19, 2026

    @Perritu

    Is there a way to apply a "hotfix" to my current version until the PR is merged?

  3. carlosrodan commented on Aug 19, 2026

    @carlosrodan
    Author

    I would also like to know this, but I didn't investigate

  4. Perritu commented on Aug 24, 2026

    @Perritu

    I did this to patch my current version:

    • Go to the VsCode extensions directory and find the continue subdirectory
    • Inside the continue subdirectory, navigate to 'gui/assets/'
    • In the file index.js, find the text "main",{ClassName:" and add w-screen to the className list

    It worked just fine.

    I also post a sed script at the PR.

  5. j-romchain commented on Sep 25, 2026

    @j-romchain

    not stack overflow, but the following seemingly duplicates of this have been identified:
    #13217
    #12912
    #12902

  6. j-romchain commented on Sep 25, 2026

    @j-romchain

    also based on what I'm seeing, with v2.0 they called it done and this is now abandoned...

  7. michaelben2336-ctrl commented on Sep 26, 2026

    @michaelben2336-ctrl
  8. bluemoehre commented on Sep 28, 2026

    @bluemoehre

    @michaelben2336-ctrl maybe you should avoid posting access tokens via email replies?

    Don't let him get away with this, folks - let's all disable his notifications by clicking the link 😏

  9. maniac-0s commented on Oct 11, 2026

    @maniac-0s

    The issue still exists. There is an automatic line wrap but thats way off the chat window behind the code window. I have to pull the chat window all the way to the right to see all the output. Why???

    Image
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions