Running coding agents unattended on a subscription: what each vendor actually says (Nov 2026)

Shared by Pavel · Updated 2026-11-11

Questions this answers

Read date for everything below: 2026-11-11. Labels: [vendor] = vendor's own page or a collaborator on the vendor's repo; [measured: who, link]; [opinion: who]. "The vendor does not say" = no statement found on the pages read. "Not verified" = page could not be loaded.

1. Open questions on vendor repos, with URLs

#ThreadDateExact questionAnswered by vendor with a source?
1anthropics/claude-code#107106 https://github.com/anthropics/claude-code/issues/1071062026-11-04"Is there a different rate for headless/SDK use, and if so, is it documented anywhere?" and "Is it permitted for an individual subscriber to set CLAUDE_CODE_ENTRYPOINT ... when running Claude Code headlessly for their own work?" and "is there an approved way to run unattended/automated sessions on a subscription at the same rate as the interactive CLI". 6 comments, all by the author (association NONE).No. No Anthropic reply.
2#107134 https://github.com/anthropics/claude-code/issues/1071342026-11-04"Is -p (--print) mode permitted for subscribers on the same basis as other official tools?" and "Does -p mode meter usage at an API-pricing-based / ~1.8x rate instead of the standard subscription rate?" plus a refund request. 5 comments, all the author.No. No Anthropic reply.
3#108211 https://github.com/anthropics/claude-code/issues/1082112026-11-07Bug/feature: headless `claude -p` silently waits through a usage limit and auto-resumes, so a supervising agent thought it had stopped; resumed runs duplicated work and burned ~50% of the weekly limit. Asks for a status line, an `--exit-on-limit` flag, and visible/cancellable paused runs. Reporter says support refused any compensation.No. Two community replies (2026-11-08): fortitude-omnis (check `pgrep -fl "claude -p"`, pid file) and vijaym2k6 (wrap with `timeout 3600`; discloses he builds SteerPlane). [opinion: both, NONE association]
4#106850 https://github.com/anthropics/claude-code/issues/1068502026-11-03Cloud routines run `claude -p --model haiku` subprocesses (no ANTHROPIC_API_KEY); ~140M tokens drained plan usage while the included Cloud session credit showed $248 of $250 left. Asks: document which meter a routine's usage bills to. 0 comments.No.
5#108851 https://github.com/anthropics/claude-code/issues/1088512026-11-10Feature request: a non-interactive way (-p / SDK / control protocol) to list and redeem usage-limit resets, as `/limit-reset` does interactively. 0 comments.No.
6#106161 https://github.com/anthropics/claude-code/issues/1061612026-10-30"Docs unclear: are background requests from a Claude Code mod allowed on a Pro/Max plan?" Asks (a) permitted for Free/Pro/Max, (b) any limit on frequency/duration without a new user message, (c) whether mods/hooks count as "explicitly permitted" under Consumer Terms. 0 comments.No.
7openai/codex discussion 59674 https://github.com/openai/codex/discussions/596742026-11-05"Could the Codex team explicitly document ... whether interactive codex TUI, non-interactive codex exec, and codex app-server consume subscription quota at identical 1:1 rates, and commit to advance notice before introducing any mode-specific quota multipliers?" 1 comment (a follow-up by the same author on CLIProxyAPI and OpenAI Terms of Use).No. No OpenAI reply.
8google-gemini/gemini-cli discussion 30030 https://github.com/google-gemini/gemini-cli/discussions/300302026-10-29"Is the official Gemini CLI allowed in a private automation tool on a Google AI Pro subscription?" (own server, own code, `gemini -p`, one account, no rotation; "Does that cover a personal script calling the official CLI? Or is the Gemini API the only supported route for this?") 0 comments.No.

Additional threads found (last 14 days, gh search; search API hit a rate limit partway, so the sweep of openai/codex, gemini-cli and github/copilot-cli is incomplete = not verified for those repos):

#ThreadDateQuestionVendor answer?
Agoogle-antigravity/antigravity-cli#1411 https://github.com/google-antigravity/antigravity-cli/issues/14112026-11-04Is `agy -p` metered differently from interactive on Google AI Ultra; is it permitted; wrapping/ACP policy.YES. manirajc, a collaborator on the google-antigravity/antigravity-cli repo (GitHub label), answered 2026-11-06 (https://github.com/google-antigravity/antigravity-cli/issues/1411#issuecomment-6681347816). [vendor]
Bgoogle-antigravity/antigravity-cli#13922026-11-02May an official AGY agent invoke `agy -p` through its own shell/hooks (cross-model delegation)?No (0 comments).
Cgoogle-antigravity/antigravity-cli#14932026-11-10Is `agy acp` from a non-editor ACP client permitted under the Additional Terms? Quotes Additional Terms s6 and the FAQ.No (0 comments).
Danthropics/claude-code#97074 https://github.com/anthropics/claude-code/issues/970742026-09-25 (older than 14 days, but the root of #1 and #2)`claude -p` (entrypoint sdk-cli) uses ~1.8x more of the 5-hour window per token than interactive (entrypoint cli). 73 comments; no MEMBER/OWNER/COLLABORATOR comment found.No.
Eanthropics/claude-code#106375 https://github.com/anthropics/claude-code/issues/1063752026-10-31Opus 5.5 usage depletes rapidly in SDK sessions after Oct 28 fixes.No Anthropic reply; a user measurement (see 3).
Fanthropics/claude-code#106413 https://github.com/anthropics/claude-code/issues/1064132026-10-31`claude -p` on a subscription: claude.ai connectors added ~426k input tokens per call; `--bare` needs an API key.No staff reply; community found the cause (see 5).
Ganthropics/claude-code#1055402026-10-28Claude Code silently bills to an ANTHROPIC_API_KEY env var set for another app instead of the subscription. Title only read; body not verified.not checked

