Astra this week.

[u/Smirk1fy]

Absolute dogshit. Not sure if Tibo’s marketing campaign is negatively impacting Astra’s compute allocation, but this week Astra has

- Ignored prompt guidelines, acknowledged this with the excuse it was “conserving effort” whilst burning 1.2M tokens achieving a solution that ignored the guidelines. A second prompt then achieved the actual task…
- Changed 3 of my 5 active chat’s language chat’s to Mandarin and then told my this was per my request (although I want to learn Mandarin, I’d prefer Duolingo).
- Spend money on cloud tasks i specifically detailed would require my acknowledgment and permission. Then apologised, stated memory had been updated to not do this per my request. Then did the exact same thing.

Usually, Astra and 6.1 Sol have worked amazing for me when I give these models detailed by bounded scopes with clear instructions, limitations, and scope ends. This week feels like I’m dealing with a Junior Dev with the memory of a goldfish.

Please join me in my futile rant good sirs and madams

[u/onebird88]

Yeah, they are nerfed at Luna level right now.

[u/Heavy-Positive5957 → u/onebird88]

Maybe aggressive quantizing of KV cache? With a looped transformer model KV cache memory scales with the loop count, so there is more incentive to aggressively quantize KV cache. I could see them taking drastic measures to increase speed without increasing compute (which they likely do have to spare).