Join the discussion

Write your take first — we'll ask for email only when you're ready to publish.

  • Hacker News
  • Things like these (Google also banned me from Antigravity for briefly using an agent) and the massive quality swings made me cancel all 3 subs last week and resort to my local Qwen 3.6 only. Open models are already great and only getting better, and I really enjoy the privacy and consistency of a model I run myself.
  • This is the future.
  • How much VRAM do you need to achieve decent performance?
  • Spent the better part of a week trying to integrate local models into my LazyVim workflow. I've tried both Avante and CodeCompanion and have yet to find any configuration which remotely works. Either it goes into an endless loop, the project directory gets filled with garbage or it can't find the file to apply changes to despite it just being read from. Not sure if it's a Qwen problem, plugins, or Ollama.
  • I don't think anyone is questioning all the benefits of using local LLMs. Those are readily apparent.

    I just don't believe for an instant that they're anywhere in the same ballpark of capabilities as running Opus or similar. My time is the most valuable resource. Opus would need to be SIGNIFICANTLY more costly and unstable for me to start entertaining local models for day-to-day development.

    Perhaps whatever work you're doing makes this trade-off more sensible, but I struggle to see how that could be true. I'm averse to running Sonnet on a large amount of software engineering problems - let alone Qwen.

  • They are trying to make a moat where no possibility of creating a moat exists.

    It’s a huge mistake at the level of IBM trying to reestablish dominance over PCs by making MicroChannel the new standard; this failed horribly and cost IBM its market leadership and reputation.

    MCA was technically better at the time, but the industry responded with EISA and VLBus which led to PCI and today’s PCIe.

  • If anyone is interested in a peek into why they are being so aggressive, check the “AI Hype” board [1]; beyond all the interesting local models (why I read it), it is usually filled with projects for circumventing LLM provider restrictions which are wildly popular (and frequently Chinese- no shade).

    The #3 result today is: “End-to-end protocol replay toolkit for ChatGPT Plus/Team/Pro subscription with from-scratch hCaptcha solver and empirical anti-fraud research”. The “research” for anti-fraud is “how to get around it”.

    It looks a lot like an arms race, and we are getting caught in the middle of it.

    1. https://hype.replicate.dev/

  • That’s incredibly frustrating.

    I’ve got a NixOS Qemu VM I use to run openclaw in. I had Claude help me set it up, and it runs local models on my own machine in a config based sandbox.

    Why should Claude block or charge extra to work on that?

    Why should Claude care if I have instructions for Hermes or OpenClaw in my project repos?

    This fingerprinting is incredibly sloppy for how much access to a machine Claude code has.

  • If it's just to set up a VM, how much would you even need to use? A couple of cents?
  • Now you've learned the advantage of knowing how to do things yourself. When you depend on untrustworthy agents, you shackle yourself to their idiotic whims. Be careful who you partner with.
  • > This fingerprinting is incredibly sloppy

    What part of "vibe coding" is unclear to you?

    These are the same people that use React as a TUI and render at 60FPS to your terminal in order to update a spinner.

  • same vain as https://news.ycombinator.com/item?id=47952722 ?

      HERMES.md in commit messages causes requests to route to extra usage billing  
      1203 points | 21 hours ago | 524 comments
    
    
    @bcherny well need a bit more than a "Fixed" here... https://github.com/anthropics/claude-code/issues/53262#issue...
  • I mentioned it in that thread, but when the HERMES bug was first reported multiple people on Reddit claimed that it could also be triggered with openclaw specific file names. It makes me think that instead of going just saying, "this approach for defending against 3rd party oauth isn't working" and rolling things back, they just tried to fix forward and continue with the strategy
  • Sounds exactly like what you’d get if you asked Vlaude how to detect OpenClaw usage.
  • That is a huge red-flag. While I understand that they will do some policing/censoring, this is way beyond what I would consider acceptable.

    They can have a different price plan for agentic stuff, but these things where they “accidentally” whoops match on specific keywords and trigger extra usage charges is giving a evil-microsoft-vibe

  • Why is this a red flag? OpenClaw is basically automated abuse of their subscription plans. This is entirely reasonable.
    by dbbk
  • This is fascinating because it makes me think OpenClaw is something of a trojan horse aimed at draining Anthropic's resources. For them to go to this length to stop OpenClaw usage raises some interesting questions and a precedent for closed model vendors.
  • What I don't quite understand is why would one of the most advanced AI labs use rudimentary broken text match heuristics to track and detect abuse. Why not run simple inference on actual turns out of band, and if abuse is detected, adjust the quotas semi-retroactively.
    by lxe
  • It's fascinating to see all these bugs in Claude Code - HERMES.md, this OpenClaw issue, the recent thinking-message pruning and cache-skipping bugs.

    They seem like the class of bugs I see in my vibe-coding experiments, and I think the Claude Code lead has said many times that he/his team don't read the code for Claude Code themselves, that it's basically vibe-coded.

    If Anthropic itself can't make vibe coding work, who can?

    by trb
  • Well to be honest, none of these are likely bugs. HERMES.md maybe... but everything else is likely them testing waters.
  • Has any of this stuff hurt their valuation? Then who says it isn't working?
  • When all these "bugs" align with /A self interest, it's quite a charitable view to attribute these to negligent vibe coding.
  • I suspect there's strong management pressure to not read the code or do "old fashioned coding"

    Because this is the company whose CEO makes public pronouncements about how they're going to exterminate our whole profession any day now, how we won't be needed.

    So if that's your ultimate boss, do you think he's going to let you stop, analyze, cautiously review, hand curate, hand edit?

    To me the thing seems like a science project that got shipped as a product, with a complete lack of proper software engineering quality principles around it.

    A gating procedure like this (and the HERMES.md thing etc) would never get past a code review process in any respectable shop that I've worked at. If I'd put up a code review like this at Google when I was there, it would been a pile-on of senior engineers demanding a better approach, no LGTM would have been given.

    I can only conclude Anthropic is getting high on their own supply.

    In any case, writing code to get features out the door has rarely been the block in our profession. It's usually process and review and understanding requirements.

    And so the entire project feels like a fundamental misunderstanding of what shipping software as a team is actually about.

  • This is very concerning. Their heavy handed tactics haven't impacted me personally yet but I am increasingly nervous and casting about for viable egress paths if I need to flee Claude Code. I really hope they pump the breaks and thoroughly reorient themselves. They are under a lot of competing pressures and probably can't make a decision that won't upset a lot of people (in order to balance growth and capacity etc), but are coming to the worst possible conclusions.

    For instance, maybe you can't afford to take on more customers right now, Anthropic. Maybe if you are severely undermining the customer relationships you already have, you should just admit you can't sell any more 20x plans right now and only accept new customers at lower tiers until you have the necessary capacity.

    This is also a DoS you could drive a truck through, and it's disturbing such an obvious vulnerability was shipped at all.

  • I'm a hair's breadth from switching to a Kimi plan at this point.
  • I have been eyeing off the ollama and minimax plans, but I just don’t know how to compare them. Ollama especially, I have no idea how much usage I could get out of a plan.

    Also, just learned about opencode go from other comments here, so gotta look into that.

  • Codex has been great for me
  • Same here. I'm not even using OpenClaw myself and it's starting to make me nervous. Every week it's a new problem, and then Anthropic deals with it by doing something so stupid and controversial it becomes news. It's really tiresome.
  • > or instance, maybe you can't afford to take on more customers right now, Anthropic. Maybe if you are severely undermining the customer relationships you already have, you should just admit you can't sell any more 20x plans right now and only accept new customers at lower tiers until you have the necessary capacity.

    Or just increase prices for new claude code users? Surely transparent upfront across the board price increases are easier to swallow than hidden context-based pricing changes like this?

  • > casting about for viable egress paths if I need to flee Claude Code

    Check out OpenCode (the OSS product [1]) and OpenCode Go/Zen (the LLMaaS [2]). Use a more expensive model with larger context (like GLM-5.1) for orchestration and cheaper models for coding and iteration on acceptance criteria (writing and passing tests). I also throw a more expensive vision-capable model into the mix like Gemini 3 Flash to iterate on UI tasks using Playwright. With the base usage in Go and pay as you go on cheaper models like MiniMax you can get a lot done for not a lot of coin.

    [1] https://github.com/anomalyco/opencode

    [2] https://opencode.ai/go