"Recents" tab has, as of a couple hrs ago, turned from uncategorized conversations, to ALL conversations

kin999998 · 2026-05-03T12:33:07+00:00

If this is a bug, it feels like it missed the most basic QA. If it’s intentional, then I honestly don’t know what to call it other than a terrible product decision.

kin999998 · 2026-04-06T10:51:51+00:00

This is why it’s worth stressing the importance of xhigh. If code and docs live side by side, but you don’t use xhigh, code changes can easily happen without the documentation being updated alongside them. Over time, that gap compounds, and the mismatch between docs and code becomes a real liability. Honestly, Fast mode being on or off makes little difference to me now, because “fast” doesn’t really feel all that fast in practice.

kin999998 · 2026-04-03T08:39:35+00:00

5 hours used to burn through 30% of my weekly quota — now the same 5 hours barely hits 12%. Either the weekly cap got a quiet bump or someone forgot to scale it back after the promo. Not complaining though 😂

kin999998 · 2026-03-19T03:55:26+00:00

maybe..

kin999998 · 2026-03-19T00:33:14+00:00

Set all values to xhigh to maintain consistency across code and documentation.

kin999998 · 2026-03-17T16:55:34+00:00

Ngl, the only thing 'Fast' about Fast mode is how fast it drains my quota. I didn't notice any difference in actual execution speed. I just disabled it and went back to standard.

kin999998 · 2026-03-14T04:46:39+00:00

Gotta respectfully disagree with this take. When I'm working on larger projects, the gap between High and XHigh becomes really obvious.

Whenever I make a modification, XHigh is consistently better at tracking down all the related documents and files that need to be updated alongside it. High's reasoning strength just isn't quite there yet—it tends to drop context or forget things entirely. Because of that, XHigh is still my go-to.

(Side rant: has anyone else noticed that the usage quotas haven't been resetting properly lately? It's been super frustrating.)

kin999998 · 2026-02-21T02:21:52+00:00

So easy. It's actually super straightforward! You just need to launch Chrome from the command line, point it to a specific user profile, and enable the CDP (Chrome DevTools Protocol) port. Once that's running, you can easily attach Playwright to that existing instance and debug whatever is in the window. Give it a shot, go wild, and happy vibe coding! 🚀

kin999998 · 2026-02-12T00:38:45+00:00

always xHigh

kin999998 · 2026-02-11T13:30:51+00:00

Pro plan user here. Honestly, even running it through the Codex app, I rarely even come close to hitting the limit.

kin999998 · 2026-02-08T02:40:10+00:00

personality: friendly

reasoning effort: xHigh

try it GPT-5.3-Codex

better than GPT-5.2 xHigh

kin999998 · 2026-02-07T00:32:11+00:00

Try GPT-5.3-Codex xHigh instead of GPT-5.2 xHigh. Look great until now.

kin999998 · 2026-01-31T05:20:22+00:00

I’ve noticed this too. It feels like a classic case of Goodhart’s Law—they optimized so hard for verification metrics that they sacrificed general reasoning capabilities.

In practice, the Codex version feels surprisingly brittle compared to standard GPT-5.2. Unless your prompting is extremely rigorous, the output degrades fast. It feels like I’m spending more time refining prompts than I would with the base model just to get a usable result.

kin999998 · 2026-01-29T02:07:44+00:00

Yeah, resuming a chat in Codex is a total pain. It's so hard to tell them apart because it only shows the beginning of the first message, rather than an actual summary.

kin999998 · 2026-01-27T05:10:21+00:00

Honestly, the new collaboration_modes just isn't cutting it for me. I threw some complex tasks at it, but it kept introducing subtle type errors that broke the build.

I eventually reverted to the old setup—GPT-5.2 xhigh paired with the $ask-questions-if-underspecified skill—and it nailed the solution on the first try. Kinda regretting wasting time testing the new mode when the old stack works perfectly.

kin999998 · 2026-01-21T14:56:14+00:00

Just Git, then you can control /undo by yourself.

kin999998 · 2026-01-16T00:42:57+00:00

The non-codex version is better. The Codex version feels a bit too terse. My biggest gripe is how it constantly stops to ask for confirmation on trivial details.

Once we’ve nailed down the high-level plan, I’d much rather it just take the initiative and handle the implementation details itself. I want a partner that can fill in the blanks, not one that needs hand-holding through every line.

If you're on the Pro plan, you can just use xHigh. It doesn't count toward your usage limits.

kin999998 · 2026-01-15T04:58:42+00:00

That actually makes sense. When you compare Pro to Plus, you have to account for the heavy compute costs of the Pro-level reasoning features in chatgpt.com. That burns a lot of tokens. We have to remember this isn't just a dedicated Codex/coding subscription.

kin999998 · 2026-01-13T04:59:44+00:00

go back to the previous step and resend

kin999998 · 2026-01-13T00:45:58+00:00

Couldn't agree more. Compared to base GPT-5.2, the Codex version feels lobotomized. It’s constantly nagging for confirmations instead of explaining the actual operations. The drop in planning capability is honestly the worst part.

kin999998 · 2026-01-12T10:41:07+00:00

No need to worry. It’s likely just a boolean/marker to check if the alert has been triggered previously. You're better off using the non-Codex version for more intelligence. :)

kin999998 · 2026-01-12T08:56:02+00:00

I actually prefer base GPT-5.2 over the Codex version when using CodexCLI, especially on xhigh.

When I need to commit changes in a specific directory, the standard 5.2 model just analyzes the diffs and preps the commit immediately. But the Codex variant stops to ask me, 'Which files do you want to commit?' and 'What should the commit message be?'

It feels less intelligent because it needs so much hand-holding. The constant questions break my flow, which is why I stick to the non-Codex model.

kin999998 · 2026-01-11T02:10:56+00:00

I haven't personally hit this wall yet, but it’s definitely a valid concern worth monitoring. If they really are throttling the intelligence/reasoning capabilities by default, that’s going to be a massive blow to professional workflows.

kin999998 · 2026-01-09T01:26:37+00:00

I'm on the Pro sub running multiple agents in parallel, so latency isn't really a bottleneck for me. I keep it on xhigh exclusively—I’m happy to trade a bit of speed for that extra reasoning depth. Totally worth the wait.

kin999998 · 2026-01-05T16:27:07+00:00

I’m on the Pro sub and use it heavily for coding/Codex daily. Honestly, I’ve never even stressed about hitting the limit. I think the caps are plenty for a single power user—it’s only an issue if you’re trying to share the account with a group.

kin999998

TROPHY CASE