Claude and ChatGPT’s latest models are nitpicky and burning tokens. Here’s the fix
Claude Opus 5 and GPT-5.6 keep flagging minor issues as major flaws, burning through usage limits fast. Credit: Ben Patterson/Foundry I’ve been using two of the newest Claude and ChatGPT models to tinker with my personal self-hosted projects… and lately, I’ve found myself drowning in bugs. Not that Claude Opus 5 and GPT-5.6 Sol (which powers the new GPT Work agent) are causing bugs in my code.
- ▪Claude Opus 5 and GPT-5.6 keep flagging minor issues as major flaws, burning through usage limits fast.
- ▪Credit: Ben Patterson/Foundry I’ve been using two of the newest Claude and ChatGPT models to tinker with my personal self-hosted projects… and lately, I’ve found myself drowning in bugs.
- ▪Not that Claude Opus 5 and GPT-5.6 Sol (which powers the new GPT Work agent) are causing bugs in my code.
PCWorld files mainly under tech. We currently carry 248 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | PCWorld |
| Canonical URL | https://www.pcworld.com/article/3201946/claude-and-chatgpts-latest-models-are-nitpicky-and-burning-tokens-heres-the-fix.html |
| Publication time | Wed, 29 Jul 2026 15:36:43 +0000 |
| Retrieval time | 2026-07-29T15:45:59.847Z |
| Last seen | 2026-07-29T15:45:59.847Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | Eycf4RfxqRbo · 1 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
Claude Opus 5 and GPT-5.6 keep flagging minor issues as major flaws, burning through usage limits fast. Here's a prompt that fixes it. Credit: Ben Patterson/Foundry I’ve been using two of the newest Claude and ChatGPT models to tinker with my personal self-hosted projects… and lately, I’ve found myself drowning in bugs. Not that Claude Opus 5 and GPT-5.6 Sol (which powers the new GPT Work agent) are causing bugs in my code. Rather, they’re finding them… everywhere they look. Indeed, my queue of open “issues” seems to have doubled in the past week, filled with critical flaws and elaborate workarounds, each broken down into multiple steps.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at PCWorld.
Discussion
0 commentsMore from PCWorld
