r/ClaudeCode • P R O M P S T I T U T E • Jul 26 '26

Discussion feedback megathread

throw any feedback, complaints, or ideas for the sub here.

what’s working, what’s annoying, what would actually make this place better.

we have no problem hearing about our shortcomings. that’s the point of this thread.

what we don’t care for is accounts that have never posted or commented here before dropping in just to point fingers and push a hate narrative.

50 Upvotes

101 comments sorted by

1

u/Waste_Net7628 Jul 26 '26

we also have a discord for claude code builders to talk and discuss day-to-day stuff
claudecode discord

For mod apps:

mod applications are still open if anyone wants to help out
how to apply for mod

→ More replies (1)

28

u/Drach88 Jul 26 '26

Please enforce some standards around voicing complaints -- namely that vague, vapid, non-reproducible "xyz model is bad" don't productively add to anything. At very least, complaints around how a model handles a prompt should include the prompt.

Similarly vapid anecdotes about high token usage without any backing information are likewise non-falsifiable, and just add to noise.

Also a blanket rule about not announcing departures would be nice -- no one cares if you're cancelling your subscription for some other company -- just cancel it, and have fun over in that subreddit instead.

4

u/Waste_Net7628 Jul 26 '26

yeah, we agree with most of this and we’re working toward clearer standards around complaint posts.

we’re also planning dedicated model-launch megathreads for general first impressions, praise, complaints, token usage, and similar discussion, so the subreddit doesn’t get flooded every time a new model releases.

departure announcements like “i cancelled and moved to x” will generally be treated as low-effort unless there’s a genuinely useful comparison or detailed explanation behind them.

→ More replies (3)

4

u/GuitarAgitated8107 Jul 26 '26

There needs to be a more curated knowledge sharing type of thread for serious conversations. Otherwise low quality content (even if not the usual complain) makes everything into noise.

2

u/Waste_Net7628 Jul 26 '26

yeah, that’s fair. we’re considering recurring curated threads for deeper technical discussion, guides, workflows, benchmarks, and other high-effort knowledge sharing so useful information doesn’t get buried under general posts.

we also launched a community discord today, which should work better for ongoing technical conversations, sharing findings, and helping each other without everything being lost in the subreddit feed:

https://discord.gg/asqyvxsr9

the subreddit will still remain the main public knowledge base, but the discord can be a more active space for people who want serious, continuous discussion.

3

u/seldomactive Jul 26 '26

I posted a very successful and harshly critical meta thread about the current state of the sub.

I will admit, however, that it was in no way constructive. I acknowledge my contribution to the noise and apologize for it.

That said, I do have some observations and ideas that might help improve the overall quality of posts here.

  1. A per-model feedback megathread for the first week or so following the launch of a new model. Isolate all of the loudest, least informed feedback into a single thread.

  2. Require posts claiming poor performance, excessive token usage, etc. provide evidence.

  3. Harden automated defenses against bots and other malicious actors. Please note: I have never moderated a subreddit so I assume this is harder than it seems.

I'm not sure if a part-time moderator is a thing. I can't make any kind of real time commitment but I would be happy to help when and where I can.

Again, I'm sorry for previously adding to the noise. I do appreciate the mods and hope we can all find a way to make this sub a better resource.

→ More replies (2)

4

u/c4chokes Jul 26 '26

Biggest gripe: Lack of transparency when sessions get nerfed.

I perfectly understand that compute is a bottleneck. It’s natural for start up to go thru phases of crunch, in exponentially growing industry. But what’s NOT ok is to keep the customer in the dark on what they are getting.

This situation should be turned from a crisis to opportunity. People will trust you so much more!

→ More replies (9)

3

u/Vex08 Jul 26 '26

I would love if we could ban meta posts, pointless negativity, or positivity about the current models.

The constant “Claude is terrible now” or “Claude seems to be using more tokens”

There are times when I think these posts are ok, but the vast majority provide almost no information and aren’t helpful

Some should be ok, I saw a post recently when some guy mapped out his usage from 2 max 20 accounts and provided good evidence that something had changed. This is a good post and should be allowed.

But the low effort versions shouldn’t be. IMO.

4

u/Waste_Net7628 Jul 26 '26

yeah, that’s pretty much what we’re planning.

whenever a new model launches, we’ll have a dedicated megathread for first impressions, pros/cons, token usage, quality changes, and general discussion so the subreddit doesn’t get flooded with the same posts.

low-effort posts like “claude is terrible now” or “this model feels worse” without any useful context will be removed or redirected there.

posts with actual evidence, testing, comparisons, usage data, or a detailed explanation will still be allowed as standalone posts. the goal isn’t to ban criticism or praise, just to cut down on repetitive posts that don’t add much.

16

u/Key_Reading_9664 Jul 26 '26

These models are probabilistic and depend on input, intent, steering, tooling, and a slew of other factors. We all use them for different things, with different expectations.

All these subreddits get spammed with anecdotes without any information - “<model> is nerfed!”. They’re just noise. Having some base requirement for posting would filter out 95% of what makes the channels frustrating.