Recently there have been a lot of posts on YouTube regarding a new website PLEASE DO NOT GO TO THIS SITE AND DOWNLOAD THE EXTENSION!
it advertises Itself as a llm aggregator with 3 months of premium subscription for free via a promo code.
I fell for it, thankfully Microsoft stopped the attack in time
IT IS A TOKEN STEALER!
The website itself was just registered a few days ago.
I am posting this so that it shows up on Google when someone looks it up. DON'T DOWNLOAD IT!
I have kind of accepted that VSCode gets an update like every day to add ever more stupid AI stuff, but today it was more dumb than ever.
So this is the left side of the update log:
In this update
- Agents
- Chat
- Accessibility
- Editor Experience
- Code Editing
- Deprecated features and settings
- Thank you
I looked at this and was like "oh wow, they did something else than just slop". Well, I thought wrong. Clicking on Accessibility, Editor Experience or Code Editing ... does nothing. Because those headings don't even exist in the changelog; what is this? Is there actually any person still involved in this project at all?
Situation:
- VSCode with Continue extension using the API of the...
- ...locally hosted LLM (a custom Qwen3.8) with LM Studio
- context is set to more than 50k+ tokens
- When using LM Studio internal chat functionality single answers can generate more than 4096 tokens.
- When doing chat, code analysis/adjustment and planning in VSCode continue chat it stops at 4096 token output.
My solution:
In the VSCode user config directory search for the continue extension folder and its config files.
In Windows this is
C:\users\<username>\.vscode\extensions\continue.continue-<version>-win32-x64
and there you go in the subfolder "out" where you should find the file extension.js which is roughly 53MB (in this version currently for me).
-> Make a backup of that file before you proceed.
When opening the file in VSCode itself it is too large and not rendered properly when scrolling further down, so I used the normal Windows Notepad (took a while, but worked)
Search for "DEFAULT_MAX_TOKENS" and you should find the entry
DEFAULT_MAX_TOKENS = 4096;
This is likely being applied to models the .js file does not recognize.
I increased the number in a first attempt to 8192 and then ran my test again and the continue extension in VSCode did not abruptly stop during streaming the output through the API at 4096 tokens and completed my requested analysis in VSCode with around 6500 output tokens (I watched the API logs). This probably can be further increased until there may be a built in limit of how much the model may output, which I have not further tested for.
maybe has relations to this forum entry:
Don't know if this helps someone and yes I know that there are alternatives to Continue like Cline.
It just kept me busy troubleshooting for over an hour after I could not find a step-by-step solution like this here elsewhere.
