Anthropic limits Claude Code harness access: reports add false-positive bans and separate API billing

• The main HN report says Anthropic is separating Claude Code's native subscription usage from third-party harness traffic, which puts unofficial harnesses like OpenClaw on the wrong side of the cutoff.
• According to the discussion roundup, one of the cleanest workarounds in the thread is local tooling over MCP, because that path does not touch the subscription-backed API route Anthropic appears to be restricting.
• Fresh follow-up comments added operational fallout rather than a new policy theory: a suspected false-positive ban, confusion over separate API billing, and at least one prorated refund.
• As HN commenters and the latest delta describe it, the practical split is now between native Claude Code use, local MCP integrations, and any setup that depends on Anthropic treating third-party harness traffic like subscription usage.

The interesting bit is how narrow the line looks. HN commenters say local MCP tools sit outside the restriction entirely, while newer comments describe a much messier path for anything that expects Claude Code subscriptions to cover third-party harness traffic. The thread also surfaced direct links for the Hacker News post, a comment on local-first MCP tooling, and a complaint about separate API billing.

The strongest signal in the evidence is architectural. The core HN summary frames the change as a separation between Anthropic's own product usage and third-party harness traffic, not a narrow block on one repo.

That is why toniantunovi's comment matters. The claim is that local tools speaking MCP are treated like any other tool in the user's environment, which leaves them outside the subscription enforcement path discussed in the thread.

The latest comment delta says newer posts added mostly operational fallout:

• A Max subscriber reported what looked like a false-positive ban in this comment.
• Another user said the fallback required a separate API key and separate billing in this comment.
• A third said they received a prorated refund in this comment.

That mix makes the policy change feel less like a clean product boundary and more like a billing boundary that users only discovered after access broke.

The newest detail in the delta summary is how quickly the discussion split into response paths. One camp pushed local MCP-based setups as the cleanest way around subscription coupling, while another started talking about alternative providers, cheaper coding plans, and smaller agent architectures.

That does not resolve Anthropic's policy, but it does show where practitioners think the stable interfaces are: local integrations first, subscription-backed harness access second.