pi-ghost-autocomplete 0.8.1 → 0.9.1

package/dist/providers/cloud-provider.d.ts

@@ -2,12 +2,56 @@
  * SPDX-License-Identifier: SSPL-1.0
  * SPDX-FileCopyrightText: 2025 Alessandro Pungitore <alessandro@pungitore.ch>
  */
+import type { Api, Model, Models, ProviderEnv, ProviderHeaders } from "@earendil-works/pi-ai";
+import type { ModelRegistry } from "@earendil-works/pi-coding-agent";
 import type { CloudProviderConfig } from "../config.js";
 import type { GhostProvider, GhostRequest, StreamDelta } from "./types.js";
+/**
+ * Resolved auth forwarded into a cloud request. All three fields are
+ * per-call options on pi-ai's stream/complete (`ProviderRequestOptions`).
+ * `baseUrl` is intentionally absent — it is a property of the static
+ * `Provider`, not a per-call option, so `builtinModels()` always uses the
+ * provider's default endpoint (see {@link resolveAuth}).
+ */
+export interface ResolvedGhostAuth {
+    apiKey?: string;
+    headers?: ProviderHeaders;
+    env?: ProviderEnv;
+}
+/**
+ * Resolve auth for a cloud request. Precedence:
+ *  1. `config.apiKey` (explicit `PI_GHOST_API_KEY`) — wins whenever set.
+ *  2. The session's real registry (`ctx.modelRegistry.getApiKeyAndHeaders`)
+ *     — reflects the user's models.json config and stored credentials exactly
+ *     as the main agent sees them, so a provider already configured for the
+ *     session (e.g. Groq) is reused without a separate ghost key. We forward
+ *     the resolved `headers` and `env` too (OAuth bearer headers, regional /
+ *     endpoint env), not just the api-key string. HOWEVER: a custom `baseUrl`
+ *     cannot be honored here — `builtinModels()` ignores models.json URLs and
+ *     `baseUrl` is not a per-call option — so when the registry resolved a
+ *     custom `baseUrl` we skip it entirely and fall back to ambient auth, to
+ *     avoid sending a custom-endpoint key to the default endpoint.
+ *  3. The builtin registry's ambient auth (`Models.getAuth`) — env keys like
+ *     `GROQ_API_KEY`. Kept for the bench/replay paths that run without a live
+ *     session registry.
+ *
+ * Safe by construction: the registry branch only adopts auth when it carries
+ * no custom `baseUrl`, so it can never send credentials to the wrong endpoint.
+ * Worst case it falls through to the original ambient path.
+ */
+export declare function resolveAuth(models: Models, config: CloudProviderConfig, model: Model<Api>, registry?: ModelRegistry): Promise<ResolvedGhostAuth>;
 export declare class CloudProvider implements GhostProvider {
     private readonly config;
+    private readonly registry?;
     readonly name = "ghost-cloud";
-    constructor(config: CloudProviderConfig);
+    /**
+     * @param registry The session's real model registry, used to resolve the
+     * provider API key from the user's actual configuration (models.json,
+     * stored credentials, env) so ghost can reuse the same key the main agent
+     * uses — without requiring a separate `PI_GHOST_API_KEY`. Optional for
+     * tests and the non-session bench/replay paths.
+     */
+    constructor(config: CloudProviderConfig, registry?: ModelRegistry | undefined);
     get debounceMs(): number;
     predict(req: GhostRequest): Promise<string | null>;
     /**