shraga 0.1.106 → 0.1.108

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
@@ -194,10 +194,12 @@ with:
194
194
  - **Your Claude subscription (recommended).** Run `claude auth login` once and leave
195
195
  `ANTHROPIC_API_KEY` unset. The agent runs on your plan, with no metered API charges.
196
196
  - **An API key.** Set `ANTHROPIC_API_KEY` in `.env` if you would rather pay per token.
197
- - **Per-user subscriptions (optional).** Set `CLAUDE_ACCOUNTS_DIR` (e.g. `/opt/shraga/shared/claude-accounts`,
198
- outside `data/`). A requester whose email (lowercased) has a folder there runs on that folder's login;
199
- everyone else keeps the default. Log each user in once:
200
- `CLAUDE_CONFIG_DIR=/opt/shraga/shared/claude-accounts/you@example.com claude auth login`.
197
+ - **Per-user subscriptions (optional).** A requester whose email resolves to a contact with a
198
+ `workspace/users/<contactId>/.claude` folder runs on that folder's login; everyone else keeps the default.
199
+ The folder is data-sync ignored and hidden from the workspace UI. Log each user in once:
200
+ **Agent Configuration → Claude subscription** in the web UI (Connect / Replace / Use shared; the owner
201
+ also manages the shared login there, no SSH), or by hand:
202
+ `CLAUDE_CONFIG_DIR=<DATA_DIR>/workspace/users/<contactId>/.claude claude auth login`.
201
203
  A folder without a login fails the run with the CLI's 401 — it never falls back to the default account.
202
204
  Routed runs don't feed the usage gauge. Same trust model as the default login: the agent's Bash can
203
205
  read a routed login just as it can read the default one.