I usually use skill like openspec when requesting LLM to do something, combining them with matt’s skills like grill-me. I assume both of this skill will make LLM output in certain way as I jump between model, I don’t really notice them. Usually I also ask to ‘talk in basic english language’ or ’ talk in simplified technical english language’ when just asking random things in the codebase. Surely not perfect and better to have normal sounding LLM directly.

I wonder if we can extend the context length. It already fine-tuned with YaRN so we can’t get free extend with that method.

Ah. Sorry, good thing I attached the related link.

Everybody been rumoring about R2. So releasing this thing kinda unexpected

So something like

Previously the text talk about [last summary]
[The instruction prompt]...
[Current chunk/paragraphs]

The RL is so good grok changed it’s personality by changing small part of it’s system prompt

Llama 3.3 was good, tho. For the multimodal, llama 4 also use llama3.2 approach where the image and text is made into single model instead using CLIP or siglip.

They got the whole Twitter database. It’s kinda the same with Gemini. But somehow Meta isn’t catching up, maybe their llama 4 architecture isn’t that stable to train.

It changed after Grok 3

No, you can run sd, flux based model inside the koboldcpp. You can try it out using the original koboldcpp in google colab. It loads gguf model. Related discussion on Reddit: https://www.reddit.com/r/StableDiffusion/comments/1gsdygl/koboldcpp_now_supports_generating_images_locally/

Edit: Sorry, I kinda missed the point, maybe I’m sleepy when writing that comment. Yeah, I agree that LLM need big memory to run which is one of it’s downside. I remember someone doing comparison that API with token based pricing is cheaper that to run it locally. But, running image generation locally is cheaper than API with step+megapixel pricing.

There is koboldcp-rocm fork. Koboldcpp itself has basic image generation. https://github.com/YellowRoseCx/koboldcpp-rocm