claude-code - 💡(How to fix) Fix [DOCS] Billing implications for `claude remote-control` on June 15th

Documentation Type

Unclear/confusing documentation

Documentation Location

https://code.claude.com/docs/en/headless

Section/Topic

Billing classification of claude remote-control

Current Documentation

Starting June 15, 2026, Agent SDK and claude -p usage on subscription plans will draw from a new monthly Agent SDK credit, separate from your interactive usage limits. See Use the Claude Agent SDK with your Claude plan for details. ~ https://code.claude.com/docs/en/headless

What's Wrong or Missing?

I just noticed that claude remote-control starts a child process for each session spawned through the remote control server:

❯ ps --forest -o pid,tty,stat,time,cmd -g 4064992
    PID TT       STAT     TIME CMD
4064992 ?        Ssl  00:14:28 /home/<snip>/.local/bin/claude remote-control
4065302 ?        Sl   00:28:24  \_ /home/<snip>/.local/share/claude/versions/2.1.143 --print --sdk-url https://api.anthropic.com/v1/code/sessions/<snip> --session-id <snip>

As you can see, the child process is claude --print. As far as I could tell, nowhere is it stated that it works this way, it's an implementation detail. However, since claude --print will draw from the "automation bucket" starting June 15th, what does that imply for claude remote-control? Will sessions spawned through claude remote-control draw from the automation bucket?

I couldn't find any source, not in the docs and not in any public statement, that clarifies this.

Suggested Improvement

This is in dire need of clarification. If claude remote-control will indeed draw from the automation bucket starting June 15th, this needs to be documented.

Impact

Medium - Makes feature difficult to understand

Additional Context

https://code.claude.com/docs/en/remote-control

No response