Repository navigation
Continue panel gets cropped/cut off in VSCodium sidebar #13055
Copy link
Copy link
Open
Description
Before submitting your bug report
- I've tried finding an answer on the Continue docs site
- I'm not able to find an open issue that reports the same bug
- I've seen the troubleshooting guide on the Continue Docs
Relevant environment info
- OS: Fedora
- Continue version: 2.0.0 (extension)
- IDE version: VSCodium 1.126.04524
- Model: DeepSeek CoderDescription
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
- Install VSCodium
- Install Continue Extensions V2.0.0
- Open the side panel
- 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)Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels
Activity
bluemoehre commentedon Aug 1, 2026
I can confirm this using:
Using DevTools it's obviously a stacked up padding combo:
Removing the inline padding on either the parent (grey highlight) or inner element (blue highlight) fixes it.
Perritu commentedon Aug 19, 2026
Is there a way to apply a "hotfix" to my current version until the PR is merged?
carlosrodan commentedon Aug 19, 2026
I would also like to know this, but I didn't investigate
Perritu commentedon Aug 24, 2026
I did this to patch my current version:
index.js, find the text"main",{ClassName:"and addw-screento the className listIt worked just fine.
I also post a
sedscript at the PR.j-romchain commentedon Sep 25, 2026
not stack overflow, but the following seemingly duplicates of this have been identified:
#13217
#12912
#12902
j-romchain commentedon Sep 25, 2026
also based on what I'm seeing, with v2.0 they called it done and this is now abandoned...
michaelben2336-ctrl commentedon Sep 26, 2026
bluemoehre commentedon Sep 28, 2026
@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 😏
maniac-0s commentedon Oct 11, 2026
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???