Hank

Hank is me.

[Hank @cch9]

I've found that the desktop version of ChatGPT is extremely resource-intensive, causing my mouse to lag. Has anyone else experienced this?

[Hank @cch9]

Is Claude secretly eating up my tokens? I didn't touch it at all while I was sleeping, yet 3% of my quota is gone. What's even weirder is that it resets in 39 minutes—even though I went to sleep over four hours ago. Do tokens get used up while I'm dreaming or something?

[Hank @cch9]

@thsottiaux Looks like I'll have to work overtime again tonight.

[Hank @cch9]

@thsottiaux I use both Codex and Claude for cross-verification and to check if my planning is on the right track.

[Tibo @thsottiaux]

Hello people of Sol! I've reset usage limits for all ChatGPT Work and Codex users. Together with that, a quick update on GPT-5.6 Sol usage limits.

Over the past few weeks, many of you have told us that Sol was using your Codex limits faster than expected. To be clear, we have not reduced usage on any subscription plans.

We’ve been digging into what was happening and have landed several improvements. As a result, we expect your usage to last around 18% longer during typical use of Sol. Some of you should already see significantly larger improvements from today. Tomorrow, we’ll also restore the five-hour limit that we temporarily paused while investigating.

Here’s what we found:
- GPT-5.6 Sol is much more willing to work for longer, make additional tool calls, and coordinate complex workflows across tools and subagents. That makes it better at solving hard problems, but some tasks were using far more than we intended.
- Sol also works harder at the same reasoning effort than previous models. High on Sol can use more tokens than High did on GPT-5.5.
- Programmatic tool calling, also referred to as code mode, gives Sol much more flexibility to run tool calls in parallel or continue working while waiting. But it also led to more responses per turn, more cached input tokens, and higher usage than expected.
- This was particularly noticeable when Sol was waiting for tool calls to finish or running many web searches. We’ve improved how we handle both cases and are continuing to make code mode more efficient.
- The impact was also very uneven. The median user actually found Sol quite token efficient, while some power users working on harder tasks saw their usage drain much faster. We were very focused on average and median usage before launch and missed some cases where the long tail could use significantly more usage.

Sol is a significant step forward in what Codex can do, but capability and efficiency do not always improve at the same pace, and some issues only become clear once people are using the model at real-world scale. We should have recognized this sooner and been more upfront about it.

You keep pushing the frontier and we’ll keep improving efficiency and sharing updates as we go.

[Hank @cch9]

@Da7_Tech I couldn't agree more! The token efficiency on Claude is insane compared to Codex. I’ve had the exact same experience.

[Hank @cch9]

Switching from Codex at 0% to Claude made a noticeable difference—token usage is genuinely way lower.

[Hank @cch9]

5.6感覺超噴token，先前用5.5就沒吸的那麼快，重點大家都在等7/29🤪

[Claude @claudeai]

The Claude Security plugin for Claude Code is now available in beta.

Scan your changes for vulnerabilities before you commit, or run a full scan across your codebase, all from your terminal on the Claude inference you already run.

[Hank @cch9]

最近花了不少時間使用 GPT 5.6，越用越能理解為什麼很多人會慢慢把它當成每天工作的助手，而不只是聊天工具。

我自己最喜歡的幾個地方：

✅ 理解能力更好
✅ 程式能力更穩定
對我來說，AI 最重要的不是「一次就給出完美答案」，而是能成為一位可靠的協作夥伴，陪著一起思考、一起修正、一起工作。

[Hank @cch9]

記得你是何時加入 Twitter 的嗎？我記得！#我的Twitter週年紀念日

[Hank @cch9]

@DOGECoinDrop 0x1138f8552e7f16F6Bf138E4Da9Ed7c5132e59614

[Hank @cch9]

@freeze_eth 0x1138f8552e7f16F6Bf138E4Da9Ed7c5132e59614

[Hank @cch9]

@Nermin_NFT 0x1138f8552e7f16F6Bf138E4Da9Ed7c5132e59614

[Hank @cch9]

@Nermin_NFT 0x1138f8552e7f16F6Bf138E4Da9Ed7c5132e59614

[Hank @cch9]

@Miss__Fortun 0x1138f8552e7f16F6Bf138E4Da9Ed7c5132e59614

[Hank @cch9]

@HafzaDeanna 0x1138f8552e7f16F6Bf138E4Da9Ed7c5132e59614

[Hank @cch9]

@HafzaDeanna 0x1138f8552e7f16F6Bf138E4Da9Ed7c5132e59614

[Hank @cch9]

@HafzaDeanna 0x1138f8552e7f16F6Bf138E4Da9Ed7c5132e59614