claude-threads 1.33.0 → 1.33.1
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/CHANGELOG.md +7 -0
- package/dist/index.js +811 -755
- package/dist/mcp/mcp-server.js +165 -144
- package/docs/CONFIGURATION.md +8 -0
- package/package.json +1 -1
package/docs/CONFIGURATION.md
CHANGED
|
@@ -554,6 +554,14 @@ claudeAccounts:
|
|
|
554
554
|
| `apiKey` | One of | Anthropic API key. Billed against that key; session history stays under the bot's default `HOME`. |
|
|
555
555
|
| `displayName` | No | Human-readable label in UI (defaults to `id`) |
|
|
556
556
|
|
|
557
|
+
⚠️ An account with `home` owns the **whole** Claude profile, not just its
|
|
558
|
+
credentials: user settings, hooks and global MCP configuration are read from
|
|
559
|
+
that home too. Anything the daemon inherited that could point elsewhere — an
|
|
560
|
+
API key, a bearer token, `CLAUDE_CONFIG_DIR` — is cleared for that child, or
|
|
561
|
+
the account you selected would be silently overridden by the one the daemon
|
|
562
|
+
runs as. Daemon-level hooks and settings therefore do **not** carry into a
|
|
563
|
+
pooled account; put them in the account's own home.
|
|
564
|
+
|
|
557
565
|
Exactly one of `home` or `apiKey` should be set per account. Persisted sessions record which account they ran under and resume on the same one.
|
|
558
566
|
|
|
559
567
|
## Environment Variables
|
package/package.json
CHANGED