@mars-sea/dsh-commandcode-provider 0.13.4 → 0.14.1

package/lib/index.d.ts

@@ -61,35 +61,13 @@ type CommandCodeProtocol = 'cli' | 'openai' | 'messages';
 declare const DEFAULT_MAX_OUTPUT_TOKENS = 131072;
 //#endregion
 //#region src/adapter.d.ts
-declare const COMMAND_CODE_CLI_VERSION = "1.82.5";
+declare const COMMAND_CODE_CLI_VERSION = "1.84.0";
 declare const DEFAULT_API_BASE = "https://api.commandcode.ai";
 /**
  * The output budget this bundle asks for, and the ceiling it will never exceed.
- *
- * 131 072, chosen against a measured provider limit rather than a round guess.
- * Probing `/alpha/generate` directly on 2026-09-28: 64 000 → 200, 131 072 → 200,
- * 196 608 → 200, **200 000 → 200, 200 704 → 400**, 1 000 000 → 400. The server
- * therefore caps `max_tokens` at 200 000, and it does so identically for a
- * 262 144-window model (`stealth/pixel-canary`, retired by Command Code on
- * 2026-10-01 and named here only as the probe's subject) and a 1 000 000-window
- * one (`stealth/space-bunny-alpha`) — the cap is global, not per model. 131 072
- * keeps a 35 % margin under it while covering the real output ceiling of the
- * models that have one (Claude 64 K, Gemini 64 K, several at 128 K).
- *
- * The old 64 000 was never a provider requirement: it cost nothing in latency
- * (a 64 000 request answered headers in 1.28 s against 1.57 s for 131 072) but
- * it did cap what a model could ever say in one turn.
- *
- * No client-side clamp is applied on top of this: an earlier version pre-shrank
- * `max_tokens` from an estimate of the prompt already sent (`requestContextBudget()`,
- * issue #67), but that estimate over-corrected on ordinary long conversations —
- * exactly the "output gets cut short as the conversation grows" symptom issue #74
- * reported — while a live A/B probe (2026-09-30, `stealth/space-bunny-alpha`,
- * ~19.6% over its 1,000,000-token window with no client-side shrink) showed the
- * endpoint answers a genuine overflow with an unambiguous `400 … exceeds the
- * model's context window`, which `isContextOverflowDetail()` below already
- * classifies as `CONTEXT_WINDOW_EXCEEDED` independently of this constant. See
- * [决策记录](../docs/决策记录.md).
+ * The figure and its probe evidence live in `./output-budget.ts` — the module
+ * the browser settings page also bounds its input by — and are re-exported here
+ * under the historical name so existing importers are unaffected.
  */
 declare const DEFAULT_GENERATE_MAX_TOKENS = 131072;
 /** How long the picker's plan-filter billing facts stay cached before refetching. */
