Jatin
131 posts

Jatin
@whynotjatin
i tell computers to do things. sometimes they listen.
Jamshedpur, India Katılım Haziran 2018
270 Takip Edilen32 Takipçiler

Spent some time polishing my portfolio.
Looking forward to filling it with better projects as I continue learning.
Feel free to take a look and share your thoughts.
🔗 amritakumari-portfolio.vercel.app

English

@whynotjatin Yeah, I was trying this app few hrs ago. It is good
English

@webdevankit didn't read past the main thread? they made it free and open source
English

@whynotjatin Yupp, also I was trying something.. take a look 💗
Ankit Bhagat@webdevankit
I’m building my own note-taking app. I liked the Tokyo night theme of Obsidian so I’m trying to replicate it.
English

@thsottiaux Hey man, I think my account is still not fixed. People are saying they are not able to consume their daily limits. Mine are consuming GPT 5.5 too fast. Can you help me investigate this?
English

Codex usage limits will be fully reset again in the next hour and we will credit one additional reset into your bank for your own usage over the next 24 hours.
We investigated reports that Codex usage was being consumed faster than expected. There wasn't one central issue, but a few smaller problems compounded for some users.
Here's what we found and changed:
- Actual usage: Auto-review had become more proactive, another change was triggering more subagent work, and background suggestions could run twice or retry too frequently after failures. We reverted the changes and fixed suggestion scheduling, duplicate generation, and retry behavior. This should reduce unnecessary background token consumption while preserving the work users explicitly request.
- Usage reporting: Auto-review was incorrectly appearing as GPT‑5.4 usage, and failed or rate-limited requests were still shown as turns. Auto-review now appears as its own category, and only successful requests count toward the turn graphs. Rate-limited requests were never charged, but they were being displayed incorrectly.
- Immediate relief: We reset usage limits while rolling out the fixes, then shipped hotfixes across the CLI, desktop app, and usage backend.
- What to expect: New usage data should be clearer and actual consumption should be lower. Historical charts may still show auto-review under GPT‑5.4 because older turn data was not relabeled. Features that intentionally perform more work; such as /goal, subagents, and higher reasoning levels will still naturally use more capacity.
All fixes are now deployed, and we've added more detailed monitoring so we can detect background-usage regressions sooner. We'll continue watching the results closely.
Thank you for building and doing all sorts of things with Codex.
Tibo@thsottiaux
Codex team is in a warroom on a Sunday combing through logs and checking whether there is anything that could lead to increased usage drains for some users. Taking it very seriously and won't rest until we get to the bottom of it.
English


@aaronp613 Just because you shared an update, I looked to confirm whether it still at 100, but now my day feels ruined 😭
English

@jarredsumner @claudeai Why has claude code recursively launched multiple subagents and only last one is implementating and rest are waiting. Is this a bug?
English

Still seeing 'Indexing in Progress' on iOS 27? Here’s how to check the actual status 9to5mac.com/2026/06/15/sti… by @mvcmendes
English











