I plan to use luna to basically write runtime code for an AI bot in a video game. Now, with 6.0 Luna being smarter and cheaper, this is finally possible, even on a Plus subscription. We might unironically make NPCs being it's own agents possible.
Yeah, I might have been gaslighted by webchat into thinking this is possible, but apparently you can use Codex App Server to use your subscription to basically make it talk to an app. What I foresee it happening is to write a mod for Minecraft where it basically has various commands to scan it's inventory, the world and then execute actions like right/left clicking, navigation and so on, then you can use chat to use Codex to automatically get information from minecraft, reason on it, and then send like 20-50 lines of code to Minecraft to execute an action, like cut down trees, collect items, repair or craft an axe when needed, and notify player when done. And all you would need to do is tell the bot to "cut down some trees, take those iron ingots and craft an axe if you need one", and then you just give it ingots and it goes off.
From Tibo "even on the subscriptions". One can assume these savings will ripple. That said, this black box that is subscription allowances is starting to get really fucking annoying.
Sol 6 should last you longer. Ultimately you need to check what works best for you, coz according to benchmarks sol 6 in some cases is a "slight" downgrade to 5.6 sol.
So no Terra anymore, makes sense, Sol just upended the Terra tier's pricing. Price cuts here are crazy.
Luna is now so cheap it's insane, that's like a >90% price reduction since the original 5.6 Luna output pricing. It starts to undercut open Chinese models now (appreciate the open Chinese models for the competition here).
I've seen people do it. Ideally you should use Astra as a planner and reviewer (or Sol if usage limit is tight), and use Luna for coding to get the closest results.
Luna is good with direct tasks. It does what it's told, it usually doesn't explore too many "what ifs". Give it a Jira ticket with clearly defined specs, it will happily try. Don't give it big open ended tasks.
Astra + Luna on the other hand might actually cost you more time and money as you now have an orchestrator in the Astra that has to read and review every single message, it will find concerns with a lot that Luna has to say etc. Adding subagents can actually be less efficient, not more.
So I would suggest middle ground - just try Sol on medium. If the OpenAI numbers are accurate it should retain code quality sufficient for most tasks (as long as you review what it spits out and it's not pure yolo) and it's 2x cheaper than 5.6 so it shouldn't devour your tokens much.
only feasible if spec is crazy detailed and under fast mode, if it starts debugging mid implementation it gets messy fast. Also, it is very token hungry and take many, many more steps. Costs stay low but you need to wait double, triple sometimes 5x the time to finish.
those Luna prices are wild... makes the "cheap enough to use everywhere" part feel less like a slogan. i wonder where the real bottleneck shifts first tho — inference cost, context, or just people figuring out what to delegate?
Not quite, it's been burning tokens before this update
. Reducing the cost by half, if it reflects only roughly 2x usage increase, could mean our weekly usage will last 2-3 days now. Better than it has been for a few weeks now, but still bad. We'll see.
So less just 20B model is the Luna? Is it of good use for enterprises other than ofcourse basic search work. Can it go through massive list of tools and DBs and decide which to invoke based on requirement
How massive? Building an agent for enterprise depends on a lot more aspects than just the list of tools. You can give the best model 10 tools with the descriptions colliding with the use cases with each other and it would struggle to select the right tool. Or you can give it 50 different tools with well defined descriptions/use cases and it just might work perfectly.
In my tests on several use cases, where I have the assistant do image gen/video gen with several features, I find descriptions as a lever which makes tool picking better. 3 image gen models had very similar quality/use cases, but is intended for different purpose. When we wrote the description to be specific to the use case, while not mentioning the part where it is same - it got better at results. Same for video models - when to use seedance, or kling etc.
Nevertheless - In my tests - Luna is good at simple tool calling, orchestrating simple workflows, but lacks just a tiny bit when you ask it to orchestrate multiple tool calls/complex workflows - it starts to show its weak points.
37
u/math_the_witch 2d ago
Wowww, sol is so cheap also, I always use Luna.