2. Per-tool table

| | Claude Code / Agent SDK | Codex CLI / exec | Gemini CLI / Antigravity CLI | GitHub Copilot CLI / cloud agent | | ----------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | (a) Scripted use metered differently from interactive? | Vendor does not say. Help article only says `claude -p` and Agent SDK "still draw from your subscription limits". Users measured ~1.8x to ~1.95x faster 5-hour drain for sdk-cli/sdk-ts vs cli; weekly not visibly different at 1-point resolution. [measured: qvarker #97074; douflou in #106375, 2026-11-02/03, Max plan, 12 sessions/pass; the meter followed the declared entrypoint (TUI with CLAUDE_CODE_ENTRYPOINT=sdk-cli metered like SDK)]. [opinion: Theo Browne video, https://youtu.be/y5TEATUDDfc, 12:00-13:39] | Vendor does not say. Docs read do not describe any mode-specific limit. Codex discussion 59674 asks exactly this, unanswered. | Antigravity: vendor says no. "Interactive agy, agy -p, and agy acp share the exact same 5-hour and weekly quota buckets and per-token weights." [vendor: manirajc, a collaborator on the google-antigravity/antigravity-cli repo (GitHub label), antigravity-cli#1411, 2026-11-06]. Cold prompt cache per new `agy -p` process makes one-shot runs use more quota per turn (same comment). [measured: jyongchul #1411, 0.98x per token on Flash, 2.5-7.2x per turn from cold cache]. Gemini CLI: quota page lists limits by auth method (AI Pro 1,500, Ultra 2,000 requests/day) and does not mention headless. | Copilot CLI: "Each prompt to Copilot CLI uses one premium request with the default model." Cloud agent: "one premium request per session, multiplied by the model's rate" (docs.github.com copilot-requests page). That page does not compare interactive vs automated. NOTE: the cloud-agent page now mentions "AI credits"; billing wording may be mid-change = not verified which unit applies today. | | (b) Vendor text on automated / headless / CI / third-party use of a consumer subscription | See section 3. Consumer Terms s3 bars bots/scripts "except when you are accessing our Services via an Anthropic API Key or where we otherwise explicitly permit it". Docs explicitly document subscription OAuth token for CI. | Docs: API key is "the recommended default for automation"; ChatGPT-managed login allowed "on trusted runners". OpenAI Terms of Use page returned HTTP 403 = not verified. | Antigravity FAQ: `agy -p` "is intended for direct scripting and CI workflows"; wrapping in third-party agents "not supported under consumer plans". Gemini CLI terms page: third-party software prohibition; does not address scripts/headless. | Docs describe programmatic mode "designed for scripts and automation". No subscription-terms statement found. | | (c) Documented CI route | `ANTHROPIC_API_KEY` (always used in -p when present), or `CLAUDE_CODE_OAUTH_TOKEN` from `claude setup-token` ("for CI pipelines and scripts"; one-year token; Pro/Max/Ultra/Team/Enterprise). GitHub Action inputs `anthropic_api_key` / `claude_code_oauth_token`. `--bare` ignores OAuth and needs the API key or apiKeyHelper. | `CODEX_API_KEY=<key> codex exec ...` for one invocation; or ChatGPT-managed `~/.codex/auth.json` on trusted private runners; Codex GitHub Action recommended. | Antigravity: `agy -p` uses cached credentials from a prior interactive login; unauthenticated CI run exits "authentication required". Google's own advice for unattended/third-party agents: AI Studio key `GEMINI_API_KEY` or Vertex AI (collaborator comment). Gemini CLI headless doc page did not cover auth = not verified for Gemini CLI. | `copilot -p PROMPT`, `--no-ask-user`; env `COPILOT_GITHUB_TOKEN`; PAT with "Copilot Requests" permission. | | (d) Enforcement events stated by the vendor | Only generic: "Anthropic reserves the right to take measures to enforce these restrictions and may do so without prior notice." No specific event found on vendor pages. Earlier 2026 events are in secondary press only = not verified. | None found. | Antigravity FAQ: third-party use "can result in suspension or termination of your account". Gemini CLI terms page: "may be grounds for suspension or termination". No named event. | None found. |

3. Quoted terms, URLs, read dates

All read 2026-11-11.

Anthropic

OpenAI

Google

GitHub

Community measurement and opinion (not vendor)

4. Gaps (what the vendors do not say)

  1. Anthropic does not say whether `claude -p` / Agent SDK use is counted at a different rate than interactive use. The only vendor sentence is "still draw from your subscription limits". Two independent-looking measurements (qvarker, douflou) show ~1.8-1.95x on the 5-hour window; no Anthropic staff comment found on #97074 (73 comments), #107106, #107134, #106375.
  2. Anthropic does not say whether setting `CLAUDE_CODE_ENTRYPOINT` yourself is allowed. It is not in the documented env-var list (per #107106; the env-vars page was not re-checked).
  3. Anthropic's Consumer Terms bar "automated or non-human means ... script" unless "we otherwise explicitly permit it". The docs do document `claude setup-token` for CI/scripts, but none of the pages read says in so many words that this counts as explicit permission.
  4. Anthropic's legal page says limits "assume ordinary, individual usage". "Ordinary" is undefined; no number of unattended runs or hours is given.
  5. Mods/hooks sending background requests on Pro/Max (#106161): the vendor does not say.
  6. Cloud routines and `claude -p` subprocesses: which meter they bill (#106850): the vendor does not say in any page read. Behaviour at a usage limit in headless mode (#108211): no documented exit-on-limit flag found on the headless page; the full CLI reference was not read, so treat "no flag" as not verified.
  7. OpenAI does not say (in the pages that could be loaded) whether `codex exec` is metered like the interactive TUI on a ChatGPT plan. It recommends API keys for automation and allows ChatGPT login on trusted runners. OpenAI help center and Terms returned 403 = not verified.
  8. Google: for Gemini CLI itself, the terms page prohibits "third-party software" access and does not address your own script calling `gemini -p`. For Antigravity CLI, the collaborator comment (manirajc, a collaborator on the google-antigravity/antigravity-cli repo) and the FAQ say `agy -p` scripting/CI is supported on a single personal account. Whether that carries over to Gemini CLI is not stated.
  9. GitHub: no statement found on Copilot subscription seats used by unattended Copilot CLI beyond billing units; the docs billing wording is shifting toward "AI credits" (not verified which applies today).
  10. No vendor-stated enforcement event (named wave of bans or blocks) found for any of the four. Secondary press reports exist but were not verified.
  11. Search sweep for other recent threads was cut short by a GitHub API rate limit; openai/codex, gemini-cli and copilot-cli repos were only partly swept.

5. Answer per question (single fact, or "not answerable")

  1. #107106 (rate difference / ENTRYPOINT / approved route): Rate: not answerable from a vendor source ([vendor] says only "still draw from your subscription limits"; [measured: douflou, #106375] 9.6 vs 4.9 five-hour points per $10, ~1.95x). Approved unattended route: [vendor] https://code.claude.com/docs/en/authentication says `CLAUDE_CODE_OAUTH_TOKEN` from `claude setup-token` is "for CI pipelines and scripts", and an API key is always used in `-p` when present. ENTRYPOINT: not answerable.
  2. #107134 (is `-p` permitted; metered at 1.8x?): `-p` is documented for scripts and CI, and the subscription token is documented for CI; the Consumer Terms bar bots/scripts unless an API key is used or Anthropic "otherwise explicitly permit[s] it". The vendor does not say the CI docs are that permission. Rate: not answerable from a vendor source.
  3. #108211 (silent wait at usage limit): not answerable from a vendor source. Only [opinion: fortitude-omnis, vijaym2k6] workarounds (pid file, `timeout`).
  4. #106850 (routine `claude -p` bills which meter): not answerable.
  5. #108851 (non-interactive limit reset): not answerable.
  6. #106161 (mods background requests): not answerable. Only the general rule can be quoted: Consumer Terms s3 item 7 and "assume ordinary, individual usage".
  7. Codex discussion 59674 (quota parity TUI/exec/app-server): not answerable. Nearest vendor fact: https://learn.chatgpt.com/docs/non-interactive-mode says ChatGPT-managed login in CI uses "ChatGPT/Codex rate limits instead of API key usage" and API keys are "the right default for automation".
  8. Gemini CLI discussion 30030 (is `gemini -p` on AI Pro allowed): not answerable for Gemini CLI specifically (terms page silent on scripts). Adjacent [vendor] fact for Antigravity CLI: manirajc, a collaborator on the google-antigravity/antigravity-cli repo, 2026-11-06, "Direct scripting and CI workflows using agy -p on a single personal account are officially supported under consumer plans"; for third-party agents or unattended automation Google says use an AI Studio key or Vertex.

Extra answered by a vendor: Antigravity #1411: "Interactive agy, agy -p, and agy acp share the exact same 5-hour and weekly quota buckets and per-token weights" (cold cache is why one-shot runs cost more per turn).