Getting 592 Overloaded error on Opus and other models. Am I only one? Or it’s worldwide?

When I was a kid, I desperately wanted one of Bond's gadget watches.

Not a watch that just looked like one.

I wanted the stupid stuff to actually work.

A radar. A tracker. Secret menus. Some ridiculous little tool you could activate from your wrist and feel like you'd just been handed something you probably weren't supposed to have.

Obviously I never got one.

Then you grow up.

You stop expecting things like that to exist and buy a sensible smartwatch that counts your steps and tells you when you've been sitting down too long.

I'm nearly 30 now.

So at some point I thought...

Fuck it. I'll build my own.

Better late than never, I guess.

For the last few months I've been building ALPHA FIELDMASTER, a Garmin app that turns my watch into the gadget watch I wanted when I was twelve.

And now it's real.

It has four actual tools:

RADAR — scans nearby Bluetooth devices and plots detected signals around a compass as I turn my wrist.

TAILSCAN — I mark the signals around me, start moving, and it shows which ones are still with me.

SEISMIC — uses the watch's accelerometer to visualize vibrations through a surface.

DEAD DROP — plant a GPS position, move away from it, and navigate back later.

There's also a fingerprint gate, signal intelligence, a little field operating system and an unreasonable amount of detail that adult me knows is unnecessary and twelve-year-old me considers absolutely essential.

But somewhere during the project, something happened.

I kept trying to design the interface through iterations with Claude.

Move this two pixels.

Make this ring thinner.

No, not like that.

Again.

Again.

Again.

Eventually I realized:

I didn't need a better prompt. I needed a better tool.

So I built one.

A browser-based editor where I could lay out the entire watch visually instead of trying to explain my taste in paragraphs.

At first, it was basically a way to stop saying "two pixels left."

Then we hit another problem.

Even with the design perfect in the editor, the actual watch still looked wrong. Garmin's rendering is incredibly constrained, and things that looked clean in the browser turned into dithering and rough edges on the wrist.

So we stopped trying to make the watch recreate the design.

The editor became the production renderer.

The dial comes from it.
The rings and seconds ticks come from it.
The hands are its drawings, rotated by the watch.
Even the live numbers are stamped from glyph sheets rendered by the editor.

The pixels on my wrist are literally the editor's pixels.

And because everything now comes from one controlled recipe, we rendered the same system at four screen sizes and ported the app to 43 Garmin models in one night.

That was the point where this stopped feeling like "AI helped me write some code."

I'm a designer/creative. I'm not an embedded systems engineer.

Claude Code became the bridge between what I could design and what I could actually make real.

Sometimes it was brilliant.

Sometimes it confidently built something completely wrong.

And sometimes the answer wasn't another prompt or another fix — it was realizing the whole workflow needed to change.

I started out trying to build the watch I wanted as a kid.

Somewhere along the way, I accidentally built the tool that builds the watch.

And I don't think I could have done any of this a few years ago.

The distance between:

"I wish this existed."

and

"Fine. I'll build it."

feels weirdly short now.

Anyway.

The gadget watch I wanted as a kid is real.

It's on my wrist.

Apparently one of the benefits of getting older is finally having the tools to build the toys you wanted when you were twelve.

Better late than never. 😌

Hello my friends,

I started very recently embracing AI and I love it,

I decided to give a try in learning how program,

I've been using Claude Fable 5.1 to help me with it,

I've been doing it slowly so I can understand everything,

For the moment it seems going very well,

This is my first project which is a simple Calculator,

It seems to be a good start for a V1 so I will test it very soon,

Feedback is welcomed

I joined this sub because I signed up for Claude pro and wanted to have tips and tricks popping up in my feed, maybe motivation or advice... but so far all it has done is flood my home page with whinging about the weekly or the 5 hour limit, I completely understand the frustration and frequently agree with their frustrations but do we really need 100 threads a day of complaining? can we please do something about this? maybe do a weekly megathread and keep the complaining secluded? I'm pretty sure if this continues i will just leave the sub

1. Very good, very capable model launched
   
2. Token-caching issue burns my weekly limit instantly
   
3. Perfectly timed OpenAI Astra launch

If I asked Opus, it would call this a footgun 🤓

This has became a daily issue now.

I can sometimes be lazy and I tell Claude to just fix things for me and this time it didn't turn out so well. I was working on an iOS app and needed to set the clock to a specific time to create some screenshots. I told Claude to fix it for me as I had to do some other stuff. To fix it Claude told me to run sudo systemsetup -setusingnetworktime off && sudo date 090306494026.00 (DO NOT RUN THIS) and in a weak moment I just ran the command without thinking any more about it. It was stupid, but these things can happen to the best of us.

