@RunOnFlux Good point. A 3 a.m. run shouldn’t depend on my laptop being awake. A versioned repo seems like a good starting point, with agents fetching the skills and references they need. How do you handle updates for scheduled agents?
Tibo, spare us the bullshit about “models getting more efficient and prices going down, so you actually get more work done.”Every single competitor is doing the exact same thing. Claude improves their models, drops prices, and still keeps the 20x. They don’t turn around and say “hey, because we got better, we’re now cutting your usage in half.” That’s not how this industry works.Efficiency gains and price reductions are the baseline of AI competition. You’re supposed to pass those gains to users as more value, not use them as an excuse to slash the quota and then act like you’re doing us a favor. You’re literally saying: “We made progress, therefore we get to give you less.” That’s completely backwards. If your models are better and cheaper, the normal move is to increase the allowance or keep the old value. Cutting usage because you improved is the logic of a company that wants to extract more margin while pretending it’s “transparent.”Other labs improve and users get more. You improve and users get half. Don’t insult our intelligence by calling that “passing down the improvements.”😅😅😅
GPT-5.6 handles complex projects far better than quick one-off answers. It fixed my PM knowledge base bugs and trimmed a bloated 685-page export into a tidy 178-page handbook with thorough self-audits.#AIProductivity
@thsottiaux Haven't you seen the numerous users on GitHub, X, Reddit, and Rednote complaining about slower speeds and declining model quality? Fix this issue as soon as possible, please!!!🥲🥲🥲🥲🥲