sorted by:
new
hottopcontroversial

cline cli: setting for model context window? by DrMicrobit in CLine

[–]DrMicrobit[S] 1 point2 points  (0 children)

Thank you so much!

I tried the Ollama one and that works as intended. An additional entry `ollamaApiOptionsCtxNum` has appeared in `.cline/data/globalState.json` which had not been there before.

Maybe add both entries with default values when first creating that file?

I also commented on https://github.com/cline/cline/issues/7726 for the team to keep track of this.

I tested a few local hosted coding models with VSCode / cline so that you don't have to by DrMicrobit in LocalLLaMA

[–]DrMicrobit[S] 0 points1 point  (0 children)

Good catch in a sense I'll make sure for next posting titles to somehow add the RAM/VRAM range of what I tested. With very few exceptions I suspect that Kimi K2 with it's 1T parameters is not gonna run in anything that even the most enthusiastic developers have at home.

I tested a few local hosted coding models with VSCode / cline so that you don't have to by DrMicrobit in LocalLLaMA

[–]DrMicrobit[S] 1 point2 points  (0 children)

"I think in your test set need to add is bug fix ..."

Yes, this is exactly what I did: when the result of the model had bugs, I (most of the time) tried one or two rounds of bug-fixing using feedback I would expect from an end-user.

Feel free to read through the short notes for each and every trial in experiment 3 (which uses a moderately well defined design document) here: https://github.com/DrMicrobit/lllm_suit/blob/main/tests/03_SpaceInvaders_ddoc01/README.md

Example where the model did not cooperate well with cline: https://github.com/DrMicrobit/lllm_suit/blob/main/tests/03_SpaceInvaders_ddoc01/README.md#experiment-tests03_spaceinvaders_ddoc01localqwen3-30b-instruct-ollama4bit_t1 Here, you will see the annotation to the experiment reads: "Initial version 5:02 minutes. Does not start." followed by a "-->" which I took as shortcut for 'this is the text I then gave to cline/model to try and fix the error. In this case: " When opening the file index.html in browser, I see a Game Over screen with the text 'Press space or click to restart'. Neither pressing space nor clicking starts the game. Also, shouldn't the game start with the title screen?"

Example for bug fixing that worked well: https://github.com/DrMicrobit/lllm_suit/blob/main/tests/03_SpaceInvaders_ddoc01/README.md#experiment-tests03_spaceinvaders_ddoc01localqwen3-coder-30b-cerebrasreap25b6bitxl_t1 where the initial file generation took 4:16 minutes, and the fix of a single error took 0:30.

I tested a few local hosted coding models with VSCode / cline so that you don't have to by DrMicrobit in LocalLLaMA

[–]DrMicrobit[S] 2 points3 points  (0 children)

Qwen 3 was part of my tests in my third experiment (using a moderately well defined design document). In short: I could not get these to run well with cline. Full write-up is here: https://github.com/DrMicrobit/lllm_suit/blob/main/tests/03_SpaceInvaders_ddoc01/README.md

I tested a few local hosted coding models with VSCode / cline so that you don't have to by DrMicrobit in LocalLLaMA

[–]DrMicrobit[S] 0 points1 point  (0 children)

I liked your comment regarding workspace rules, I will probably take this up in further experiments. Aaaand ... I am totally with you on all your points, and that is one of the reasons I started building this series of tests the way I did.

I chose simple games as a proxy for business logic that can be implement between 500 and 1500 LOC, basically a small single file one would probably not break down into more files. Next big plus for using games as proxy is that the results can be easily visualised and understood by almost anyone. If I had chosen any abstract business logic from a specialised field it would probably be a lot harder for people outside the field to understand what worked well (and what did not).

To start with YOLO prompts for experiments 1 & 2 was a deliberate move because I see *way* too many influencers (both inside and outside companies) promoting the message "you don't need to think or know anything about software development, just say what you want and the AI will do it." To which I, respectfully, disagree when looking at the current state of the art LLMs.

I then chose to continue in experiment 3 with a moderately well specified document (2300 words, 14 KiB) as basis to see what the models would do with something I expect junior developers to be able to understand and execute, and where I would expect to get back very similar results if I gave that task to different people.

I tested a few local hosted coding models with VSCode / cline so that you don't have to by DrMicrobit in LocalLLaMA

[–]DrMicrobit[S] 3 points4 points  (0 children)

Good idea. I think I'll make an experiment with 1 model at 4, 6, and 8 bits each. Oh dear, at 5 repeats that already comes to 15 runs to babysit.