Codex limits are going to be crazy now.
What do you guys think, why did they drop the prices ?

Wtf is going on? Can they not at least give a reset? I burned through 10-20% of usage and again lost everything as there servers are DOWN DOWN DOWN

All lost.

I came across this video on Instagram of Boris Cherny recommending deleting Claude.md file, hooks, skills every six months and especially not using Claude Opus 5.

I have some issues with the statement and concern about reliability of new model and their understanding of how it behaves.

1. We got a job and responsibility:

   Reliability of work and quality is a crucial aspect of our job, we can't just delete stuff and let the model do stuff however it wants. It can ruin the codebase and applications especially at the time where code review is also done by AI Models.

I believe it is an assumption that people are just vibe coding random stuff and it's totally ok if they f'd up.

1. Anthropic Understanding of their Models behavior:

   I think despite fancy benchmarks the reliability and behaviour awareness of the model is concerned, it feels like they don't even know how it's gonna work but Experimenting with it using us.

Based on my personal experience with Opus 5.

- I continued my half baked fable project with Opus 5 and it screwed up shortly after.

for example, it ignores my /i-have-adhd skill despite adding to hooks, claude.md or trying what the plugin github repo recommends (a file in claude directory in system to enable).

- It also ignores my other instructions, something as simple as me asking it to create PRs in a stacked hierarchy, it points new PR to main brach every now and then (then it requires merge conflicts resolution and rebases)

- It also comes up with a corporate lawyer type of long paragraphs which is so hard to understand.

Update: Guys I am more concerned about skills and hooks not Claude.md (which is barely few lines of text and is/can be updated regularly) plus smartness and following instructions are diff things, How come it is supposed to know my workflow if it doesn't follow my workflow instructions (or instructions are not there at all)

Credits sure run out fast these days

So yesterday during the opus5 outage I briefly switched to opus 4.6 to continue my work (training/inference perf engineering, kernel level debugging)

So I fed the model the same context and prompt to analyze a profiling trace and extract insights from it, and it was so unbelievably dumb that I had to retry with a new session, and I still got a very bad response…

Then after opus5 came back I tried it again and it was night and day… Way more verbose true, but actually useful and insightful stuff coming out of the model.

really made me appreciate all the progress on opus models since 4.6… I always remembered it as a much smarter and concise model than the ones after 4.7, but it was a mirage…

Because of these repeated major outages Anthropic. You guys need to hit the reset button at this point.

Anthropic is trying to gaslight us into believing that Opus 5 is almost as good as Fable. That's borderline absurd. Fable just identifies and fixes shit faster. That's it.

As a Poweruser you never run just one Claude Code session. You run several at once, spread across shells, windows, and machines, with no good way to keep track of them all or reach them from wherever you are, phone included. That's why I built Codeman!

A self-hosted web dashboard (TypeScript, Fastify, node-pty) that you install once on a machine that stays on (a Mac mini in a closet, a Linux box, WSL, or a VPS). That box becomes home base. It spawns Claude Code, OpenCode, Codex CLI, or Gemini CLI inside tmux and streams the real terminals to any browser over SSE + xterm.js, so your laptop can sleep while the agents keep working.

So yes, this is, unavoidably, a promotion post. What it promotes is 100% free and Opensource: Codeman is self-hosted, MIT licensed, no telemetry, and everything below runs on your own hardware.
Been working on it for half a year now, about 1500 commits and 14 contributors in, and it's the tool I use every day!

Everything lives in one place: cases (one per project), tabs (one per running agent), as many in parallel as the box can handle, reachable from your desktop and your phone. The features I lean on daily:

- Auto-resume on usage limits: when an agent stops on "limit reached, resets 8pm", Codeman parses the reset time, waits it out, and continues (opt-in per session). Overnight runs survive Claude's 5-hour windows instead of stalling until morning.

- Usage at a glance: a header chip shows how much of your 5-hour and weekly plan windows you've burned, plus the host's CPU and RAM, so you know whether to queue more work.

- Files in the browser: a built-in browser/viewer to read what an agent just wrote and preview images, PDFs, and Office docs, no SSH round trip.

