Important note about Claude subscription usage in NeverWrite starting June 15, 2026 #83
jsgrrchg
announced in
Announcements
Replies: 1 comment 1 reply
-
|
https://x.com/zeddotdev/status/2054653400789225638. It looks like Zed is working on a TUI wrapper. |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
https://x.com/zeddotdev/status/2055014285512728722. Zed had a great idea, making terminal threads live in the agent's sidebar. Exploring to do the same here! Also exploring how to make NeverWrite's change control layer compatible with Claude interactive terminal. |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi everyone,
Anthropic recently published new official guidance about how Claude subscription plans will apply to Claude Agent SDK usage starting on June 15, 2026. Since NeverWrite supports Claude through an ACP adapter built on top of the Claude Agent SDK, I want to share what I currently understand and what it may mean for NeverWrite users.
The short version: if you use Claude in NeverWrite through Claude subscription login, usage may no longer draw from the same normal Claude subscription limits used by Claude web, Claude desktop, or interactive Claude Code. Based on Anthropic's docs, Agent SDK usage will instead draw from a separate monthly Agent SDK credit attached to eligible Claude plans.
What Anthropic announced
Anthropic says that, starting June 15, 2026, Claude Agent SDK usage,
claude -p, Claude Code GitHub Actions, and third-party apps built on the Agent SDK can use a separate monthly credit for eligible Claude plans.The announced monthly credits are:
Anthropic also says this credit is per user, refreshes each billing cycle, does not roll over, and is consumed before extra usage. If the credit runs out, further Agent SDK usage can continue only if extra usage is enabled; otherwise, requests should stop until the credit refreshes.
What this means for NeverWrite
NeverWrite currently exposes multiple Claude connection methods:
The route most likely affected by Anthropic's new Agent SDK credit system is:
Claude subscription
NeverWrite's Claude runtime is based on the official ACP adapter for Claude Agent SDK, so it appears to fit Anthropic's category of third-party apps that authenticate with a Claude subscription through the Agent SDK.
That said, I want to be precise: this is my current reading of Anthropic's official docs plus the architecture of the Claude ACP adapter. I still need to validate the exact billing behavior in practice once the change is live.
API keys are different
If you use an Anthropic API key in NeverWrite, this change should not give that API key a subscription credit. Anthropic's docs say Claude Developer Platform API key usage continues to be billed as pay-as-you-go / API usage.
This distinction matters:
Important warning about
ANTHROPIC_API_KEYAnthropic documents that Claude Code prioritizes the
ANTHROPIC_API_KEYenvironment variable over an authenticated Claude subscription.This means that if
ANTHROPIC_API_KEYis set on your machine, Claude may use API billing even if you expected subscription usage. If you want to use Claude through your subscription, Anthropic recommends keepingANTHROPIC_API_KEYunset and checking your active auth state.I am reviewing how NeverWrite should surface this more clearly so users do not accidentally use the wrong billing route.
Possible workaround: Claude Code in the terminal
One workaround, although not a clean one, is to use interactive Claude Code directly from a terminal inside NeverWrite instead of using NeverWrite's native Claude provider.
According to Anthropic's current docs, interactive Claude Code continues to use the normal Claude subscription limits. So if you run Claude Code yourself in a terminal session, that may avoid the Agent SDK credit path used by NeverWrite's native Claude integration.
The tradeoff is significant: this bypasses NeverWrite's own control layer. You would not get the same native NeverWrite experience around agent sessions, structured review, inline change control, accept/reject flows, workspace-aware UI, or the guardrails I build around provider behavior. In other words, it can be a practical escape hatch for some users, but it is not equivalent to using Claude as a first-class NeverWrite provider.
What I am doing next
Before June 15, there is no immediate action required inside NeverWrite.
After the change goes live, I plan to verify the behavior with an eligible Claude subscription by checking whether NeverWrite usage appears under the Agent SDK credit flow rather than Claude Console API billing.
I am also considering UI copy and safeguards to make the billing route clearer, especially around:
ANTHROPIC_API_KEY.Official references
I know billing changes are frustrating, especially for power users who rely on local tools and agent workflows. My goal is to keep NeverWrite transparent here: Claude will remain supported, but I want the app to make it very clear which Claude route you are using and what that route may cost.
Beta Was this translation helpful? Give feedback.
All reactions