Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 8 additions & 1 deletion docs/guides/claude-subscription.md
Original file line number Diff line number Diff line change
Expand Up @@ -30,11 +30,18 @@ This is [Anthropic's way for scripts](https://code.claude.com/docs/en/authentica
token can only make model requests and has no refresh. `hermit check` and `hermit train` refuse a run on the login
when the variable is not set or the CLI is missing or too old (2.1.248 or later; these pages were tested on 2.1.318).

Running the official CLI yourself on that sign-in, interactively or as `claude -p` from your own scripts, is an end user
signing in to the unmodified binary with their own subscription, which the terms permit (within their "ordinary,
individual usage"). What Hermit avoids is holding the sign-in itself.

Why not the sign-in you already have (`claude auth login`, in `~/.claude/.credentials.json` or the macOS Keychain)? A
session needs a home of its own, and one working from a copy of that file refreshes it when its access token nears
expiry: the refresh token rotates, and your own Claude Code is left holding a dead one. A run could sign you out of your
own sessions. Codex's route (`login: chatgpt`) keeps a shared copy of its login for this reason; here the token makes
the copy unnecessary, and the terms above advise against one.
the copy unnecessary. Hermit also keeps no copy because of how it reads the terms above: a shared copy would have
Hermit store and refresh your credentials, which their rule that developers "may not collect, store, or intermediate
Claude.ai credentials" may cover. That rule is written for products that serve other people, and the terms do not say
whether a tool you run for yourself counts; Hermit takes the cautious reading.

Nothing else may pay for a session on the login. In print mode the CLI takes an `ANTHROPIC_API_KEY` over any sign-in
without asking, and a settings file can bring in another key, a key helper or another host. So the session's environment
Expand Down
7 changes: 5 additions & 2 deletions hermit/agent/base/login.py
Original file line number Diff line number Diff line change
Expand Up @@ -11,8 +11,11 @@
the user exports as CLAUDE_CODE_OAUTH_TOKEN: Anthropic's way for scripts (a year, model requests only, no refresh). The
token passes through the environment to the official CLI and nothing here reads, keeps or copies a credential: no
shared copy, no write-back. The user's `claude` sign-in (~/.claude/.credentials.json, the Keychain on macOS) is left
alone on purpose: a session refreshing a copy of it rotates the refresh token under the user's own Claude Code, and
Anthropic's terms do not let a third-party tool collect, store or intermediate such credentials.
alone on purpose: a session refreshing a copy of it rotates the refresh token under the user's own Claude Code. A shared
copy, as Codex's login keeps, would have this tool store and refresh the credentials, which Anthropic's rule that
developers "may not collect, store, or intermediate Claude.ai credentials" may cover; the terms speak of products that
serve other users, and this reads them cautiously. Running the official CLI yourself on that sign-in (`claude -p` from
your own scripts included) is ordinary use the terms permit; only this tool's holding of it is avoided.

A sandbox that runs a login's sessions allows the hosts they reach (`hosts`); the token passes by name with each
session that runs on it, never to the sandbox's other commands.
Expand Down
Loading