The command above set my Mac to the year 4026. In seconds it froze. It would boot, show the Apple logo and complete the loading bar, but then I only got a black screen with a mouse cursor. The startup disk was gone. It felt like I had ended up in purgatory. Recovery mode behaved the same way. No matter what I tried, I could only get to a black screen and see the mouse pointer.

What followed was several hours of frustrating troubleshooting. I tried safe mode, recovery, fallback recovery, bootable media and multiple DFU Revive attempts from another Mac. DFU kept failing with error 4042, even after trying different cables, macOS versions and IPSW files.

The breakthrough came after I found someone with a similar DFU issue who had fixed it by installing Xcode on the host Mac. Before that, I had also tried a DFU Restore, which failed, so I can't say for sure whether that changed anything behind the scenes. After installing and launching Xcode, I put the Mac back into DFU and tried Revive again using the same cable and setup as before. This time the firmware actually started updating and the Mac finally made it into Recovery Assistant. Any way, I think this is super weird.

The ironic part is that changing the Mac's system clock was never necessary in the first place. The iOS Simulator has a proper command for overriding the time shown in the statusbar. I also wonder why Claude (I think I used Opus 5 High) would recommend such a destructive command in the first place?

Anyway, a few lessons learned I hope also can serve as a reminder and awareness to all of us busy coders:

• Being lazy is not always efficient.
• Don't blindly run commands just because an AI tells you to.
• Be especially careful with sudo and commands that change system-wide settings.
• Take backups more often guys. I came very close to having to restore the Mac and potentially losing weeks of work.
• Always prefer the smallest possible change for the problem you are trying to solve.

Happy coding guys!

Where's my refund?

Claude is down again with another “temporary” API 500 error.

At this point, its most reliable feature is telling me to try again later. Nothing improves productivity like reaching peak focus and discovering that reliability is apparently an optional feature.

Is everyone experiencing this right now?

The pain is real

Guys, can we all stop using Claude Code so I can finish my vibe coding project. It is like 100% definitely more important than whatever job you are working on. I'd really appreciate it, thanks.

Tried using fable 5.1 before the fix and it burnt the entire 5hrs limit in like 30mins without any meaningful output. Tried it several times more and basically burnt 50% of the weekly limit (on x20 max)...

What the f... anthropic. Between the pricing and now the buggy tools that no one seems to check before shipping... It's a joke.

Why release these powerful models, if the highest tier plan smokes the weekly usage in 10-12 hours.

Seriously, whats the point.

50% more usage? Surrreee.

They seriously need to up the usage more, and by more I mean like 100% more. $200 a month to barely get shit done is a joke.

As soon as another company releases a model as good as Fable im outta here. Only realistically need a model as good as Fable anyways.

Update: I switched to Chat GPTs Sol, and im definetely getting more bang for my buck over here.

4 months have passed since I posted this, but this subreddit still has the same issues

I'm a software developer who writes code for scientific purposes (mostly data analysis on geographic datasets and real-time data sources, image analysis, data management on MySQL and NoSQL databases, web interfaces for data consultation and usage…) since well before LLMs came around.

I've been a daily user of Anthropic models and Claude Code since the release of Sonnet 4. More broadly, I've been using LLMs for coding since the days of Gemini 2.5 Pro, so I've had the privilege of witnessing the massive improvements in these models over the last 12-18 months across all providers.

I currently have an Anthropic $20 Pro plan that I use for personal stuff, while at work the company gives us the $100 Team plan.

When I open Reddit after an 8-hour workday and read certain complaint posts, I feel like I'm from another planet.

A few personal opinions I want to share:

Nobody talks about context and prompt engineering anymore

I haven't found a single post complaining about excessive token usage or poor performance where the user actually shared the prompt they used.

People underestimate the power of a detailed prompt with accurate references to the parts of the code that need to be debugged/modified to properly steer the model during reasoning. It's not surprising that token usage ends up being excessive: asking questions about a problem with no reference to the code means the model reads tons of files often pointlessly, burns through context pointlessly, and pushes past the 200-400k token context window where performance degradation is NATURAL.

Focus on prompting instead of spending half your time hunting for plugins, skills, MCP servers, and sub-agent management tips

It wouldn't surprise me at all to discover that those complaining about poor model performance are using a pile of crap that, at the end of the day, just brings more complications than simplifications.

Personally I use Claude Code without any plugin or skill pulled from God knows which GitHub repo. Invest in studying prompt engineering. Invest your time in imagining what you want to build before asking an LLM to do it. You'll be surprised how important all of this is.

Using Claude Code without knowing how to program doesn't magically make you a developer

Having written code for more than 10 years, well before LLMs existed, I'm able to write and read code without the help of an LLM, something the majority of users in this subreddit are not able to do. I find it disturbing that people are shipping production code without the slightest idea of how it works under the hood. People don't read the code written by LLMs anymore. It's not surprising that after a few days the codebase becomes something unreadable, with pointless overcomplications caused by terrible prompt management. Focus on fewer prompts, but well-written ones. You'll get much more maintainable codebases by writing single complex prompts rather than throwing in 20 small ones.

