3k context on first thread (main agent) - 3k on sub-agent = full working Pacman clone on local inference. The last update is pretty Wild!
Can i ask for image processing? I'd like that LLM can view/process images for UI composing/testing. Thanks for your hard work!!
Still don't know why in the world this IS compacting 882 messages, if they were already compacted in previous turns. That's nonsense.
No Matter what, Kilo is my preferred for complex tasks, but It still refuses to compress context when threshold is obviously over. Ej. 70K from 80K total. It's very frustrating. 😢
I got 5$ about 2 weeks ago, and i run out this afternoon. At this price, i was like "hey, this IS good, let's top Up another 5 bucks". Then, in 1 hour, 5$ R.I.P.
Seems that token budget was nerfed a lot. Screenshots of both. Left, was consistent use on the past weeks. Right one, the peak IS the spended today (46M until recharge) and peak to the bye bye again (around 100M token). It's a bad assignation problem? Or really downgraded from 700,000,000 T to 70,000,000?
It's llama cpp fault? Kilo don't detect death loops? What is happening? I'm tired, Boss....
Can't understand WHY with a same u_id wey are getting separated sessions/context with local terminal/browser/Telegram/others. If my user if = x give me my chat
Automatic context compacting seems not be working on Local LLMs, tried with 64K context, and It seems to reach and exceed limits everytime. It's a bug or i'm missing some configuration?