@evandu/super-pi 0.1.104 → 0.1.105

package/dist/server/server-context.d.ts

@@ -7,6 +7,7 @@ import type { ConversationService } from "./application/conversation-service.js"
 import type { RunService } from "./application/run-service.js";
 import type { ExtensionUiService } from "./application/extension-ui-service.js";
 import type { CatalogService } from "./application/catalog-service.js";
+import type { ProviderService } from "./application/provider-service.js";
 import type { ExecService } from "./exec-service.js";
 import type { ToolRegistry } from "./tool-registry.js";
 import type { ToolRunner } from "./tool-runner.js";
@@ -49,6 +50,8 @@ export interface ServerContext {
     runService: RunService;
     extensionUiService: ExtensionUiService;
     catalogService: CatalogService;
+    /** The providers a person added through the settings window. */
+    providerService: ProviderService;
     execService: ExecService;
     toolRegistry: ToolRegistry;
     toolRunner: ToolRunner;

package/dist/server/types.d.ts

@@ -377,6 +377,29 @@ export type ModelOption = ModelSelection & {
  * honest answer is "the list could not be read". `fetchedAt` travels with the value so a stale
  * cache is visible rather than silent.
  */
+/**
+ * A provider a person added through the settings window, as the BROWSER sees it.
+ *
+ * The API key is a FACT here and not a value: `hasKey` says whether one is stored, and the key
+ * itself never leaves the server. It is in Super Pi's own registry and in Pi's `auth.json`, both of
+ * them files with restrictive permissions, and in neither the state snapshot nor any event.
+ */
+export type PublicProviderModel = {
+    id: string;
+    name: string;
+    reasoning: boolean;
+    imageInput: boolean;
+    contextWindow: number;
+    maxTokens: number;
+};
+export type PublicProvider = {
+    id: string;
+    name: string;
+    baseUrl: string;
+    api: string;
+    hasKey: boolean;
+    models: PublicProviderModel[];
+};
 export type ModelCatalog = {
     source: "pi" | "unavailable";
     models: ModelOption[];
@@ -874,6 +897,43 @@ export type ClientCommandBody =
     type: "model.rules.set";
     rules: ModelFilterRule[];
 }
+/**
+ * Adds a provider, or adds a model to one, or updates one.
+ *
+ * The key is OPTIONAL and its absence means "keep the stored one": the key is never shown again
+ * once it is saved, so an empty field is the normal state of the form for a provider that already
+ * has one. `clearKey` is how a person asks for it to be removed.
+ */
+ | {
+    type: "providers.set";
+    provider: {
+        id: string;
+        name?: string;
+        baseUrl: string;
+        api: string;
+        apiKey?: string;
+        clearKey?: boolean;
+        models: {
+            id: string;
+            name?: string;
+            reasoning?: boolean;
+            imageInput?: boolean;
+            contextWindow?: number;
+            maxTokens?: number;
+            supportsDeveloperRole?: boolean;
+            supportsReasoningEffort?: boolean;
+        }[];
+    };
+}
+/** Removes a provider Super Pi manages. One it does not manage is refused. */
+ | {
+    type: "providers.remove";
+    providerId: string;
+}
+/** Asks for the providers Super Pi manages. The answer carries no key. */
+ | {
+    type: "providers.fetch";
+}
 /**
  * Sets the app-wide default model. `null` clears it back to "Pi's own default" - the same
  * "absence, not a frozen copy" convention the workspace defaults use, so removing the default
@@ -1330,6 +1390,18 @@ export type ServerEvent = {
     type: "model.catalog.all";
     catalog: ModelCatalog;
 }
+/**
+ * The providers Super Pi manages. Sent when they change, and when a client connects.
+ *
+ * `apis` travels with them so the form's API-type list has ONE source of truth: the list of
+ * adapters Pi ships is a fact about the Pi that is installed, and a copy of it in the browser
+ * would be a copy that goes stale.
+ */
+ | {
+    type: "providers.list";
+    providers: PublicProvider[];
+    apis: string[];
+}
 /**
  * The answer to conversation.autoRename. Carries a title OR an error and never both, because the client
  * has exactly two things to say about it: here is the new name, or here is why there isnt one.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@evandu/super-pi",
-  "version": "0.1.104",
+  "version": "0.1.105",
   "description": "Web control plane and companion for Pi",
   "license": "MIT",
   "type": "module",
@@ -94,6 +94,8 @@
     "scripts/agent-config-regression.test.mjs",
     "scripts/model-filter.test.mjs",
     "scripts/settings-default-model.test.mjs",
+    "scripts/provider-registry.test.mjs",
+    "scripts/provider-pi-reads.test.mjs",
     "scripts/active-memory.test.mjs",
     "scripts/knowledge-base.test.mjs",
     "scripts/tool-runner.test.mjs",
@@ -140,6 +142,7 @@
     "scripts/theme-switch-state.test.mjs",
     "scripts/settings-window-structure.test.mjs",
     "scripts/settings-model-browser.test.mjs",
+    "scripts/provider-browser.test.mjs",
     "scripts/file-tab-selected-contrast.test.mjs",
     "scripts/help-window.test.mjs",
     "scripts/composer-regression-browser.test.mjs",