Ray

71 posts

Ray

Ray

@Ray_DaHero

Sydney, New South Wales Katılım Eylül 2016
216 Takip Edilen6 Takipçiler
Ray
Ray@Ray_DaHero·
I just lost a second banked Codex reset because I had no idea what time it would expire. Goodbye reset 7/11 and 7/18. It stated 7/18 but without the actual time, especially with people living in various time zones, it seems I have to just use it the day before even if I could get more work done. Could adding the localized time of reset be considered? @thsottiaux @ajambrosino #OpenAI #Codex #ChatGPT
Ray tweet media
English
4
0
2
1.9K
Ray
Ray@Ray_DaHero·
P.S. - We appreciate even having these banked resets and the new UI for it!
English
0
0
1
71
Ray
Ray@Ray_DaHero·
My biggest bottleneck right now is iteratively changing the trajectory of an MVP while I’m already deep in development. I’ll be building toward a certain architecture and feature set, then new ideas, better infrastructure approaches, or fresh AI capabilities come up and suddenly I need to replan, refactor, update context across the codebase, and re-verify everything without losing momentum. The overhead of re-contextualizing, replanning, and safely making bigger course corrections (especially around infra + new best practices) is what slows me down the most. How would Vorflux help me maximize momentum in this kind of dynamic, fast-moving environment where the “right” path keeps evolving?
English
0
0
0
19
Prasanna S
Prasanna S@myprasanna·
Launching @vorfluxai : The autopilot for software engineering. I was prev co-founder / CTO of @Rippling ($10B) and #1 coder in India. Vorflux is my high octane Ferrari. Every AI coding tool still makes you fly the plane. That's the copilot model: you stay in the seat, approving every turn. The models quietly got good enough to fly the whole route, but the tools never caught up. So we built the autopilot. @vorfluxai raised a $15M seed by @ycombinator @peakxvpartners @alliancedao @parkerconrad @jake_zeller @balajis @nivi @metakovan @lmrankhan @nikitabase @0xrwu @ayushjaiswal @mattshumer_ @eshamanideep @sreeramkannan @dvcoolster @nusimow @TeddySolomon11 @ashtoncofer @rvivek etc Drop your biggest engineering bottleneck below. I'll reply with how I'd attack it with Vorflux, and hand you $200 in free credits to bang out your backlog. Our full thesis 🧵👇
English
634
246
3.2K
2M
Ray
Ray@Ray_DaHero·
Switching to Codex and using GPT-5.6 Sol has been brilliant. I've learnt so much by simply using it daily working on personal projects for ideas didn't think I'd get to create myself. I'd say the best part of the whole experience is the seamless troubleshooting that Codex can perform on it own, even on itself! From frustrating troubleshooting to a one prompt fix, priceless. Try it out yourself and you'd be surprised how much of the leg work it can do for you. GPT-5.6 has also been leaps and bounds bigger of an upgrade than I had expected from 5.5. I am looking forward to getting more done with my subscription once I figure out the newer ways to utilize the optimizations and use cases of Sol, Terra and Luna. #OpenAI #Codex #ChatGPT
English
0
0
0
43
Ray
Ray@Ray_DaHero·
Green! Back to building we go.
Ray tweet media
English
0
0
0
4
Ray
Ray@Ray_DaHero·
Update: Looks like it's almost back to stable. My Codex CLI update command went through now. Monitoring for more. #OpenAI #Codex #ChatGPT
Ray tweet media
English
1
0
0
74
Ray
Ray@Ray_DaHero·
FYI: OpenAI is currently having some intermittent stability issues with ChatGPT: status.openai.com First noticed this when updating the Codex CLI and running into network errors. #OpenAI #Codex #ChatGPT
English
1
0
0
353
Haider.
Haider.@haider1·
GPT-5.6 Luna is a standout model for price-to-performance at half the cost, "5.6 luna max" matches gpt-5.5 xhigh, while outperforming "fable 5 md" at half the cost -- so together, "luna" and "sol" dominate the Pareto frontier i'm still unsure when to use "terra"
Haider. tweet media
English
62
45
681
149.2K
Ray
Ray@Ray_DaHero·
@reach_vb The question now is, what will you build next with the shiny new Sol in action VB? 👀
English
0
0
1
60
Ray
Ray@Ray_DaHero·
@DeanoDingus Tibo has acknowledged agent related issues in his recent post: "And we introduced regressions for some existing multi-agent workflows, alongside a collection of rough edges in plugins and other parts of the experience." Fixes should be on their way soon.
English
0
0
0
30
Ray
Ray@Ray_DaHero·
I've been running the new GPT 5.6 Sol with my regular development tasks and noticed it is taking up substantially more usage than GPT 5.5 at the same intelligence level. Two sets of 5hr windows drained over some UX/UI tasks, which in the past would not take up anywhere near as much :O Might be some day 1 issues to be ironed out, so here's to hoping the team continue to deliver more amazing stuff. Keen to try out more when I can. #Codex #OpenAI #GPT5 #GPTSol
Ray tweet media
English
10
4
65
6K
Ray
Ray@Ray_DaHero·
Saint Tibo has spoken! Looks like plenty of fixes and some clearer usage guidance of models are coming soon.
Tibo@thsottiaux