@@ -196,6 +174,14 @@ interface CommandCodeConnectionOptions {
    * 非法条目在 `resolveAdapterOptions` 已被清洗，这里只读已判定的值。
    */
   contextWindowOverrides?: Readonly<Record<string, number>> | undefined;
+  /**
+   * 输出预算上限（issue #74）。未设置＝沿用既有推导（模型公布/学习上限、
+   * 网关总上限）。正整数＝用户上限，与推导值取较小者，永远不会超过网关总上限。
+   * `0`＝不发送 `max_tokens`，把单轮输出规模交回平台——仅 CLI 与 OpenAI 传输
+   * 支持；Messages 端点必填该字段，因此那条链路仍按推导值发送（见
+   * `omitOutputTokens()`）。
+   */
+  maxOutputTokens?: number | undefined;
   /**
    * Optional protocol hint. `'auto'` (default) uses billing/cache plus
    * Provider API fallback; `'cli'` forces `/alpha/generate`; `'openai'`
@@ -967,11 +953,28 @@ interface EnrollmentInput {
   key?: string;
 }
 type EnrollmentPhase = 'creating' | 'waiting' | 'writing' | 'naming' | 'finished' | 'cancelling' | 'cancelled' | 'failed' | 'cleanup-needed';
+/**
+ * 账号开通状态的语义消息键。
+ *
+ * 状态消息传键而不是成品文案：界面语言由浏览器侧持有，宿主没有立场去猜；同一条状态
+ * 要在中文与英文界面下各自显示，而 `phase` 不足以唯一确定它——`naming` 既有「正在
+ * 保存名称」也有「名称保存失败」，`cleanup-needed` 既有「收尾未完成」也有「清理未
+ * 完成」，`cancelled` 既有「已取消」也有「已取消并清理」。客户端拿这些键走 `t()`
+ * 渲染，不必再匹配自由文本；`SettingsCommandCodeKey` 收录本类型，因此新增键漏写
+ * 中文或英文字典都会被类型检查拦下。
+ *
+ * 其中十五条由宿主产出（`src/enrollment.ts`），`enrollmentCleanupPending` 也在此列——
+ * 它在「收尾未完成」时由宿主与页面两侧共用同一个键；另外七条是浏览器侧控制器的专属键
+ * （`src/client/enrollment.ts`），只在传输失败或连接断开时由该侧自己产出。宿主抛出的
+ * 异常消息不在此列：它们不上屏，客户端在所有失败路径都用自己这一侧的文案覆盖。
+ */
+type EnrollmentMessageKey = 'enrollmentCreating' | 'enrollmentWaiting' | 'enrollmentWriting' | 'enrollmentNaming' | 'enrollmentNameFailed' | 'enrollmentFinished' | 'enrollmentCancelling' | 'enrollmentCancelled' | 'enrollmentCancelledCleaned' | 'enrollmentFailed' | 'enrollmentFailedCleaned' | 'enrollmentCleanupPending' | 'enrollmentCleanupFailed' | 'enrollmentRecordNaming' | 'enrollmentRecordCleanup' | 'enrollmentBeginFailed' | 'enrollmentCancelUnconfirmed' | 'enrollmentNameRequestFailed' | 'enrollmentCleanupRequestFailed' | 'enrollmentDisconnected' | 'enrollmentHostUnavailable' | 'enrollmentStatusUnavailable';
 interface EnrollmentState {
   id: string;
   ref: string;
   phase: EnrollmentPhase;
-  message: string;
+  /** 要显示的语义键；文案由浏览器侧按界面语言渲染，见 {@link EnrollmentMessageKey}。 */
+  messageKey: EnrollmentMessageKey;
   authUrl?: string;
   suggestedName?: string;
 }
@@ -1070,9 +1073,13 @@ declare const KNOWN_IMAGE_MODELS: ReadonlySet<string>;
  * what the current CLI says.
  *
  * 1.82.4 then reversed 1.74.1's removal of `meituan/LongCat-2.0:free` and added
- * the `stealth/cat-jam:free` preview, taking this set to 24 members — the size
- * of the live catalog's `zdr:false` list. The canonical helper set still carries
- * 23 because `cat-jam:free` postdates the artifact's embedded snapshot.
+ * the `stealth/cat-jam:free` preview, taking this set to 24 members. The 1.84.0
+ * sync (2026-10-16) moves it to 25 with no verdict flip: LongCat's exclusion
+ * followed its rename to the paid id, and the free `reflection/beam:free`
+ * preview joined on catalog evidence alone. The authoritative membership is the
+ * UNION of the artifact's exclusion set and the catalog's `zdr:false` list —
+ * neither source alone is complete, which is why this set is not simply "what
+ * the CLI says".
  */
 declare const KNOWN_NON_ZDR_MODELS: ReadonlySet<string>;
 /**
@@ -1937,47 +1944,132 @@ declare const COMMANDCODE_SEARCH_PROVIDER_ID = "commandcode";
  */
 declare const DEFAULT_WEB_SEARCH_PROVIDER_ID = "deepseek-official";
 /**
- * Tracked web-search selection state for one mounted `WebRuntime`.
+ * Profile entry id whose volatile `searchProvider` selects the search backend.
+ *
+ * The hosting profile declares it in `dsh-base`'s cordis patch as
+ * `- id: web` / `name: '@deepseek-ai/dsh-web'`, and the shipped web-search
+ * settings page addresses the very same namespace — that page and this plugin
+ * are therefore two writers of ONE field (see
+ * {@link createCommandCodeSearchSelection} for how they avoid fighting).
+ */
+declare const WEB_SELECTION_NAMESPACE = "web";
+/**
+ * Structural view of the host settings service.
+ *
+ * Spelled structurally rather than imported: only these three members are used,
+ * and a narrower contract keeps the tests' double honest. Every member is
+ * called inside a `try`, because a host mounted without `configEditor` /
+ * `profileContext` throws from `describe()` rather than answering empty.
+ */
+interface WebSelectionSettings {
+  /** Every configurable entry's form view; the `web` row is absent when it has no volatile field. */
+  describe(): unknown;
+  /** Merge fields into that entry's live config (the official volatile write). */
+  update(ns: string, patch: object): Promise<void>;
+  /** Reset the entry's live fields, then set the supplied ones. */
+  replace(ns: string, section: object): Promise<void>;
+}
+/** Failure and visibility sink; implementations must never throw. */
+interface WebSelectionLogger {
+  warn(message: string): void;
+  info(message: string): void;
+}
+/**
+ * Tracked web-search selection state.
+ *
+ * `owner` is true while this plugin is the one asserting the selection: it
+ * wrote the value, or found it already equal to ours AND attributed it to a
+ * user-layer pin. Disabling only ever gives back what `owner` covers.
+ *
+ * `preexisting` marks the one case where the value is NOT ours to give back:
+ * the field already read `commandcode` while the USER LAYER held nothing, so
+ * the value came from the deployment's composed config or
+ * `$DSH_WEB_SEARCH_PROVIDER`. Restoring there would write over a pin this
+ * plugin never took.
  *
- * `owner` marks whether this plugin currently owns the selection. `displaced`
- * is the backend it took over — restored on disable or unload — and
- * `undefined` means "nothing was configured, leave auto-select" and must
- * round-trip untouched.
+ * `foreign` is a non-`commandcode` pin found in the user layer — the shipped
+ * web-search settings page writes `deepseek-search-api`, and any sibling plugin
+ * may pin its own id. A foreign pin is never displaced; `foreign` keeps the
+ * value so the state (and the log line) can name who owns the backend.
  *
- * `preexisting` is the one fact `displaced` cannot carry: an `undefined`
- * `displaced` means EITHER "the field was unset when we took over" (give
- * `undefined` back) OR "the field already read `commandcode`" (touch
- * nothing). Collapsing the two is what turned a user's own
- * `searchProvider: commandcode` pin into an auto-select, and then into
- * `WEB_PROVIDER_AMBIGUOUS` on every search.
+ * `displaced` is the config value at takeover time. It is what the DEGRADED
+ * (memory-only) restore writes back; the persisted path restores the composed
+ * base instead, because a copy of it in the user layer would outlive a later
+ * deployment change.
  */
 interface CommandCodeSearchSelection {
   owner: boolean;
-  displaced: string | undefined;
-  /** Whether the field already read `commandcode` when this plugin first took it over. */
   preexisting: boolean;
+  foreign: string | undefined;
+  displaced: string | undefined;
 }
 /** Fresh selection state: the plugin starts out not owning the selection. */
 declare function commandCodeSearchSelection(): CommandCodeSearchSelection;
+/** Dependencies {@link createCommandCodeSearchSelection} resolves per call. */
+interface WebSearchSelectionDeps {
+  /** The running `web` service whose selection field backs the degraded write. */
+  web: WebRuntime;
+  /** Host settings service, resolved per use because it may activate after `web`. */
+  settings: () => WebSelectionSettings | undefined;
+  /** Failure and visibility sink. */
+  logger: WebSelectionLogger;
+}
+/** The handle `src/index.ts` drives; every member is synchronous and non-throwing. */
+interface WebSearchSelectionHandle {
+  /** Live state, for callers that surface who currently owns the backend. */
+  readonly state: CommandCodeSearchSelection;
+  /** Align the selection with one end of the `webSearch` toggle. Never throws. */
+  apply(enable: boolean): void;
+  /** Resolve once every queued write has settled. */
+  settled(): Promise<void>;
+  /** Fiber release: drop queued writes and restore in memory ONLY — never on disk. */
+  release(): void;
+}
 /**
- * Reach one end of the `webSearch` toggle without trampling sibling search
- * providers (issue #26).
+ * The selection seam over `ctx.web`.
  *
- * - Enabling writes `commandcode` and remembers whatever it displaced. When
- *   the plugin already owns the selection, the original `displaced` is kept —
- *   the field currently holds our own id, which must never be mistaken for the
- *   user's backend.
- * - Disabling hands the selection back to the remembered backend only when
- *   this plugin actually took it over. A fresh boot straight into
- *   `webSearch: false`, or a `preexisting` field, leaves it ALONE: writing the
- *   empty memory back would clear the user's own `searchProvider: commandcode`
- *   pin and hand the selection to dsh-web's auto-select, where a second usable
- *   provider makes every later search throw `WEB_PROVIDER_AMBIGUOUS`.
+ * ## Why settings rather than the runtime instance
  *
- * Never throws: like the low-level rewrite, a hardened runtime shape degrades
- * to registered-but-unselected.
+ * 0.2.1-rc.2's `WebRuntime` reads `this.config.searchProvider.get()` on EVERY
+ * search and fetch, and the loader commits a settings write into that same
+ * reference in place (`Entry._commitVolatile`) without remounting the entry.
+ * Writing the reference directly therefore works, but leaves the value out of
+ * the profile: the next commit for that entry — including one caused by an
+ * unrelated field such as `fetchProvider` — re-resolves the raw config and
+ * overwrites it. `ctx.settings.update()` / `replace()` is the documented path
+ * and the one the shipped web-search settings page uses, so this plugin takes
+ * it first and falls back to the reference only when settings is unavailable or
+ * refuses (see `volatileWrite`).
+ *
+ * ## Two engine shapes
+ *
+ * Everything above describes an rc.2+ runtime, where the selection is a
+ * reference. PRE-rc.2 engines (0.2.0-rc.2 and the 0.2.1 alphas) have neither
+ * that reference nor a settings row for `web`: there the selection is the
+ * private instance field `searchProviderId`, memory-only by nature. Those
+ * engines therefore run the degraded path BY CONSTRUCTION — no profile write
+ * exists for it and the user layer is unreadable, so a foreign pin cannot be
+ * seen and the takeover/restore semantics are the ones this plugin shipped
+ * before rc.2: remember the displaced backend, hand back only what we took. The
+ * shape is resolved per observation, so one build serves both.
+ *
+ * ## Two writers, one field
+ *
+ * The shipped web-search settings page writes `web.searchProvider` too
+ * (`deepseek-search-api` / `deepseek-official`). This seam never displaces a
+ * pin it did not write: a non-`commandcode` value in the USER LAYER stops the
+ * takeover, the value is recorded on {@link CommandCodeSearchSelection.foreign}
+ * and named in one `info` line, and the provider stays registered but
+ * unselected. A value the user layer does not carry is the deployment's own
+ * default, and taking it over is the toggle's whole purpose. A user-layer
+ * `commandcode` is treated as ours: nothing else writes that id, so it can only
+ * be a previous run of this plugin or a deliberate manual pin, and turning the
+ * toggle off restores the composed default in both cases.
+ *
+ * @param deps - the running `web` service, a settings resolver, and a log sink.
+ * @returns a synchronous handle; failures are logged, never thrown.
  */
-declare function applyCommandCodeSearchSelection(web: WebRuntime, state: CommandCodeSearchSelection, enable: boolean): void;
+declare function createCommandCodeSearchSelection(deps: WebSearchSelectionDeps): WebSearchSelectionHandle;
 /** Per-request facts the provider needs, all injected so the class stays cordis-free and testable. */
 interface CommandCodeSearchProviderDeps {
   /** 使用搜索已捕获的网关解析账号，探测不能在等待后转到另一个网关。 */
@@ -2185,7 +2277,7 @@ interface Config {
   workingDir?: string;
   /** Model catalog cache path; defaults to `~/.commandcode/models-cache.json`. */
   modelsCachePath?: string;
-  /** Milliseconds to wait for the generate response's first byte; defaults to 60s. */
+  /** Milliseconds to wait for the generate response's first byte; defaults to 300s. */
   requestTimeoutMs?: number;
   /** Milliseconds a stream may stall before being treated as a dead connection; defaults to 300s. */
   streamIdleTimeoutMs?: number;
@@ -2239,6 +2331,17 @@ interface Config {
    * 调用还会丢弃无效条目，按全局值、目录值的顺序回落。
    */
   contextWindowOverrides?: Record<string, number>;
+  /**
+   * 单轮输出预算上限（issue #74）。不填（默认）＝沿用既有推导：模型公布或
+   * 运行时学到的输出上限、以及网关总上限（131 072）三者取最小。填正整数＝
+   * 再与推导值取最小，永远不会突破三者；越界值由配置校验拒绝。
+   * 填 `0`＝**不发送** `max_tokens` 字段，把单轮输出规模交回平台自行限制——
+   * 这是报告者要的「不再被硬切」，但仅 CLI（`/alpha/generate`）与 OpenAI
+   * （`/provider/v1/chat/completions`）两条传输支持：Anthropic Messages 端点
+   * 必填该字段，缺失会被上游拒绝，因此 Claude 链路仍按推导值发送。
+   * 宿主显式传入的每次调用预算（如会话标题的 64）优先于此设置。
+   */
+  maxOutputTokens?: number;
   /**
    * Extra accounts for multi-account rotation. The top-level
    * `apiKey`/`apiKeyEnv` (plus the CLI auth file) always form the first
@@ -2266,12 +2369,16 @@ interface Config {
   /**
    * Whether to use Command Code as the backend for dsh's model-facing
    * `web_search` tool. Enabled registers a `commandcode` search provider on
-   * `ctx.web` AND selects it over the shipped `deepseek-official` (or a
-   * sibling plugin's pin), reusing the SAME key and apiBase as chat. Disabling
-   * hands the selection back to whichever backend was there before, so a
-   * sibling search plugin (e.g. modsearch) keeps working (issue #26). The
-   * write rides dsh's internal `searchProviderId`, read per search call, so a
-   * setting change lands on the next search without a restart. Defaults true.
+   * `ctx.web` AND selects it over the shipped `deepseek-official` (or a sibling
+   * plugin's pin), reusing the SAME key and apiBase as chat. Selection is the
+   * `web` profile entry's volatile `searchProvider`, written through the host
+   * settings service and read by `WebRuntime.search()` on the next call, so a
+   * toggle change lands without a restart or a remount. Disabling gives the
+   * field back to the deployment's composed value, so a sibling search plugin
+   * (e.g. modsearch) keeps working (issue #26) — EXCEPT when the user layer
+   * already carries someone else's explicit pin (the shipped web-search
+   * settings page writes `deepseek-search-api`): that choice is never
+   * displaced, and the provider stays registered but unselected. Defaults true.
    */
   webSearch?: boolean;
   /**
@@ -2331,5 +2438,5 @@ interface ResolvedCommandCodeOptions extends CommandCodeConnectionOptions {
 declare function resolveAdapterOptions(config: Config): ResolvedCommandCodeOptions;
 declare function apply(ctx: Context, config: Config): void;
 //#endregion
-export { ACTIVE_ACCOUNT_AUTO, type ApiKeyValidation, BILLING_ACCESS_TTL_MS, COMMANDCODE_SEARCH_PROVIDER_ID, COMMAND_CODE_CLI_VERSION, type CommandCodeAccountConfig, CommandCodeAccountPool, type CommandCodeAccountSlot, type CommandCodeAccountState, type CommandCodeAccountUsage, type CommandCodeAccountsReport, CommandCodeAdapter, type CommandCodeAdapterDeps, type CommandCodeBillingAccess, type CommandCodeCommandDeps, type CommandCodeConnectionOptions, type CommandCodeLoginCredentials, type CommandCodeLoginFailureReason, CommandCodeLoginFlow, type CommandCodeLoginFlowDeps, type CommandCodeLoginStatus, type CommandCodeModelAccountRule, CommandCodeSearchProvider, type CommandCodeSearchProviderDeps, type CommandCodeSearchSelection, type CommandCodeTuiSettingsDeps, type CommandCodeUsageDeps, type CommandCodeUsageReport, CommandCodeUsageService, Config, DEFAULT_API_BASE, DEFAULT_GENERATE_MAX_TOKENS, DEFAULT_MAX_OUTPUT_TOKENS, DEFAULT_MODELS_CACHE_PATH, DEFAULT_REQUEST_TIMEOUT_MS, DEFAULT_STREAM_IDLE_TIMEOUT_MS, DEFAULT_WEB_SEARCH_PROVIDER_ID, KNOWN_DEALS, KNOWN_EFFORTS, KNOWN_IMAGE_MODELS, KNOWN_NON_ZDR_MODELS, KNOWN_PEAK_PRICING, KNOWN_PLANS, KNOWN_SUBSCRIPTION_PLANS, KNOWN_THINKING_MODELS, LANG_AUTO, LOGIN_ALLOWED_ORIGINS, LOGIN_BEGIN_ENDPOINT, LOGIN_BODY_LIMIT_BYTES, LOGIN_CANCEL_ENDPOINT, LOGIN_MAX_PORT_ATTEMPTS, LOGIN_START_PORT, LOGIN_STATUS_ENDPOINT, LOGIN_TIMEOUT_MS, type LoginFlowFacade, PLAN_LABELS, PLAN_ORDER, PROVIDER, type ResolveAttachments, ResolvedCommandCodeOptions, type TuiSettingsField, type TuiSettingsFieldOption, type TuiSettingsFieldWrite, type TuiSettingsGroup, type TuiSettingsSection, type TuiSettingsSectionsService, USAGE_REPORT_ENDPOINT, accountUsable, apply, applyCommandCodeSearchSelection, applyCommandCodeTuiSettings, applyCommands, applyUsageRemote, buildCommandAuthUrl, buildCommandCodeTuiSection, capabilityDescription, commandCodeSearchSelection, commandDefinition, compareByPlan, dealLabel, formatContext, inject, loginStatusSchema, matchModelRule, modelVisibleInPlan, name, parseLoginStatus, peakPricingLabel, peakPricingState, planLabel, projectSlugFromPath, resolveAdapterOptions, resolveAuthFileApiKey, selectAccountForModel, selectActiveAccount, studioBaseForApiBase, subscriptionPlanInfo, supportsZeroDataRetention, usageReportSchema, validateCommandApiKey };
+export { ACTIVE_ACCOUNT_AUTO, type ApiKeyValidation, BILLING_ACCESS_TTL_MS, COMMANDCODE_SEARCH_PROVIDER_ID, COMMAND_CODE_CLI_VERSION, type CommandCodeAccountConfig, CommandCodeAccountPool, type CommandCodeAccountSlot, type CommandCodeAccountState, type CommandCodeAccountUsage, type CommandCodeAccountsReport, CommandCodeAdapter, type CommandCodeAdapterDeps, type CommandCodeBillingAccess, type CommandCodeCommandDeps, type CommandCodeConnectionOptions, type CommandCodeLoginCredentials, type CommandCodeLoginFailureReason, CommandCodeLoginFlow, type CommandCodeLoginFlowDeps, type CommandCodeLoginStatus, type CommandCodeModelAccountRule, CommandCodeSearchProvider, type CommandCodeSearchProviderDeps, type CommandCodeSearchSelection, type CommandCodeTuiSettingsDeps, type CommandCodeUsageDeps, type CommandCodeUsageReport, CommandCodeUsageService, Config, DEFAULT_API_BASE, DEFAULT_GENERATE_MAX_TOKENS, DEFAULT_MAX_OUTPUT_TOKENS, DEFAULT_MODELS_CACHE_PATH, DEFAULT_REQUEST_TIMEOUT_MS, DEFAULT_STREAM_IDLE_TIMEOUT_MS, DEFAULT_WEB_SEARCH_PROVIDER_ID, KNOWN_DEALS, KNOWN_EFFORTS, KNOWN_IMAGE_MODELS, KNOWN_NON_ZDR_MODELS, KNOWN_PEAK_PRICING, KNOWN_PLANS, KNOWN_SUBSCRIPTION_PLANS, KNOWN_THINKING_MODELS, LANG_AUTO, LOGIN_ALLOWED_ORIGINS, LOGIN_BEGIN_ENDPOINT, LOGIN_BODY_LIMIT_BYTES, LOGIN_CANCEL_ENDPOINT, LOGIN_MAX_PORT_ATTEMPTS, LOGIN_START_PORT, LOGIN_STATUS_ENDPOINT, LOGIN_TIMEOUT_MS, type LoginFlowFacade, PLAN_LABELS, PLAN_ORDER, PROVIDER, type ResolveAttachments, ResolvedCommandCodeOptions, type TuiSettingsField, type TuiSettingsFieldOption, type TuiSettingsFieldWrite, type TuiSettingsGroup, type TuiSettingsSection, type TuiSettingsSectionsService, USAGE_REPORT_ENDPOINT, WEB_SELECTION_NAMESPACE, type WebSearchSelectionHandle, type WebSelectionLogger, type WebSelectionSettings, accountUsable, apply, applyCommandCodeTuiSettings, applyCommands, applyUsageRemote, buildCommandAuthUrl, buildCommandCodeTuiSection, capabilityDescription, commandCodeSearchSelection, commandDefinition, compareByPlan, createCommandCodeSearchSelection, dealLabel, formatContext, inject, loginStatusSchema, matchModelRule, modelVisibleInPlan, name, parseLoginStatus, peakPricingLabel, peakPricingState, planLabel, projectSlugFromPath, resolveAdapterOptions, resolveAuthFileApiKey, selectAccountForModel, selectActiveAccount, studioBaseForApiBase, subscriptionPlanInfo, supportsZeroDataRetention, usageReportSchema, validateCommandApiKey };
 //# sourceMappingURL=index.d.ts.map