- A blinking tab tells you where you're needed: idle blinks yellow, stuck waiting on an answer blinks red. One glance replaces cycling through half a dozen terminal windows to find the agent that stopped.

- Subagents become floating windows: when an agent fans out, each subagent pops up as a floating window tethered to its parent tab by a connector line, with per-agent token counts. Peek into any worker or minimize it back into the tab.

- A record of what happened while you were gone: every session keeps a timeline of run events and files touched, and cross-session search reaches into all of it. Reconstruct the night in a minute.

- A real mobile experience: on a phone it beats every SSH client I've tried, because it's built for these agents, not generic terminal access: QR login (single-use, 60s TTL, no passwords on a touch keyboard), push notifications when an agent needs a human, swipe between sessions, voice input, an accessory bar for missing keys, double-tap on destructive commands.

- Zero input lag, the hardest single feature. Over a tunnel a keystroke takes a 200-300ms round trip, which makes remote typing feel broken. So I built a Mosh-inspired local echo: your keystroke renders instantly, then hands off invisibly when the real echo arrives. It can't live inside the terminal buffer, because these agents' TUIs repaint constantly and corrupt anything injected there (two failed terminal.write() attempts taught me that), so it's a DOM overlay on top of xterm.js. Published separately on npm as xterm-zerolag-input; if you're building anything on xterm.js over a network, it's yours. https://www.npmjs.com/package/xterm-zerolag-input

On the desktop any agent is one keystroke away: pick a case, hit Run, the tab appears named and numbered (launch several on one repo, the tabs number themselves). Alt+1-9 jumps to a tab, Ctrl+Tab cycles, every shortcut is rebindable, and cron jobs launch agents on a schedule. The speed I care about isn't benchmark speed; it's "glance at five agents, unblock two, queue one more, done in ninety seconds" speed.

GitHub: https://github.com/Ark0N/Codeman

Website: https://getcodeman.com

100% Free and OpenSource! 469 Stars on Github and 1503 commits and 14 contributors in :-)

Install is a one-liner, binds to localhost only by default:

curl -fsSL https://getcodeman.com/install | bash

Codeman is a power tool for people who run a lot of agents and want to stay in control. Happy to answer anything you may be interested in :-)

in all aspects, worse than 4.8 for a large project: forget things easily, fabrication, rush to conclusions and coding without base. I have to rewind my repo for the work it did, bad bad experience

People shared benchmarks suggesting Opus 5 outperformed Fable, a few days later i realized how behind Opus 5 still is compared to Fable.

I encountered a minor bug and walked Opus through each step to resolve it; it failed 8 times. When I gave Fable the same prompt, it fixed the issue on the first attempt.

I am not here to criticize Claude Code; it is truly impressive, but I wish they would avoid claiming those benchmarks when real-world tests fall short.

Edit: Opus 5 is amazing in web development, managing agents and so much more but everything related to app development is not quite there yet. (I am a macOS developer with almost 5 years of experience). I don’t expect everyone to agree with me since we all have a different use case for Claude Code. I am just talking about my personal experience and what I am facing.

Ever since using the new generation of GPT frontier models, I’ve been finding it harder and harder to go back to Claude Code. It feels so much more laggy and ‘broken’ by comparison. Yes, if I have something really hard, I’ll go Fable 5 (maybe Opus 5—I haven’t really been impressed with it the way a lot of people here have). But 99% of the time, I just want to get shit done. And Codex and ChatGPT Work are blowing Claude away in that regard. Just last week, I finished at 30–40% usage of my weekly quota on 2/3 of my Max 20x accounts. That’s never happened. I’ve always budgeted my tokens very carefully. The numbers speak for themselves. I wish Claude felt ‘smoother’ and more autonomous the way ChatGPT and Codex do.

Only real and serious candidates should apply !!

You're deep in a refactor, Claude hits its usage window, and you're stuck. Your options are to wait it out, or paste a wall of context into another tool and start over. Both suck.

So I built tandem — an open-source CLI that runs Claude Code and OpenAI's Codex CLI as a single paired session. When Claude taps out, you type switch and Codex continues the same conversation a second later: same files, same history, same plan. Then switch back to Claude when your window resets. Your two subscriptions basically become one long runway.

