claude-use 6.1.0 → 6.2.1

package/README.md

@@ -4,6 +4,8 @@
 
 A profile manager and launcher for [Claude Code](https://claude.com/claude-code) that lets one person run multiple logins from one machine while controlling — precisely, and per working directory — what gets shared between them.
 
+[![npm downloads chart, log scale](https://shieldcn.dev/chart/npm/claude-use.svg?bg=transparent&logo=false&yScale=log)](https://www.npmjs.com/package/claude-use)
+
 ## The problem
 
 Claude Code keeps everything it knows in one place: `~/.claude`. Skills, memory, conventions, but also every conversation transcript, session file, and task list you've ever produced, across every project you've ever touched. If you want a second login (a personal account alongside a work one, say) or you want to keep one client's work cleanly separated from another's, there's no built-in way to say "share the skills and conventions, but not the history" — it's all one directory, all or nothing.
@@ -43,6 +45,8 @@ That's it — with no further configuration, everything in `~/.claude` that isn'
 - **An identity** is a login: the thing that owns credentials and daemon state, selected with `claude-use run @<name>` or, once `claude-use shim enable` has run, `claude @<name>`.
 - **A configuration profile** is a reusable, named bundle of sharing rules, independent of any identity, resolved per working directory via directory rules or a committed `.claude-use.json`.
 
+A third, optional thing sits on top of identities: **a pool** is a named list of them. Select `pool:<name>` where an identity name goes (`claude @pool:subs`) and claude-use picks the member whose unused quota is closest to expiring, skipping any that are refused right now, using the usage it already records. See [docs/configuration-model.md](docs/configuration-model.md#pools-picking-an-account-at-launch).
+
 Every top-level entry in `~/.claude` is classified into one of five categories, shipped as a default map (`config/categories.default.json`):
 
 | Category | Default shared? | Example entries |
@@ -64,7 +68,7 @@ The full mechanics, including the credential block, the merge algorithm, conditi
 ## CLI reference
 
 ```
-claude-use <noun> <verb> [name] [options]      # nouns: identity, profile, provider, rule
+claude-use <noun> <verb> [name] [options]      # nouns: identity, profile, pool, provider, rule
 
 claude-use identity add <name>
 claude-use identity list [--json]
@@ -86,6 +90,14 @@ claude-use profile show <name> [--json]
 claude-use profile remove <name> [--yes]
 claude-use profile use <name>               # the global default configuration profile
 
+claude-use pool add <name> --identity <identity>...
+claude-use pool set <name> --identity <identity>...
+claude-use pool list [--json]
+claude-use pool show <name> [--json]
+claude-use pool remove <name> [--yes]
+claude-use pool use <name>
+claude-use pool pick <name> [--json]
+
 claude-use provider add <name> --display-name <name> (--base-url <url> | --kind codex) (--credential <source>)... [--credential-target <bearer|apiKey>] [--env KEY=VALUE]...
                                               [--codex-default-model <model>] [--codex-model <tier=model>]... [--codex-effort <none|low|medium|high>]
 claude-use provider set <name> [--display-name <name>] ([--base-url <url>] | --kind codex) [--credential <source>]... [--credential-target <bearer|apiKey>] [--env KEY=VALUE]... [--unset-env KEY]...
@@ -116,7 +128,7 @@ claude-use run [@<identity>] [launch flags] [claude arguments]
   # launch flags, recognised only before a `--` terminator:
   #   --identity <name>  --config-profile <name>  --provider <name> | --no-provider
   #   --category <category>=<bool>  --share <category>/<path>  --hide <category>/<path>   (each repeatable)
-  #   --[no-]skip-permissions  --[no-]remote-control  --[no-]headroom  --[no-]track-usage
+  #   --[no-]skip-permissions  --[no-]remote-control  --[no-]headroom  --[no-]track-usage  --[no-]wait
 claude @<identity> ...                      # the same, once `claude-use shim enable` has run
 ```