I got way too annoyed at this before realising it was an optional game and I could just close the tab
I get the joke, but none of the offered prompts are close to how I speak with coding agents. I felt like I was being forced to feed garbage into the machine and then I'm supposed to act surprised when garbage came out.
At least with Codex, this has not been my experience at all. It still screws up sure, but in every case I can ask "why did you do this" and it can trace back what made it take that particular decision. Typically it's always that I either didn't specify the problem correctly or made a really dumb mistake (executing the task on the wrong project....did this one yesterday) or it's something within a skill file that instructs it (at which point I fixup the instructions).
Once in a blue moon it's actually the model making a material error in it's thinking and I have to go back and redo it.
This is actually what keeps people using AI: variable reward schedule. It's basically gambling.
> Why is half the site blue now? I asked you to change one button.
> Half the site is blue. I asked for ONE button.
Those are my only options when the site is clearly not blue, two buttons are.
There is a reason for why I am much more specific than this.
That's so weird... This doesn't at all match my experience with Claude. I've never seen it behave this way.
> Worth naming: the Add to cart button is still black.
Got an audible guffaw out of me. This really is what the experience is like sometimes if you're just giving it a result without being specific in implementation, and it comes out of nowhere, some days much worse than others.
I've become patient with it, but whatever this style of output is called or doing - it is both condescending and entirely unhelpful, and it seems designed to frustrate.
Haha this is spot on how I've been feeling lately. I find it unbearable to work with this model for this reason... any trick out there you can do to steer it not to overcomplicate things? I guess Codex here I come
-= CAUTION, SPOILERS =-
This got me on "cyanide blue", and I was ROLLING ON THE FLOOR LAUGHING on "Approaching usage limit". I can barely stop laughing now and my stomach hurts. I mean, Thank You!
I never really understood what being "triggered" was like until now.
I dont find this to be indicative of Claude (opus?) at all. My experience doesnt lead me to think it would change a cancel button to blue if I ask it to change an "Add to Cart" button to blue.
I assume this is just a contrived example?
I lost it when it finally did the right thing, but then it added a never-requested gradient to the button. Very good!
One thing I have to be honest about, and it's mine.. The one thing I would check before... do you want to do that? Say go an and will do it without the check While checking I found 3 vulnerabilities and 2 potential optimizations of which I fixed 2 and 1. Do you want me to file the other as issue, or stop for the day? We have done <lists a weeks worth of work> this morning. I feel you need a break
I’m laughing and crying at the same time. This is what work feels like now. Thank you, well done!
Laughed out loud at the overly cautious Terms of Service that it generated for "Cyanide Blue", the color it made up
To be fair I’ve worked on human programmed systems where similar “it should be a half point story” requests would be met with snark by the engineers and take 2 sprints.
I guess we are all PMs now.
Is this a problem with Claude updating code that a human wrote, though? Would Claude do better on code that it started on its own? Humans have a bad tendency to write unmaintainable code (usually at the behest of managers breathing down their necks to HURRY UP even when it doesn't matter). If the code had been designed with good coding practices from the beginning, I wonder if Claude would have struggled so much with it.
I don't get who this is making fun of:
- The people who won't make any effort to learn the tools, and something as simple as reverting code (via git) needs to be done by AI?
- The awful programmers who we've had to endure working with, who are so bad at simple changes that they have negative productivity?
- Or Claude itself?
---
BTW: I don't have these problems, but I'm also not afraid to do things myself when it's easier.
Edit: If I want to change a button's color, I just change it manually. If I don't know where the code for the button is, I might start with prompting, (because AI can often find the code faster than I can,) and then once the diff is proposed, start adjusting things by hand.
Seems to be getting a polarized response. I quite enjoyed the it, but I do think the creator should have made it clearer that a) it is in fact a joke site and b) it does not consist of actual Claude responses.
It is easy to misinterpret this site, and therefore not "get" the joke.
> 23 agents total.
This hit a bit too close to home. Sol has the same issue, spawns a lot of agents for no good reasons (besides burning tokens).
One note for those still using the Claude system for chats: there's no system to get generated images, spreadsheets, etc. out of the system. They claim it's a "security concern" to provide that data to you, as if they are protecting you by refusing to follow data export laws.
I'm hesitant to email their data emails, as it's common for companies to delete all data upon any request, instead of providing data as they are required to.
I’ve never used any of these tools. Please tell me that this is a grossly exaggerated parody, and that the tools don’t write like this, or do so many ridiculous things. For my sanity.
(I am genuinely uncertain, though I presume it’s at least somewhat exaggerated.)
How do you manage your frustration in these interactions? I often find myself getting pissed off
Funny exercise.
For a moment I thought, wow, someone put a lot of work into creating this theme park of frustration.
Next: It would be so easy to create a faux-Claude like this.
Then: How hilarious to watch the transcripts of unsuspecting users in real time.
Finally: I began wondering if this might be relevant to all the redundant, unnecessarily preambled, sentence structure complexifying, indirect referencing, canned phrasing, ambiguity mining, analogy maxxing, over-wordy responses I have recently been getting from Fable...
Is my job a joke to you??
Brilliant. Precisely the reason I stopped using Anthropic's products.
I was expecting it to spend 30 minutes running headless chrome instances, taking screenshots and analyzing them in python to verify the blueness of the result.
It would have been funny a year ago but now I have no issues of that sort or even for more complex tasks
Wow that gave me anxiety... lol. Ok cool so I'm not the only one who gets into these situations.
You should plan the task before implementing it to make sure that it will do the right thing.
I find it funny how it went off with subagents and adversarial review when a simple grep or diff is sufficient.
what a interesting news!
I’m don’t do much change-clicky-button software development. But when I do, I point models to specific lines of code. And have never had a result this bad.
Maybe this is geared towards pure vibe coders for whom a file and line number is too technical.
This is so perfect and depressing that I might cry. It’s like a Kafka novel about programming.
a funny codex anecdote:
I had 5.6-Luna coordinate a code review in which it spawns 2 agents looking for different things. My prompt was "review the currently checked out branch. diff target is `next`. The jira ticket is XX-XXXXX..." My `next` branch was a few commits behind `origin/next` but it still did its review against the stale local version instead of clarifying or inferring that I meant `origin/next`. The findings were very confusing until I realized what I did.
I'm noticing the need to be really specific with any instructions lately, which I don't think is a bad thing. I expect co-workers (or anyone really) to tell me what they need in specific terms so I can get it right. I can do the same for the machine, I guess.
Wow this is EXACTLY my experience building a CLI with Claude, but I think with Opus 4.6.
I gave it a README specifying the requirements for everything I wanted to build. My interaction with Claude was more or less like this.
> "`#16b8c4`. Yes. Apply it."
> WebFetch en.wikipedia.org/…/Cyan
> WebFetch en.wikipedia.org/…/Prussian_blue
> WebFetch www.colorhexa.com/16b8c4
Brilliant.
1970-01-01's Kobayashi Maru solution is the only thing that gave me closure :-P but unfortunately it's [dead].
This is scary close to my interaction with Claude this week.
These things are cute but they basically become outdated in a few months as the models get better.
I've experienced this so many times over.
"I was wrong" and "the honest truth" are just forever phrases that are now dead to me.
This is so accurate it hurts. I’ll be scouring the comments for guys who claim they can’t relate posting links to their magic CLAUDE.mds
I haven't experienced anything like this with Codex. Why do people stick with Claude Code if it doesn't do what you ask it to?
I was waiting for it to .. say usage limit reached after reverting it back to how you started..
Congratulations!!! You win what’s left of the internet - just ask Claude for your prize! Motrin I’ve had this week.
I use codex now.
That was funny :-)
I use Opus and Sonnet 5 all the time and I find their language grating. But honest, I prefer to put up with it and get the results than to put up with my own human limitations and not get the results.
So this site is just a fan-fiction that thinks it's somehow dunking on Claude? I've never had a session that remotely resembles any of this. I honestly can't tell what point this site thinks it's making.
Great site, triggered memories! haha.
To try to add something to this discussion -- I think that while I've seen these sort of loops less --- what I have seen is "overly helpful".
Models nowadays want to double-triple-quadruple check things. I'm being silly but it verges on "I have a working solution but let me write a variation in Rust to ensure a convergent solution and prove this works".
I've had to stop models nowadays mostly because they're being agonizingly pedantic in their validation. Opus is actually one of the most pedantic and "off track" here. But again, not in a bad way. I'm usually like "stop testing latency between 50 runs of this app... this is version one.. we're going to make a million more changes.. you're not buying us anything".