llm/122b8d72-a8a3-4fcf-8eca-6a52786d1a8b/batch-4-ae1af947-dab4-409d-acec-47dac689b2a4-input.json
The following is content for you to classify. Do not respond to the comments—classify them.
<topics>
1. Lack of Concrete Evidence
Related: Commenters repeatedly criticize the article for providing no examples, code, projects, costs, or specifics about what was actually built, calling it empty hype and platitudes without substance or proof of claims
2. Author Credibility Concerns
Related: Multiple commenters point to the author's previous blog post praising the Rabbit R1 as evidence of poor technical judgment and tendency toward unfounded enthusiasm for new technology
3. AI Coding Tool Limitations
Related: Discussion of how AI tools work well for simple, repetitive, or locally-scoped tasks but fail with complex systems, large codebases, and non-trivial problems requiring significant human guidance
4. Greenfield vs Legacy Projects
Related: Observations that AI coding excels at new projects under 10,000 lines of code but struggles maintaining consistency and avoiding regressions in larger, established codebases
5. Astroturfing Suspicions
Related: Multiple commenters suspect pro-AI posts are marketing campaigns or astroturfing given the billions invested in AI, with some noting suspicious voting patterns and repetitive promotional content
6. AI-Generated Content Detection
Related: Many suspect the blog post itself was written by AI, citing lack of specifics, excessive em-dashes, and generic promotional language characteristic of LLM-generated slop
7. Manager Fantasy Critique
Related: Skepticism about the desire to become a 'super manager' rather than hands-on developer, with some viewing it as CEO cosplay or escapism from actual technical work
8. Productivity Illusion
Related: Discussion of whether AI tools create actual productivity gains or merely the feeling of productivity, with some noting impressive-looking output that lacks substance or quality
9. Security Concerns
Related: Significant worry about OpenClaw's security vulnerabilities, prompt injection risks, and the danger of giving AI agents access to production systems, emails, and sensitive data
10. Skills and Learning Curve
Related: Debate over whether effective AI tool usage requires significant skill development, with some arguing poor results indicate user skill issues while others see fundamental tool limitations
11. Real World Use Cases
Related: Commenters share legitimate use cases including utility scripts, exploring unfamiliar codebases, setup automation, and learning new tools, distinguishing these from transformative claims
12. Cost and Accessibility
Related: Discussion of the financial barriers including expensive subscriptions, Mac Mini hardware, and token costs that contradict claims of democratizing technology
13. AI Hype Cycle
Related: Observations that we're at the apex of AI hype, with predictions the bubble will pop and more realistic assessments will emerge over time
14. Context Window Problems
Related: Technical discussion of how AI agents lose coherence as context grows, with compaction causing confusion and requiring human redirection
15. Testing and Verification
Related: Emphasis on the need for humans to verify AI output, run tests, and maintain quality control since AI cannot reliably check its own work
16. Language-Specific Performance
Related: Observations that AI performs better with some programming languages like Python and JavaScript compared to Java, Scala, or enterprise frameworks
17. Engineering vs Management
Related: Philosophical debate about why engineers want to become managers, whether it's about power, career progression, avoiding obsolescence, or building bigger things
18. Model Selection Matters
Related: Discussion of significant quality differences between AI models, with frontier models like Opus and GPT-5.2 performing notably better than cheaper alternatives
19. Workflow Integration Tips
Related: Practical advice including using AGENTS.md files, breaking tasks into smaller chunks, brainstorming with agents, and having separate contexts for review and implementation
20. Vibe Coding Skepticism
Related: Criticism of fully autonomous AI coding without understanding the output, with warnings about technical debt, logical errors, and unmaintainable code accumulation
0. Does not fit well in any category
</topics>
<comments_to_classify>
[
{
"id": "46940356",
"text": "Yeah, once I saw that I was like \"Oh, so OpenClaw is probably going to be a dud too\" :)"
}
,
{
"id": "46936782",
"text": "I am somewhat worried that this is the moment AI psychosis has come for programmers."
}
,
{
"id": "46938875",
"text": "Add to that worry the suspicion that half this push is just marketing stunts by AI companies.\n\n(Not necessarily this specific post)."
}
,
{
"id": "46936866",
"text": "Yeah… I'm using Claude Code almost all day every day, but it still 100% requires my judgment. If another AI like OpenClaw was just giving the thumbs up to whatever CC was doing, it would not end well (for my projects anyway)."
}
,
{
"id": "46938454",
"text": "Exactly. Posts that say \"I got great results\" are just advertisements. Tell me what you're doing that's working good for you. What is your workflow, tooling, what kind of projects have you made.\n\n>Over the past year, I’ve been actively using Claude Code for development. Many people believed AI could already assist with programming—seemingly replacing programmers—but I never felt it brought any revolutionary change to the way I work.\n\nFunny, because just last month, HN was drowning in blog posts saying Claude Code is what enables them to step away from the desk, is definitely going to replace programmers, and lets people code \"all through chatting on [their] phone\" (being able to code from your phone while sitting on the bus seems to be the magic threshold that makes all the datacenters worth it)."
}
,
{
"id": "46936513",
"text": "There is no code, there are no tools, there is no configuration, and there are no projects.\n\nThis is an AI generated post likely created by going to chatgpt.com and typing in \"write a blogpost hyping up [thing] as the next technological revolution\", like most tech blog content seems to be now. None of those things ever existed, the AI made them up to fulfill the request."
}
,
{
"id": "46936571",
"text": "> There is no code, there are no tools, there is no configuration, and there are no projects.\n\nTo add to this, OpenClaw is incapable of doing anything meaningful. The context management is horrible, the bot constantly forgets basic instructions, and often misconfigures itself to the point of crashing."
}
,
{
"id": "46937978",
"text": "It didn’t seem entirely AI generated to me. There were at least a few sentences that an LLM would never write (too many commas)."
}
,
{
"id": "46937283",
"text": "There is zero evidence this is the case. You are making up baseless accusation, probably due to partisan motivations.\n\nedit: love the downvotes. I guess HN really is Reddit now. You can make any accusation without evidence and people are supposed to just believe it. If you call it out you get downvoted."
}
,
{
"id": "46937429",
"text": "Is there any evidence the opposite is the case?"
}
,
{
"id": "46938025",
"text": "It doesn’t work like that. The burden is on the person making the claim. If you are going to accuse someone of posting an AI-written article you need you show evidence."
}
,
{
"id": "46939137",
"text": "It's a losing strategy in 2026 to assume by default that any questionable spam blog/comment/etc content is written by an actual human unless proven otherwise.\n\nBesides, if there are enough red flags that make it indistinguishable from actual AI slop, then chances are it's not worth reading anyway and nothing of value was lost by a false positive."
}
,
{
"id": "46938132",
"text": "Please don't tell me you read that article and thought it was written by a person. This is clearly AI generated."
}
,
{
"id": "46940672",
"text": "What evidence are you expecting exactly? It's vacuous AI slop that spends 1000 words just making vague assertions about how incredible OpenClaw is without a single actual example. There's nothing here, it's not real. You are going to struggle going forward if you can't detect AI slop this obvious."
}
,
{
"id": "46937669",
"text": "Did they even end up launching and maintaining the project? Did things break and were they able to fix it properly? The amount of front-loaded fondness for this technology without any of the practical execution and follow up really bugs me.\n\nIt's like we all fell under the spell of a terminal endlessly printing output as some kind of measurement of progress."
}
,
{
"id": "46936450",
"text": "It's AI slop itself. It seems inevitable that any AI enthusiast ends up having AI write their advocacy too.\n\nI just give the link to those posts to my AI to read it, if it's not worth a human writing it, it's not worth a human reading it."
}
,
{
"id": "46937811",
"text": "Does it matter?"
}
,
{
"id": "46937515",
"text": "It reads like articles that pretended blockchain was revolutionary. Also the article itself seems like AI slop."
}
,
{
"id": "46932108",
"text": "This is quite a low quality post. There is nothing of substance here. Just hot air.\n\nThe only software I've seen designed and implemented by OpenClaw is moltbook. And I think it is hard to come up with a bigger pile of crap than Moltbook.\n\nIf somebody can build something decent with OpenClaw, that would help add some credibility to the OpenClaw story."
}
,
{
"id": "46936268",
"text": "Given that the authors previous post was about how the Rabbit R1 has “the potential to change the world”, I don’t expect much in the way of critical assessment here."
}
,
{
"id": "46940011",
"text": "Oh, wow, totally forgot about that. I kind of miss the brief period when there was a new absurd LLM-based gadget every week or so (actually, I think they are still coming out; there were some at CES. But everyone has largely lost interest)."
}
,
{
"id": "46932248",
"text": "I was reading the post and had the same feeling of superficiality. I don’t think a human wrote it tbh"
}
,
{
"id": "46934944",
"text": "Very likely part of their bots output. The ultimate goal isn’t to make useful things, but to “teach” others how to do it and convince them how successful they can become."
}
,
{
"id": "46938042",
"text": "There’s a whole new genre of blog posts that are just “finally thanks to AI everyone will know how smart I am. Watch in awe as I tell something to do stuff for me”"
}
,
{
"id": "46932183",
"text": "AI is all facade"
}
,
{
"id": "46932152",
"text": "My openclaw built skills (python scripts) to interact with the Notion API which allows it to make work items for me and evenly distribute them, setting due dates on my calendar."
}
,
{
"id": "46932180",
"text": "It’s a fun example, because openclaw is the boss in it and you are the agent."
}
,
{
"id": "46936474",
"text": "These days it feels like there is a ton of pro anthropic astroturfing on this site. Probably it is mostly genuine enthusiasm from sincere people. But nevertheless there are a ton of articles from or about anthropic and within the comments of these you are sure to find, often at the top, someone staunchly defending the superiority of engineering everything via agentic use of the in fashion Claude model. If they are truly right than I don't see the need for proselytizing like they do. The proof is in the pudding. That is, if your choices are truly the best and fastest way to produce software inevitably the market and industry will reflect this. But it feels like they don't want to let results speak for themselves they need to hype up their claims continually and forcibly shove this down people's throats"
}
,
{
"id": "46938834",
"text": "I think some of it might be genuine. For people that don't code (like management), going from 0 to being able to create a landing page that looks like it came from a big corporation is a miracle.\n\nThey are not able to comprehend that for anything more complicated than that, the code might compile, but the logical errors and failure to implement the specs start piling up."
}
,
{
"id": "46938022",
"text": "I’ve also been a little suspicious of the vote counts these days. Pro AI stuff regular hitting like 800 votes. The codex announcement hit like 1500? Like what’s goin on here"
}
,
{
"id": "46938431",
"text": "If you check the OpenClaw discord, a common sentiment there is \"it works but only if you use Opus.\" That seems to be the actual situation now.\n\nGrok 4 Fast told me its own internal system prompt has rules against autonomous operation, so that might have something to do with it. I am having decent results with it though."
}
,
{
"id": "46936844",
"text": "My pet peeve with AI is that it just accelerates whatever has already been automated or can be automated easily, but could not touch the bastions of government service, financial service, schools and health services that are way less automated. They keep eating ourselves’ lunch without touching the real problems.\n\nFor me the pain point has always been with non-IT people/companies. They are way more accustomed with phone or even in person appointments. They in general have way more of a say than me, the customer.\n\nCan Openclaw make and take phone calls for me to make appointments? Can Openclaw do chores for me? Can Openclaw meet with contractors for me? None of them it can do. It can make notes for me (useless as most notes are useless). It can scrap websites for me (not very interesting as why would I want to collect so much knowledge?). It can probably automate anything that already has an endpoint or whatever, but I don’t mind write code for my own projects. I always failed to understand why anyone would want to let AI write most of the code of their PERSONAL project — unless they want to sell them quickly.\n\nI’m just a frustrated old man I guess."
}
,
{
"id": "46936918",
"text": "It can make/take phone calls[0], but they need to be prompted on the nature of the call, the data they need, and how to collect it. They can also output the results of the call via API. An AI agent from Masterworks recently called me using this technology.\n\n[0] https://vapi.ai/"
}
,
{
"id": "46937087",
"text": "> My pet peeve with AI is that it just accelerates whatever has already been automated or can be automated easily ....\n\n> I’m just a frustrated old man I guess.\n\nI think this is a great summary of the failure of vision that a lot of tech people are having right now.\n\n> automate anything that already has an endpoint or whatever\n\nFacebook used to have API's, Reddit used to have API's, amazon used to have API's\n\nThey are gone.\n\nEnshitification and dark patterns have taken over.\n\n\"Hey open claw, cancel service xxx\" where XXX is something that is 17 steps and purposely hard to cancel so they keep your money.\n\nWhat's going to happen when your AI tool can go to a website and strip the ad's off and return you just the text? What happens when it can build a customized news feed that looks less like Facebook and more like HN? Aren't we just gaining back function we lost with the death of RSS?\n\nConsumers are mad about the hype of AI but the moment that it can cut through the bullshit we keep putting in their way it's going to wreck business MODELS, and the choice will be adapt or die. Start asking your \"AI\" tools to do all the basic, tedious bullshit tasks that are low risk (you have a ton of them) and if it gets 1/4 of them done your going to free up a ton of your own time."
}
,
{
"id": "46936608",
"text": "This is from the same person who wrote this [1]\n\n[1] https://reorx.com/blog/rabbit-r1-the-upgraded-replacement-fo..."
}
,
{
"id": "46936402",
"text": "Last night I was debugging a website where some users, some times were getting a message that they were attempting to sign up too many times, even when they only had tried to sign-up once.\n\nI tried using LLMs to help debug at different points, but they went in circles on bad ideas, even when I gave them what turned out to be a correct clue.\n\nRoot cause turned out to be that IPv6 wasn't enabled for Docker networking, but was enabled for the websites DNS. So people who connected over IPv6 were getting their IPs all converted to the same internal Docker IP before being handed to the per-IP throttling algorithm.\n\nI spotted that there were no IPv6 IPs in the logs, but the LLMs missed that the key pattern was the absence of something expected, instead drawing wrong conclusions.\n\nSo no, I'm not about to turn OpenClaw loose on building anything at all complex."
}
,
{
"id": "46937106",
"text": "By not trusting OpenClaw on your system, you are missing out on lot of 0-days and 10/10 CVEs!"
}
,
{
"id": "46939026",
"text": "skill issue"
}
,
{
"id": "46935655",
"text": "> My role as the programmer responsible for turning code into reality hasn’t changed\n\n> OpenClaw gave me the chance to become that super manager [...] A manager shouldn’t get bogged down in the specifics—they should focus on the higher-level, abstract work\n\nThese two propositions seem to be highly incompatible"
}
,
{
"id": "46932078",
"text": "> My answer is: become a “super manager.”\n\nHonestly I'd rather die"
}
,
{
"id": "46936155",
"text": "\"and then the engineers turned themselves into managers, funniest thing I've ever seen\""
}
,
{
"id": "46936531",
"text": "> Twelve voices were shouting in anger, and they were all alike. No question, now, what had happened to the faces of the pigs. The creatures outside looked from pig to man, and from man to pig, and from pig to man again; but already it was impossible to say which was which."
}
,
{
"id": "46939369",
"text": "Something sus about these posts that promote OpenClaw specifically, even on X when ClawdBot was first popping up - an unusual number of people were promoting it all without specific information on why it was useful. All the usual suspects were also promoting it (the 'dev influencer' accounts). Is this a new(?) tactic on hyping up a github repo for engagement?"
}
,
{
"id": "46941162",
"text": "- Dear OP, how much did you get paid in crypto to write this post?\n\n- Because the seasoned developers have something entirely different to say https://www.xda-developers.com/please-stop-using-openclaw/\n\n- Also please stop spamming HN with this stuff"
}
,
{
"id": "46936165",
"text": "Besides that blog post obviously being written by AI, can someone here confirm how credible the hype about openclaw is? I'm already very proficient at using Claude Code anywhere, so what would i gain really with openclaw?"
}
,
{
"id": "46936636",
"text": "I played with it extensively for three days. I think there are a few things it does that people are finding interesting:\n\n1. It has a lot of files that it loads into it's context for each conversation, and it consistently updates them. Plus it stores and can reference each conversation. So there's a sense of continuity over time.\n\n2. It connects to messaging services and other accounts of yours, so again it feels continuous. You can use it on your desktop and then pick up your phone and send it an iMessage.\n\n3. It hooks into a lot of things, so it feels like it has more agency. You could send it a voice message over discord and say \"hey remember that conversation about birds? Send an email to Steve and ask him what he thinks about it\"\n\nIt feels more like a smart assistant that's always around than an app you open to ask questions to.\n\nHowever, it's worth stressing how terrible the software actually is. Not a single thing I attempted to do worked correctly, important issues (like the discord integration having huge message delays and sometimes dropping messages) get closed because \"sorry we have too many issues\", and I really got the impression that the whole thing is just a vibe coded pile of garbage. And I don't like to be that critical about an open source project like this, but I think considering the level of hype and the dramatic claims that humans shouldn't be writing code anymore, I think it's worth being clear about.\n\nEnded up deleting it and setting up something much simpler. I installed a little discord relay called kimaki, and that lets me interact with instances of opencode over discord when I want to. I also spent some time setting up persistent files and made sure the llm can update them, although only when I ask it to in this case. That's covered enough of what I liked from OpenClaw to satisfy me."
}
,
{
"id": "46940031",
"text": "> You could send it a voice message over discord and say \"hey remember that conversation about birds? Send an email to Steve and ask him what he thinks about it\"\n\nAh, so it's a device for irritating Steve, got it."
}
,
{
"id": "46938687",
"text": "> You could send it a voice message over discord and say \"hey remember that conversation about birds? Send an email to Steve and ask him what he thinks about it\"\n\nif one of my friends sent me an obviously AI-written email, I think that I would cease to be friends with them..."
}
,
{
"id": "46938570",
"text": "> “hey remember that conversation about birds? Send an email to Steve and ask him what he thinks about it”\n\nIsn’t the “what he thinks about it” part the hardest? Like, that’s what I want to phrase myself - the part of the conversation I’d like to get their opinion on and what exactly my actual request is. Or are people really doing the meme of sending AI text back and forth to each other with none the wiser?"
}
,
{
"id": "46938724",
"text": "I think in the context of business communication; yeah a lot of people are doing that. Which, to be honest, I don't think it the worst thing ever. Most corporate communication is some basic information padded out with feigned personal interest and rehearsed politeness, so it's hardly a huge loss.\n\nFor personal communication between friends it would be horrible. Authenticity has to be one of the things I value most about the people I know. Didn't mean to imply from that example that I did or would communicate that way."
}
]
</comments_to_classify>
Based on the comments above, assign each to up to 3 relevant topics.
Return ONLY a JSON array with this exact structure (no other text):
[
{
"id": "comment_id_1",
"topics": [
1,
3,
5
]
}
,
{
"id": "comment_id_2",
"topics": [
2
]
}
,
{
"id": "comment_id_3",
"topics": [
0
]
}
,
...
]
Rules:
- Each comment can have 0 to 3 topics
- Use 1-based topic indices for matches
- Use index 0 if the comment does not fit well in any category
- Only assign topics that are genuinely relevant to the comment
Remember: Output ONLY the JSON array, no other text.
50