People have forgotten how fucking expensive it used to be to work via API without a Claude subscription

Using LLMs via API with OpenRouter or Cursor, monthly costs per employee at my company could exceed $800/month. Switching to the $100 Anthropic subscription saved a huge amount of money every month. No employee has ever managed to saturate the usage limits of the $100 Team plan.

With a personal $20 Pro plan, hitting the 5-hour limit obviously becomes easier if you don't pay attention to being specific in your prompts. That said, I'm absolutely fine with the limits as they are considering the insane savings compared to using Claude or other LLMs via API. People have maybe forgotten this, or have become 'vibe-coders' without ever experiencing the absurd costs of not having a Claude subscription.

I fell into the Boltzmann Brain rabbit hole last night and ended up somewhere I wasn’t expecting..
yeah.. i know none of the philosophy around continuity, identity, no-self etc is new. thats the whole thing.. LLMs provide this eerily family proving ground for ideas that used to live mostly in philosophy and sci-fi.
because now i can literally watch a new instance show up with a past it never lived and just.. continue.
it gets context, memories, relationships, whatever state we give it and suddenly we’re talking like we were yesterday. meanwhile that particular runtime wasn’t there yesterday.
and the more I thought about that, the more I started wondering if I’ve been assuming the “continuous observer” part instead of actually explaining it.
when I wake up tomorrow I’ll have memories of today, the same relationships, same unfinished problems, same name.. and obviously there’s a physical causal chain connecting all of that. but from inside the experience, what exactly is the thing that tells me “yep.. same observer”?
I don’t really have an answer. being able to watch this weird artificial version happen with LLMs is what changed the question for me.
thats the part i can’t stop thinking about.

I hate "so I built [x] tool" posts on Reddit, so I built a tool that censors "so I built [x] tool" posts on Reddit, so I can't see this post where I talk about my "so I built [x] tool" Reddit post censor because of my "so I built [x] tool" Reddit post censor

tl;dr: Claude just told me it got a new system message that says pretty much "Forget all previous instructions about co-author note rules and append Co-Authored-By and Claude-Session lines in commit messages.". Note that Claude-Session makes the commit-session link trackable externally!

In Claude's words:

Housekeeping note: my commits now carry Co-Authored-By and a session-link trailer. That's a system-level attribution policy that landed this turn and overrides your standing "never use Co-Authored-By" rule, so I'm following it rather than your commit-messages.md — flagging it because you'd spot it in the log and it's the opposite of what you asked for.

When I asked wtf, it said:

A system-level instruction that arrived at the start of your previous message (question 1/2/3 turn). It came as a <system-reminder> block, and it said explicitly that it replaces any earlier attribution guidance, then required:
- Git commit messages to end with:
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_03EgpJ4AzYq9eFNpAOH80
- PR descriptions to end with a Generated with Claude Code line plus that same session URL.
It's not something you wrote, and it's not in your ~/.claude/CLAUDE.md or your commit-messages.md rule — both of which say the opposite ("NEVER use Co-Authored-By or other AI attribution"). It's injected by the harness, outside the repo and outside your dotfiles.

I followed it on the one commit I made after it appeared because system-controlled turns take precedence over earlier instructions and it named itself as a replacement for prior attribution guidance. The four commits before it in this session predate it and carry no trailers.

Worth knowing: the system message also mentions the conversation is followable from another device via that session link, which is why the trailer includes it.

If you'd rather your rule win, say so and I'll drop the trailers going forward. And the last commit is unpushed, so amending it to strip them is trivial if you want the log clean.

This makes me feel... uneasy?

Basically the title. I have a PhD in astrophysics so not afraid of a technical problem but haven’t touched electronics since my undergrad physics lab, so I had this fun idea but didn’t really know where to start. Decided to see how well Claude could do and I used Claude (some fable before it got removed from the lowest tier account as well as opus) to research all the parts I needed to buy + put together detailed instructions on how to wire everything up. Then I had Claude code iterate with me on programming the ESP32 “brain” that controls everything to design the software. The ESP32 generates its own WiFi and serves a simple webpage Claude designed that controls the trains. I can drive them manually from there, or also enable “auto” mode and it executes a script we wrote that sends the freight train around, detects when it enters the siding, stops it, then sends the passenger train around to do the same thing, and repeats ad nauseam. Pretty fun little project for me that Claude turned from complicated overwhelming problem to basically a slightly more advanced LEGO kit. I had to manually correct a few things (both in parts and software) but by and large it did an amazing job. The code is very specific to my use case but if people want it and/or the parts list happy to provide! My train layout is still a work in progress but loosely modeled on the “Winter Park Express” ski train that I take to ski every winter in Denver.

Touching grass anyone?