Jazzcort

@AndrewTsao Can you just check if `contextLength` is correctly set to 128k in your config.yaml like what @GrimmiMeloni did? For code context, 400 lines might be around 4000 tokens so...

@GrimmiMeloni Forbidding file mention for files that have token size larger than context length is a new feature in 1.0.6. You can see the announcement in the 1.0.6 release. If...

@GrimmiMeloni You can check out the Rich LLM logging implemented by @owtaylor which is also a new feature in 1.0.6 release. You can see the LLM options sent from Continue...

@GrimmiMeloni If the `contextLength` is correctly set, you will see it appears in the options like this. 

> As per your suggestion, I adjusted the contextLength parameter to 1000000, and the error dialog no longer appears. @AndrewTsao I'm glad that you solved the issue. By the way,...

@GrimmiMeloni You can check the constructor in core/llm/llms/Ollama.ts where it fires a `api/show` request to get `num_ctx` from Ollama for the specific model you use. If `num_ctx` exists and we...

@AndrewTsao I don't think so, if you set the `contextLength` to 20,000, does the warning still show up?

> Can you point me to said announcement? I would like to understand where I can check for future breaking changes to get myself unblocked quicker. (I checked the github...

@RomneyDa I'll try to find another way to send the warning message back to the webview.

I've already implemented this second approach in the following branch: [Jazzcort/warn-when-truncate-last-msg-v2](https://github.com/Granite-Code/continue-for-granite/tree/Jazzcort/warn-when-truncate-last-msg-v2). Instead of sending the warning through the stream, I used the messenger system to deliver the warning message. With...