claude-use 6.0.0 → 6.2.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -4,6 +4,8 @@
4
4
 
5
5
  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.
6
6
 
7
+ [![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)
8
+
7
9
  ## The problem
8
10
 
9
11
  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'
43
45
  - **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>`.
44
46
  - **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`.
45
47
 
48
+ 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).
49
+
46
50
  Every top-level entry in `~/.claude` is classified into one of five categories, shipped as a default map (`config/categories.default.json`):
47
51
 
48
52
  | Category | Default shared? | Example entries |
@@ -64,7 +68,7 @@ The full mechanics, including the credential block, the merge algorithm, conditi
64
68
  ## CLI reference
65
69
 
66
70
  ```
67
- claude-use <noun> <verb> [name] [options] # nouns: identity, profile, provider, rule
71
+ claude-use <noun> <verb> [name] [options] # nouns: identity, profile, pool, provider, rule
68
72
 
69
73
  claude-use identity add <name>
70
74
  claude-use identity list [--json]
@@ -79,13 +83,21 @@ claude-use identity resolve-conflicts <name> # interactively resolve a retained
79
83
  claude-use profile add [name] [--extends <profile>]... [--description <text>] # interactive with no options on a terminal
80
84
  claude-use profile set <name> [--category <category>=<bool>]... [--entry <category>/<path>=<bool>]...
81
85
  claude-use profile set <name> [--extends <profile>]... [--no-extends] [--description <text> | --no-description]
82
- claude-use profile set <name> [--[no-]launch-skip-permissions] [--[no-]launch-remote-control] [--[no-]launch-headroom]
86
+ claude-use profile set <name> [--[no-]launch-skip-permissions] [--[no-]launch-remote-control] [--[no-]launch-headroom] [--[no-]launch-track-usage]
83
87
  claude-use profile set <name> [--launch-provider <provider> | --no-launch-provider]
84
88
  claude-use profile list [--json]
85
89
  claude-use profile show <name> [--json]
86
90
  claude-use profile remove <name> [--yes]
87
91
  claude-use profile use <name> # the global default configuration profile
88
92
 
93
+ claude-use pool add <name> --identity <identity>...
94
+ claude-use pool set <name> --identity <identity>...
95
+ claude-use pool list [--json]
96
+ claude-use pool show <name> [--json]
97
+ claude-use pool remove <name> [--yes]
98
+ claude-use pool use <name>
99
+ claude-use pool pick <name> [--json]
100
+
89
101
  claude-use provider add <name> --display-name <name> (--base-url <url> | --kind codex) (--credential <source>)... [--credential-target <bearer|apiKey>] [--env KEY=VALUE]...
90
102
  [--codex-default-model <model>] [--codex-model <tier=model>]... [--codex-effort <none|low|medium|high>]
91
103
  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]
116
128
  # launch flags, recognised only before a `--` terminator:
117
129
  # --identity <name> --config-profile <name> --provider <name> | --no-provider
118
130
  # --category <category>=<bool> --share <category>/<path> --hide <category>/<path> (each repeatable)
119
- # --[no-]skip-permissions --[no-]remote-control --[no-]headroom
131
+ # --[no-]skip-permissions --[no-]remote-control --[no-]headroom --[no-]track-usage --[no-]wait
120
132
  claude @<identity> ... # the same, once `claude-use shim enable` has run
121
133
  ```
122
134