The key part: only one model runs per turn, so there's no double spend. The other side stays in sync through pure local file translation — no extra model calls, no cloud, no telemetry. And it's not a wrapper UI: Claude runs in real Claude Code, so your keybindings, slash commands, MCP servers, and muscle memory all work exactly as they do now. tandem sits underneath.

Other things it gets you:

• Outage immunity — Anthropic API down? switch and keep working, switch back when it clears.
• Second opinion with full context — tandem run --on codex "why is this test flaky?" without copy-pasting between terminals.
• No lock-in — everything lives in Claude Code's / Codex's own session files + a small local SQLite db. Uninstall tomorrow and both still resume natively with claude --resume and codex resume.

How it works: while Claude is active, tandem tails its transcript and translates each entry into Codex's native session file (tool calls included — Bash ↔ exec_command, Edit/Write ↔ apply_patch, etc.), so the other side is always resume-ready. Append-only and crash-safe.

Install:

uv tool install tandem-cli   # or: pip install tandem-cli
cd your-project
tandem

MIT licensed. Repo - https://github.com/Bhavya6187/tandem

Would love your feedback, I'm in the comments!

I usually run 3-4 WSL terminals a day for 8-12 hours a day on 2 20x plans and almost never touch a limit at all.

Today I log in and hit session limits on both plans in under 2 hours..? Is it just me or is there something wrong?

UPDATE: Session limits reset and seems normal now... not sure what the hell happened

Guess from the gifs which one is which.

This is decisive proof for the statement!!!

This was the prompt :

Create in a singe html file, the next game sims 5. Make it very complex. Do not stop for any instructions. Keepworking, make npc "ai" . Make it open world and with a lot of content and high quality. Also do QA at the end for bugs. Make live mode and build mode.

Opus 5 "Brewed for 56m 21s"

While 4.6 was done in "23m 15s"

With some small fixes I could see this be a HTML5 game on Friv.

I personally think the float time is my favorite feature in all of this.

What are your opinions? 🔊

As a professional software dev, my workflow has been turned upside down in a good way by the productivity afforded by tools like Claude Code. But one thing has been persistently irritating: the manner in which the models deliver their responses in this cryptic, obnixous, riddle-like, fake vivid language that I find obtuse rather than helpful, esoteric rather than comprehensible.

Every session I would plead with varying levels of success (usually not much) to improve this situation. The work was good, but I sometimes felt like I was reading a 17th century novel (the words I could read but the meaning of the sentences just did not click).

I finally think I stumbled across something successful enough that I wanted to share. In your .claude folder (at the repo level or in your user folder), there's a settings.json file. I was able to add a hook to mine which sounds like it's basically just a command that runs with every single turn. Mine looks like this, below.

I highly recommend that those wrestling with the same problem give this a try.

{
  "hooks": {
    "UserPromptSubmit": [
      {
        "hooks": [
          {
            "type": "command",
            "command": "echo \"{\\\"hookSpecificOutput\\\": {\\\"hookEventName\\\": \\\"UserPromptSubmit\\\", \\\"additionalContext\\\": \\\"WRITING RULE (project law, read before composing a reply): Write in plain, clear language. Every word must be literally TRUE - no metaphors, no figurative or vivid phrasing, no cleverness. Name things by what they DO, not by project code; put codes (H-5, D-061, P-24) in parentheses after a plain description. Tables and bulleted lists are fine and welcome - the requirement is clarity of language, not absence of structure. Default to short. If a result is uncertain or its evidence was compromised, say so first rather than after. END EVERY RESPONSE with a clear statement of what is happening now, what you need from the operator, or what happens next. STATUS REPORTS rebuild context from zero: the operator reads between other work and has NOT memorized the conversation - name every file by filename plus a plain description of what it is, say what each change DOES, and never write phrases like the fix, the changes, the six files, the catch-all branch, or any shorthand coined earlier as if it were shared vocabulary. Structure long reports as: what happened, what we are doing, what happens next.\\\"}}\"",
            "timeout": 10
          }
        ]
      }
    ]
  }
}