Hello beautiful people! We have reset usage limits across Codex and ChatGPT Work. And another one will come later in the day. Rejoice. Now that I have your attention, a quick update on ChatGPT Work, Codex and all the updates we shared yesterday. We’ve spent the last 24 hours reading feedback, looking at usage patterns, and talking with many of you. The short version is that there is a *lot* of excitement for GPT 5.6 Sol, ChatGPT Work on mobile & web, but also that we didn't get everything quite right. - We made it too easy to use the highest-compute settings without making the impact on usage limits sufficiently clear. - We reorganized the desktop app in one bold move, making familiar things like chats and projects harder to find. - Our launch framing was focused on ChatGPT Work and to some of our Codex fans it made it feel like Codex was going away over time. Absolutely not our intention, we love Codex and it is here to stay. - And we introduced regressions for some existing multi-agent workflows, alongside a collection of rough edges in plugins and other parts of the experience. We’re landing a first set of improvements today. We’re resetting usage twice so people can keep experimenting, changing defaults and the model picker so they don’t push people toward unnecessarily expensive settings, fixing several plugin submission issues, improving how we represent Codex in the product, and cleaning up some of the most immediate desktop problems. A larger set of improvements will land next week. We’re bringing chats and projects back into the sidebar in a more familiar and customizable way, making usage and reset timing much more visible, clarifying when to use ChatGPT Work and when to use Codex, and addressing the many other smaller pieces of great feedback we've had. The ambition behind this launch hasn’t changed. We think bringing ChatGPT and Codex together into a workspace where people and agents can collaborate is a very important step forward. But an ambitious direction doesn’t excuse avoidable confusion or regressions in the first version. Please keep the feedback coming. We’re moving quickly, and you should see the experience already get better with a few updates today; and substantially better again next week.

English
0
0
0
81
Ray
Ray@Ray_DaHero·
Understood on reasoning levels not being one to one, but is it expected for usage to be THIS different? Ive been working on an app daily and I'm familar with how much each piece of work usually drains, so hoping to find out what's going on with Sol. Could this be looked into? Happy to share more in DMs!
Ray@Ray_DaHero

I've been running the new GPT 5.6 Sol with my regular development tasks and noticed it is taking up substantially more usage than GPT 5.5 at the same intelligence level. Two sets of 5hr windows drained over some UX/UI tasks, which in the past would not take up anywhere near as much :O Might be some day 1 issues to be ironed out, so here's to hoping the team continue to deliver more amazing stuff. Keen to try out more when I can. #Codex #OpenAI #GPT5 #GPTSol

English
0
0
3
275
Vaibhav (VB) Srivastav
Vaibhav (VB) Srivastav@reach_vb·
Reasoning efforts on GPT-5.6 Sol: Start with the lowest setting that gets the job done, then turn it up only when the task actually needs more thinking. > Light & Low: quick, well-scoped tasks > Medium: planning, analysis, or a few moving parts > High & xhigh: harder work with multiple steps, tradeoffs, research, or careful verification Max and Ultra are a bit different: > Max: one model spends longer working through one hard problem > Ultra: multiple subagents work on different parts of a bigger problem in parallel Oh and, as with any new model, the reasoning levels don’t map directly from GPT-5.5 to GPT-5.6. If you’re used to 5.5, try starting one level lower on a familiar task, then increase it only if the result needs it.
English
103
45
611
76.3K
Ray
Ray@Ray_DaHero·
@midasavocado @thsottiaux Higher context window sizes can already be set manually via "model_context_window" configuration: developers.openai.com/codex/config-a… However, Codex's auto compaction is designed to perform much better on the default settings, which is why its a trade-off in overall performance atm.
English
1
0
10
341
Tibo
Tibo@thsottiaux·
What is something that you feel is surprising that Codex still can't do well and we should have gotten right a while ago?
English
3K
44
3K
566.9K
Drew P Bahlz
Drew P Bahlz@Igbeauxx·
@xai what’s up guys? I got rate limited on Grok Build, I upgraded to SuperHeavy and I’m still getting the same rate limit message.
English
3
1
7
154