@anthropic-ai/claude-agent-sdk 0.3.273 → 0.3.275

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/sdk.d.ts CHANGED
@@ -227,6 +227,21 @@ export declare type CanUseTool = (toolName: string, input: Record<string, unknow
227
227
  * For example, when a Bash command tries to access a path outside allowed directories.
228
228
  */
229
229
  blockedPath?: string;
230
+ /**
231
+ * For `mcp__*` tools: the MCP server serving the tool and where its
232
+ * definition came from. `source: 'sdk'` means one of the in-process
233
+ * servers this SDK host registered (its `name` is the key you registered;
234
+ * only the host can register one); any other value (`plugin`, `user`,
235
+ * `project`, `local`, `dynamic`, `managed`, …) is a server from
236
+ * configuration, whose `name` is the key as authored there — untrusted
237
+ * text, escape it before display. Key trust decisions on `source`, not on
238
+ * the name or the tool-name prefix. Absent for non-MCP tools and on CLIs
239
+ * that predate the field.
240
+ */
241
+ mcpServer?: {
242
+ name: string;
243
+ source: string;
244
+ };
230
245
  /** Explains why this permission request was triggered. */
231
246
  decisionReason?: string;
232
247
  /**
@@ -384,6 +399,7 @@ declare namespace coreTypes {
384
399
  McpSSEServerConfig,
385
400
  McpSdkServerConfig,
386
401
  McpServerConfigForProcessTransport,
402
+ McpServerProvenance,
387
403
  McpServerStatusConfig,
388
404
  McpServerStatus,
389
405
  McpServerToolPolicy,
@@ -465,6 +481,7 @@ declare namespace coreTypes {
465
481
  SDKSessionInfo,
466
482
  SDKSessionStateChangedMessage,
467
483
  SDKSettingsParseError,
484
+ SDKStartupFailureReason,
468
485
  SDKStatusMessage,
469
486
  SDKStatus,
470
487
  SDKSystemMessage,
@@ -756,7 +773,12 @@ export declare function forkSession(_sessionId: string, _options?: ForkSessionOp
756
773
  * Options for forking a session into a new branch.
757
774
  */
758
775
  export declare type ForkSessionOptions = SessionMutationOptions & {
759
- /** Slice transcript up to this message UUID (inclusive). If omitted, full copy. */
776
+ /**
777
+ * Slice transcript up to the message whose `uuid` field equals this value
778
+ * (inclusive). If omitted, full copy. Obtain the value from
779
+ * {@link SessionMessage.uuid} via `getSessionMessages()`, or from the
780
+ * `uuid` you supplied on a streamed {@link SDKUserMessage}.
781
+ */
760
782
  upToMessageId?: string;
761
783
  /** Custom title for the fork. If omitted, derives from original title + " (fork)". */
762
784
  title?: string;
@@ -1126,6 +1148,17 @@ export declare type McpServerConfig = McpStdioServerConfig | McpSSEServerConfig
1126
1148
 
1127
1149
  export declare type McpServerConfigForProcessTransport = McpStdioServerConfig | McpSSEServerConfig | McpHttpServerConfig | McpSdkServerConfig;
1128
1150
 
1151
+ /**
1152
+ * The MCP server serving this tool, for `mcp__*` tools: `name` is the server's config key (for `source: "sdk"`, exactly the name the SDK host registered in `sdkMcpServers` / `mcp_set_servers`; for any other source, the key as authored in that configuration — untrusted text, the same value `mcp_status` and system/init report, to be escaped before display), `source` is where its definition came from — `sdk` (an in-process server the SDK host runs; only the host can register one, so a configured server of the same name never reads `sdk`), `plugin` (a server a plugin ships or registers at runtime), or a config scope (`user`, `project`, `local`, `dynamic` for --mcp-config / `mcp_set_servers` process servers, `managed`, `enterprise`, `claudeai`, `agent`). Key trust on `source`, not on the name or the tool-name prefix. Absent for non-MCP tools.
1153
+ */
1154
+ export declare type McpServerProvenance = {
1155
+ name: string;
1156
+ /**
1157
+ * sdk | plugin | user | project | local | dynamic | managed | enterprise | claudeai | agent — an open set; treat unknown values as an unrecognized configured source, never as sdk.
1158
+ */
1159
+ source: string;
1160
+ };
1161
+
1129
1162
  /**
1130
1163
  * Status information for an MCP server connection.
1131
1164
  */
@@ -1149,6 +1182,7 @@ export declare type McpServerStatus = {
1149
1182
  * Error message (available when status is 'failed')
1150
1183
  */
1151
1184
  error?: string;
1185
+
1152
1186
  /**
1153
1187
  * Server configuration (includes URL for HTTP/SSE servers)
1154
1188
  */
@@ -1157,6 +1191,10 @@ export declare type McpServerStatus = {
1157
1191
  * Configuration scope (e.g., project, user, local, claudeai, managed)
1158
1192
  */
1159
1193
  scope?: string;
1194
+ /**
1195
+ * Where the server definition came from: sdk (an in-process server the SDK host registered — only the host can register one), plugin (a server a plugin ships or registers at runtime), or the config scope (user, project, local, dynamic, managed, enterprise, claudeai, agent). Key trust on this, not on the name. Absent on CLIs that predate the field.
1196
+ */
1197
+ source?: string;
1160
1198
  /**
1161
1199
  * Tools provided by this server (available when connected)
1162
1200
  */
@@ -1419,6 +1457,16 @@ export declare type Options = {
1419
1457
  * Paths should be absolute.
1420
1458
  */
1421
1459
  additionalDirectories?: string[];
1460
+ /**
1461
+ * The trusted checkout `cwd` is a worktree of. Project settings (hooks,
1462
+ * permissions), `.mcp.json`, the `.claude` config trees (commands, agents,
1463
+ * skills, workflows, routines, output-styles; a routine cannot be
1464
+ * activated with it)
1465
+ * and `CLAUDE_PROJECT_DIR` come from here instead of `cwd`, so whatever
1466
+ * the branch checked out in `cwd` carries is not what the session runs.
1467
+ * Absolute path.
1468
+ */
1469
+ projectConfigRoot?: string;
1422
1470
  /**
1423
1471
  * Agent name for the main thread. When specified, the agent's system prompt,
1424
1472
  * tool restrictions, and model will be applied to the main conversation.
@@ -2320,6 +2368,7 @@ export declare type PermissionDeniedHookInput = BaseHookInput & {
2320
2368
  tool_input: unknown;
2321
2369
  tool_use_id: string;
2322
2370
  reason: string;
2371
+ mcp_server?: McpServerProvenance;
2323
2372
  };
2324
2373
 
2325
2374
  export declare type PermissionDeniedHookSpecificOutput = {
@@ -2337,6 +2386,7 @@ export declare type PermissionRequestHookInput = BaseHookInput & {
2337
2386
  tool_name: string;
2338
2387
  tool_input: unknown;
2339
2388
  permission_suggestions?: PermissionUpdate[];
2389
+ mcp_server?: McpServerProvenance;
2340
2390
  };
2341
2391
 
2342
2392
  export declare type PermissionRequestHookSpecificOutput = {
@@ -2494,6 +2544,7 @@ export declare type PostToolUseFailureHookInput = BaseHookInput & {
2494
2544
  * Tool execution time in milliseconds. Excludes permission-prompt and hook time.
2495
2545
  */
2496
2546
  duration_ms?: number;
2547
+ mcp_server?: McpServerProvenance;
2497
2548
  };
2498
2549
 
2499
2550
  export declare type PostToolUseFailureHookSpecificOutput = {
@@ -2511,6 +2562,7 @@ export declare type PostToolUseHookInput = BaseHookInput & {
2511
2562
  * Tool execution time in milliseconds. Excludes permission-prompt and hook time.
2512
2563
  */
2513
2564
  duration_ms?: number;
2565
+ mcp_server?: McpServerProvenance;
2514
2566
  };
2515
2567
 
2516
2568
  export declare type PostToolUseHookSpecificOutput = {
@@ -2588,6 +2640,7 @@ export declare type PreToolUseHookInput = BaseHookInput & {
2588
2640
  tool_name: string;
2589
2641
  tool_input: unknown;
2590
2642
  tool_use_id: string;
2643
+ mcp_server?: McpServerProvenance;
2591
2644
  };
2592
2645
 
2593
2646
  export declare type PreToolUseHookSpecificOutput = {
@@ -2656,6 +2709,7 @@ export declare interface Query extends AsyncGenerator<SDKMessage, void> {
2656
2709
  warning?: string;
2657
2710
  }>;
2658
2711
 
2712
+
2659
2713
  /**
2660
2714
  * Change the model used for subsequent responses.
2661
2715
  * Only available in streaming input mode.
@@ -3417,6 +3471,8 @@ export declare type SDKAssistantMessage = {
3417
3471
 
3418
3472
 
3419
3473
 
3474
+
3475
+
3420
3476
  };
3421
3477
 
3422
3478
  export declare type SDKAssistantMessageError = 'authentication_failed' | 'oauth_org_not_allowed' | 'account_on_hold' | 'verification_required' | 'billing_error' | 'rate_limit' | 'overloaded' | 'invalid_request' | 'model_not_found' | 'server_error' | 'unknown' | 'max_output_tokens' | 'cloud_credential_error';
@@ -4432,6 +4488,7 @@ declare type SDKControlMcpToggleRequest = {
4432
4488
  declare type SDKControlPermissionRequest = {
4433
4489
  subtype: 'can_use_tool';
4434
4490
  tool_name: string;
4491
+ mcp_server?: coreTypes.McpServerProvenance;
4435
4492
  input: Record<string, unknown>;
4436
4493
  permission_suggestions?: coreTypes.PermissionUpdate[];
4437
4494
  blocked_path?: string;
@@ -4443,6 +4500,7 @@ declare type SDKControlPermissionRequest = {
4443
4500
  * Structured discriminator for why auto-mode escalated. Lets SDK hosts make policy (e.g. auto-deny safetyCheck) without parsing decision_reason text. For compound bash commands this is "subcommandResults" even when a safetyCheck is nested inside — check classifier_approvable for that case, and see decision_reason: for this variant it carries the nested safety check's warning text.
4444
4501
  */
4445
4502
  decision_reason_type?: 'rule' | 'mode' | 'subcommandResults' | 'permissionPromptTool' | 'hook' | 'asyncAgent' | 'sandboxOverride' | 'workingDir' | 'safetyCheck' | 'classifier' | 'other';
4503
+
4446
4504
  /**
4447
4505
  * Set when a safetyCheck is present anywhere in the decision reason (including nested inside subcommandResults for compound bash). false = at least one safety check requires manual approval (e.g. Windows path bypass, dangerous rm); true = all safety checks MAY be classifier-approved (e.g. sensitive-file paths). Absent when no safetyCheck is involved.
4448
4506
  */
@@ -5149,6 +5207,7 @@ export declare type SDKPermissionDeniedMessage = {
5149
5207
  * Discriminator from PermissionDecisionReason (e.g. 'classifier', 'asyncAgent', 'mode', 'rule').
5150
5208
  */
5151
5209
  decision_reason_type?: string;
5210
+
5152
5211
  /**
5153
5212
  * Human-readable reason from the deciding component, when available.
5154
5213
  */
@@ -5317,6 +5376,10 @@ export declare type SDKResultError = {
5317
5376
  queued_turn_count?: number;
5318
5377
  errors: string[];
5319
5378
 
5379
+ /**
5380
+ * Set on the zeroed error_during_execution result a stream-json run writes before exiting on a known startup failure; errors carries the same text as stderr. Failures that used to end with stderr alone write that result only when the host sets CLAUDE_CODE_STARTUP_FAILURE_RESULTS. Absent on every other result, on startup failures without a known cause, and from older producers.
5381
+ */
5382
+ startup_failure_reason?: SDKStartupFailureReason;
5320
5383
  /**
5321
5384
  * Client uuid of the user message that triggered this turn (submitMessage options.uuid), echoed back so a consumer can link this error result to the send it answers — the same join key the success variant echoes, carried alone (error turns have no request_sent_wall_ms to report). A delivery-failure result from the remote-session client echoes the failed send's queue key, which is client-minted when the host sent no uuid of its own. A synthetic/scheduled (meta) turn's own uuid is echoed only when the host vouches it is the client event's own (delivered content such as a Slack owner ping or a Slack-bot observation); a meta turn that folded queued user messages in mid-turn, vouched or not, echoes the LAST of them. Absent on turns that neither had a client uuid nor folded a user message in, on session-scoped failures with no single triggering send (a crashed worker's zeroed result), and from older producers.
5322
5385
  */
@@ -5368,6 +5431,7 @@ export declare type SDKResultSuccess = {
5368
5431
  time_origin_ms?: number;
5369
5432
  is_error: boolean;
5370
5433
  api_error_status?: number | null;
5434
+
5371
5435
  num_turns: number;
5372
5436
  result: string;
5373
5437
  stop_reason: string | null;
@@ -5478,6 +5542,11 @@ export declare type SDKSettingsParseError = {
5478
5542
  message: string;
5479
5543
  };
5480
5544
 
5545
+ /**
5546
+ * Why Claude Code refused to start, so a host can offer the fix instead of a retry. org_pin_api_key_conflict: managed settings pin a first-party or Cloud gateway sign-in, and an Anthropic API key or auth token is configured instead. org_verify_failed: the sign-in's organization could not be verified against the pin (network, or a revoked token). org_pin_mismatch: the sign-in belongs to an organization the pin does not allow. managed_settings_invalid: managed policy settings could not be read, or the pin names no organization. remote_settings_required_unavailable: managed settings the organization requires could not be loaded. gateway_signin_required: the Cloud gateway ended this sign-in. gateway_access_denied: the Cloud gateway refused managed settings for this account. proxy_invalid: a proxy setting is not a complete URL. temp_dir_unusable: the per-user temp directory is unsafe or could not be created. cwd_unavailable: the working directory was deleted, moved or cannot be read. shell_tool_missing: Windows has no shell tool: Git Bash is missing, and PowerShell is missing or turned off by CLAUDE_CODE_USE_POWERSHELL_TOOL. session_held_by_background: the conversation to resume or continue is running as a background session. worktree_resume_refused: the resume was refused because the session's worktree failed its safety checks or the resume was launched from inside it; errors says whether a re-run continues without the worktree. worktree_unverified: the session's worktree could not be verified right now; retrying may succeed. cli_version_too_old: this Claude Code version is below the minimum Anthropic requires. bypass_root: bypass permissions mode was requested while running as root.
5547
+ */
5548
+ export declare type SDKStartupFailureReason = 'org_pin_api_key_conflict' | 'org_verify_failed' | 'org_pin_mismatch' | 'managed_settings_invalid' | 'remote_settings_required_unavailable' | 'gateway_signin_required' | 'gateway_access_denied' | 'proxy_invalid' | 'temp_dir_unusable' | 'cwd_unavailable' | 'shell_tool_missing' | 'session_held_by_background' | 'worktree_resume_refused' | 'worktree_unverified' | 'cli_version_too_old' | 'bypass_root';
5549
+
5481
5550
  export declare type SDKStatus = 'compacting' | 'requesting' | null;
5482
5551
 
5483
5552
  export declare type SDKStatusMessage = {
@@ -5511,6 +5580,10 @@ export declare type SDKSystemMessage = {
5511
5580
  mcp_servers: {
5512
5581
  name: string;
5513
5582
  status: string;
5583
+ /**
5584
+ * Where the server definition came from — same values as McpServerStatus.source (sdk | plugin | a config scope). Absent on CLIs that predate the field.
5585
+ */
5586
+ source?: string;
5514
5587
  }[];
5515
5588
  model: string;
5516
5589
  /**
@@ -6926,7 +6999,7 @@ export declare interface Settings {
6926
6999
  */
6927
7000
  sparsePaths?: string[];
6928
7001
  /**
6929
- * Skip Git LFS smudge during clone and update (sets GIT_LFS_SKIP_SMUDGE=1) so LFS pointer files stay as pointers instead of downloading their content. Use for marketplaces hosted in repos with large LFS objects.
7002
+ * Has no effect; accepted so existing settings keep working. Claude Code's own git never downloads Git LFS content: LFS-tracked files in the marketplace repository are checked out as pointer files whether or not this is set, and adding or updating the marketplace says how many were. To fetch their content, run `git lfs pull` in the marketplace's checkout under ~/.claude/plugins/marketplaces/.
6930
7003
  */
6931
7004
  skipLfs?: boolean;
6932
7005
  } | {
@@ -6948,15 +7021,23 @@ export declare interface Settings {
6948
7021
  */
6949
7022
  sparsePaths?: string[];
6950
7023
  /**
6951
- * Skip Git LFS smudge during clone and update (sets GIT_LFS_SKIP_SMUDGE=1) so LFS pointer files stay as pointers instead of downloading their content. Use for marketplaces hosted in repos with large LFS objects.
7024
+ * Has no effect; accepted so existing settings keep working. Claude Code's own git never downloads Git LFS content: LFS-tracked files in the marketplace repository are checked out as pointer files whether or not this is set, and adding or updating the marketplace says how many were. To fetch their content, run `git lfs pull` in the marketplace's checkout under ~/.claude/plugins/marketplaces/.
6952
7025
  */
6953
7026
  skipLfs?: boolean;
6954
7027
  } | {
6955
7028
  source: 'npm';
6956
7029
  /**
6957
- * NPM package containing marketplace.json
7030
+ * npm package containing marketplace.json (e.g. "\@acme/claude-marketplace"). In strictKnownMarketplaces / blockedMarketplaces an entry also governs plugins installed straight from the npm marketplace (`<package>\@npm`): an exact package name matches that package, and "\@acme/*" matches every package under the scope.
6958
7031
  */
6959
7032
  package: string;
7033
+ /**
7034
+ * Version or range to fetch (e.g. "1.4.0", "^1.4"); defaults to the latest dist-tag
7035
+ */
7036
+ version?: string;
7037
+ /**
7038
+ * Registry URL. When adding a marketplace: a one-off registry override (otherwise your npm configuration decides). In a policy entry: the origin and path prefix the package's RESOLVED tarball URL must fall under (e.g. "https://npm.example.com/api/npm/internal/").
7039
+ */
7040
+ registry?: string;
6960
7041
  } | {
6961
7042
  source: 'file';
6962
7043
  /**
@@ -7170,7 +7251,7 @@ export declare interface Settings {
7170
7251
  */
7171
7252
  sparsePaths?: string[];
7172
7253
  /**
7173
- * Skip Git LFS smudge during clone and update (sets GIT_LFS_SKIP_SMUDGE=1) so LFS pointer files stay as pointers instead of downloading their content. Use for marketplaces hosted in repos with large LFS objects.
7254
+ * Has no effect; accepted so existing settings keep working. Claude Code's own git never downloads Git LFS content: LFS-tracked files in the marketplace repository are checked out as pointer files whether or not this is set, and adding or updating the marketplace says how many were. To fetch their content, run `git lfs pull` in the marketplace's checkout under ~/.claude/plugins/marketplaces/.
7174
7255
  */
7175
7256
  skipLfs?: boolean;
7176
7257
  } | {
@@ -7192,15 +7273,23 @@ export declare interface Settings {
7192
7273
  */
7193
7274
  sparsePaths?: string[];
7194
7275
  /**
7195
- * Skip Git LFS smudge during clone and update (sets GIT_LFS_SKIP_SMUDGE=1) so LFS pointer files stay as pointers instead of downloading their content. Use for marketplaces hosted in repos with large LFS objects.
7276
+ * Has no effect; accepted so existing settings keep working. Claude Code's own git never downloads Git LFS content: LFS-tracked files in the marketplace repository are checked out as pointer files whether or not this is set, and adding or updating the marketplace says how many were. To fetch their content, run `git lfs pull` in the marketplace's checkout under ~/.claude/plugins/marketplaces/.
7196
7277
  */
7197
7278
  skipLfs?: boolean;
7198
7279
  } | {
7199
7280
  source: 'npm';
7200
7281
  /**
7201
- * NPM package containing marketplace.json
7282
+ * npm package containing marketplace.json (e.g. "\@acme/claude-marketplace"). In strictKnownMarketplaces / blockedMarketplaces an entry also governs plugins installed straight from the npm marketplace (`<package>\@npm`): an exact package name matches that package, and "\@acme/*" matches every package under the scope.
7202
7283
  */
7203
7284
  package: string;
7285
+ /**
7286
+ * Version or range to fetch (e.g. "1.4.0", "^1.4"); defaults to the latest dist-tag
7287
+ */
7288
+ version?: string;
7289
+ /**
7290
+ * Registry URL. When adding a marketplace: a one-off registry override (otherwise your npm configuration decides). In a policy entry: the origin and path prefix the package's RESOLVED tarball URL must fall under (e.g. "https://npm.example.com/api/npm/internal/").
7291
+ */
7292
+ registry?: string;
7204
7293
  } | {
7205
7294
  source: 'file';
7206
7295
  /**
@@ -7409,7 +7498,7 @@ export declare interface Settings {
7409
7498
  */
7410
7499
  sparsePaths?: string[];
7411
7500
  /**
7412
- * Skip Git LFS smudge during clone and update (sets GIT_LFS_SKIP_SMUDGE=1) so LFS pointer files stay as pointers instead of downloading their content. Use for marketplaces hosted in repos with large LFS objects.
7501
+ * Has no effect; accepted so existing settings keep working. Claude Code's own git never downloads Git LFS content: LFS-tracked files in the marketplace repository are checked out as pointer files whether or not this is set, and adding or updating the marketplace says how many were. To fetch their content, run `git lfs pull` in the marketplace's checkout under ~/.claude/plugins/marketplaces/.
7413
7502
  */
7414
7503
  skipLfs?: boolean;
7415
7504
  } | {
@@ -7431,15 +7520,23 @@ export declare interface Settings {
7431
7520
  */
7432
7521
  sparsePaths?: string[];
7433
7522
  /**
7434
- * Skip Git LFS smudge during clone and update (sets GIT_LFS_SKIP_SMUDGE=1) so LFS pointer files stay as pointers instead of downloading their content. Use for marketplaces hosted in repos with large LFS objects.
7523
+ * Has no effect; accepted so existing settings keep working. Claude Code's own git never downloads Git LFS content: LFS-tracked files in the marketplace repository are checked out as pointer files whether or not this is set, and adding or updating the marketplace says how many were. To fetch their content, run `git lfs pull` in the marketplace's checkout under ~/.claude/plugins/marketplaces/.
7435
7524
  */
7436
7525
  skipLfs?: boolean;
7437
7526
  } | {
7438
7527
  source: 'npm';
7439
7528
  /**
7440
- * NPM package containing marketplace.json
7529
+ * npm package containing marketplace.json (e.g. "\@acme/claude-marketplace"). In strictKnownMarketplaces / blockedMarketplaces an entry also governs plugins installed straight from the npm marketplace (`<package>\@npm`): an exact package name matches that package, and "\@acme/*" matches every package under the scope.
7441
7530
  */
7442
7531
  package: string;
7532
+ /**
7533
+ * Version or range to fetch (e.g. "1.4.0", "^1.4"); defaults to the latest dist-tag
7534
+ */
7535
+ version?: string;
7536
+ /**
7537
+ * Registry URL. When adding a marketplace: a one-off registry override (otherwise your npm configuration decides). In a policy entry: the origin and path prefix the package's RESOLVED tarball URL must fall under (e.g. "https://npm.example.com/api/npm/internal/").
7538
+ */
7539
+ registry?: string;
7443
7540
  } | {
7444
7541
  source: 'file';
7445
7542
  /**
@@ -7638,7 +7735,7 @@ export declare interface Settings {
7638
7735
  */
7639
7736
  sparsePaths?: string[];
7640
7737
  /**
7641
- * Skip Git LFS smudge during clone and update (sets GIT_LFS_SKIP_SMUDGE=1) so LFS pointer files stay as pointers instead of downloading their content. Use for marketplaces hosted in repos with large LFS objects.
7738
+ * Has no effect; accepted so existing settings keep working. Claude Code's own git never downloads Git LFS content: LFS-tracked files in the marketplace repository are checked out as pointer files whether or not this is set, and adding or updating the marketplace says how many were. To fetch their content, run `git lfs pull` in the marketplace's checkout under ~/.claude/plugins/marketplaces/.
7642
7739
  */
7643
7740
  skipLfs?: boolean;
7644
7741
  } | {
@@ -7660,15 +7757,23 @@ export declare interface Settings {
7660
7757
  */
7661
7758
  sparsePaths?: string[];
7662
7759
  /**
7663
- * Skip Git LFS smudge during clone and update (sets GIT_LFS_SKIP_SMUDGE=1) so LFS pointer files stay as pointers instead of downloading their content. Use for marketplaces hosted in repos with large LFS objects.
7760
+ * Has no effect; accepted so existing settings keep working. Claude Code's own git never downloads Git LFS content: LFS-tracked files in the marketplace repository are checked out as pointer files whether or not this is set, and adding or updating the marketplace says how many were. To fetch their content, run `git lfs pull` in the marketplace's checkout under ~/.claude/plugins/marketplaces/.
7664
7761
  */
7665
7762
  skipLfs?: boolean;
7666
7763
  } | {
7667
7764
  source: 'npm';
7668
7765
  /**
7669
- * NPM package containing marketplace.json
7766
+ * npm package containing marketplace.json (e.g. "\@acme/claude-marketplace"). In strictKnownMarketplaces / blockedMarketplaces an entry also governs plugins installed straight from the npm marketplace (`<package>\@npm`): an exact package name matches that package, and "\@acme/*" matches every package under the scope.
7670
7767
  */
7671
7768
  package: string;
7769
+ /**
7770
+ * Version or range to fetch (e.g. "1.4.0", "^1.4"); defaults to the latest dist-tag
7771
+ */
7772
+ version?: string;
7773
+ /**
7774
+ * Registry URL. When adding a marketplace: a one-off registry override (otherwise your npm configuration decides). In a policy entry: the origin and path prefix the package's RESOLVED tarball URL must fall under (e.g. "https://npm.example.com/api/npm/internal/").
7775
+ */
7776
+ registry?: string;
7672
7777
  } | {
7673
7778
  source: 'file';
7674
7779
  /**
@@ -7867,7 +7972,7 @@ export declare interface Settings {
7867
7972
  */
7868
7973
  sparsePaths?: string[];
7869
7974
  /**
7870
- * Skip Git LFS smudge during clone and update (sets GIT_LFS_SKIP_SMUDGE=1) so LFS pointer files stay as pointers instead of downloading their content. Use for marketplaces hosted in repos with large LFS objects.
7975
+ * Has no effect; accepted so existing settings keep working. Claude Code's own git never downloads Git LFS content: LFS-tracked files in the marketplace repository are checked out as pointer files whether or not this is set, and adding or updating the marketplace says how many were. To fetch their content, run `git lfs pull` in the marketplace's checkout under ~/.claude/plugins/marketplaces/.
7871
7976
  */
7872
7977
  skipLfs?: boolean;
7873
7978
  } | {
@@ -7889,15 +7994,23 @@ export declare interface Settings {
7889
7994
  */
7890
7995
  sparsePaths?: string[];
7891
7996
  /**
7892
- * Skip Git LFS smudge during clone and update (sets GIT_LFS_SKIP_SMUDGE=1) so LFS pointer files stay as pointers instead of downloading their content. Use for marketplaces hosted in repos with large LFS objects.
7997
+ * Has no effect; accepted so existing settings keep working. Claude Code's own git never downloads Git LFS content: LFS-tracked files in the marketplace repository are checked out as pointer files whether or not this is set, and adding or updating the marketplace says how many were. To fetch their content, run `git lfs pull` in the marketplace's checkout under ~/.claude/plugins/marketplaces/.
7893
7998
  */
7894
7999
  skipLfs?: boolean;
7895
8000
  } | {
7896
8001
  source: 'npm';
7897
8002
  /**
7898
- * NPM package containing marketplace.json
8003
+ * npm package containing marketplace.json (e.g. "\@acme/claude-marketplace"). In strictKnownMarketplaces / blockedMarketplaces an entry also governs plugins installed straight from the npm marketplace (`<package>\@npm`): an exact package name matches that package, and "\@acme/*" matches every package under the scope.
7899
8004
  */
7900
8005
  package: string;
8006
+ /**
8007
+ * Version or range to fetch (e.g. "1.4.0", "^1.4"); defaults to the latest dist-tag
8008
+ */
8009
+ version?: string;
8010
+ /**
8011
+ * Registry URL. When adding a marketplace: a one-off registry override (otherwise your npm configuration decides). In a policy entry: the origin and path prefix the package's RESOLVED tarball URL must fall under (e.g. "https://npm.example.com/api/npm/internal/").
8012
+ */
8013
+ registry?: string;
7901
8014
  } | {
7902
8015
  source: 'file';
7903
8016
  /**
@@ -9005,10 +9118,11 @@ export declare type SyncHookJSONOutput = {
9005
9118
  /**
9006
9119
  * Marker string that splits a custom `systemPrompt` into a static prefix
9007
9120
  * (eligible for cross-session prompt caching) and a dynamic suffix
9008
- * (session-specific, not globally cached). Include this literal as a
9009
- * standalone element of a `string[]` `systemPrompt` to opt in; blocks
9010
- * before it get global cache scope, blocks after do not. See
9011
- * `splitSysPromptPrefix` in `src/utils/api.ts`.
9121
+ * (session-specific, not globally cached). Include it as a standalone
9122
+ * element of a `string[]` `systemPrompt`, or as a line of its own in a
9123
+ * `--system-prompt` string, to opt in; content before it gets global
9124
+ * cache scope, content after does not. See `splitSysPromptPrefix` in
9125
+ * `src/utils/api.ts`.
9012
9126
  */
9013
9127
  export declare const SYSTEM_PROMPT_DYNAMIC_BOUNDARY = "__SYSTEM_PROMPT_DYNAMIC_BOUNDARY__";
9014
9128