@evandu/super-pi 0.1.120 → 0.1.121

package/dist/client/.super-pi-client-sources.json

@@ -30,5 +30,5 @@
     "src/client/types.ts": "7654e95b65053d639634e0bbee2b4524831571ec59c79d4b8384d1eeb662b0cf",
     "src/client/vite-env.d.ts": "65996936fbb042915f7b74a200fcdde7e410f32a669b1ab9597cfaa4b0faddb5"
   },
-  "recordedAt": "2026-10-23T06:23:16.694Z"
+  "recordedAt": "2026-10-23T06:47:25.078Z"
 }

package/dist/server/application/provider-service.d.ts

@@ -49,7 +49,7 @@ export declare class ProviderService {
      * asks for it to go.
      */
     set(input: unknown): Promise<PublicProvider[]>;
-    /** Removes a provider Super Pi manages, and only one it manages. */
+    /** Removes a provider from Pi's models.json and auth.json. */
     remove(providerId: string): Promise<PublicProvider[]>;
     /**
      * Removes ONE model from a provider, leaving the provider and its other models alone.

package/dist/server/application/provider-service.js

@@ -101,7 +101,7 @@ export class ProviderService {
         await this.afterChange();
         return publicProviders(next);
     }
-    /** Removes a provider Super Pi manages, and only one it manages. */
+    /** Removes a provider from Pi's models.json and auth.json. */
     async remove(providerId) {
         const previous = await this.registry.load();
         const existing = previous.find((provider) => provider.id === providerId);

package/dist/server/providers.d.ts

@@ -62,6 +62,7 @@ export type ProviderDefinition = {
     api: string;
     /** The API key. Stored, never broadcast. */
     apiKey?: string;
+    hasAuthKey?: boolean;
     models: ProviderModelDefinition[];
 };
 /** One model, as the browser sees it. No key, no nothing secret - there is nothing secret here. */
@@ -116,36 +117,19 @@ export declare class ProviderRegistry {
     /** Super Pi's own registry: the providers it manages, with their keys. */
     private get registryPath();
     /**
-     * Reads the registry.
-     *
-     * A missing file is an empty registry, not an error: nobody has added a provider yet. A file that
-     * cannot be parsed IS an error, because reading it as empty would let the next write replace
-     * somebody's keys with nothing.
+     * Reads all configured providers directly from Pi's models.json and auth.json.
+     * Super Pi acts as the direct visual management plane for Pi's model configurations.
      */
     load(): Promise<ProviderDefinition[]>;
     /** Writes the registry. The key lives here, so the file is 0600. */
     save(providers: ProviderDefinition[]): Promise<void>;
     /**
-     * Makes Pi's files match the registry.
-     *
-     * `previousIds` are the providers Super Pi managed before this change: they are the only ones
-     * whose entries may be REMOVED. An id that is in Pi's `models.json` and not in `previousIds` belongs
-     * to the person who wrote that file, and touching it would be Super Pi editing a provider it does
-     * not own - so the write is refused with a message naming the id.
+     * Directly updates Pi's models.json and auth.json to match the new set of providers.
+     * Full visual editor semantics: any provider in models.json is editable and removable.
      */
     applyToPi(previous: ProviderDefinition[], next: ProviderDefinition[]): Promise<void>;
     /**
      * Writes the keys into Pi's `auth.json`.
-     *
-     * A credential is REMOVED only when it is the one Super Pi wrote: the same provider id and the
-     * same key. A person who replaced our key with their own - or who ran Pi's `/login` and put an
-     * OAuth token there - keeps it. Deleting somebody else's credential because they removed our
-     * provider would be the worst version of this feature.
-     *
-     * TWO CASES, and the second is the one that is easy to miss: the provider can be gone ENTIRELY
-     * (it was removed), or it can still be there with its key GONE (the person asked for the key to be
-     * cleared). Both have to take the credential with them, or "clear the key" would leave a working
-     * key sitting in Pi's auth file.
      */
     private applyKeysToPi;
 }

package/dist/server/providers.js

@@ -224,32 +224,65 @@ export class ProviderRegistry {
         return join(this.dataDir, "providers.json");
     }
     /**
-     * Reads the registry.
-     *
-     * A missing file is an empty registry, not an error: nobody has added a provider yet. A file that
-     * cannot be parsed IS an error, because reading it as empty would let the next write replace
-     * somebody's keys with nothing.
+     * Reads all configured providers directly from Pi's models.json and auth.json.
+     * Super Pi acts as the direct visual management plane for Pi's model configurations.
      */
     async load() {
-        const raw = await readJsonFile(this.registryPath);
-        if (!raw || typeof raw !== "object")
-            return [];
-        const providers = raw.providers;
-        if (!Array.isArray(providers))
-            return [];
-        return providers.filter((provider) => Boolean(provider) && typeof provider === "object");
+        const modelsPath = piModelsPath(this.piDir);
+        const authPath = piAuthPath(this.piDir);
+        const piModels = (await readJsonFile(modelsPath))?.providers ?? {};
+        const piAuth = (await readJsonFile(authPath)) ?? {};
+        // Backup registry from Super Pi data dir if needed
+        const rawBackup = await readJsonFile(this.registryPath);
+        const backupList = rawBackup && typeof rawBackup === "object" && Array.isArray(rawBackup.providers)
+            ? rawBackup.providers.filter((p) => Boolean(p) && typeof p === "object")
+            : [];
+        const backupMap = new Map(backupList.map((p) => [p.id, p]));
+        const providers = [];
+        const seen = new Set();
+        for (const [pId, pData] of Object.entries(piModels)) {
+            if (!pData || typeof pData !== "object")
+                continue;
+            seen.add(pId);
+            const rec = pData;
+            const backup = backupMap.get(pId);
+            const baseUrl = typeof rec.baseUrl === "string" ? rec.baseUrl : (backup?.baseUrl ?? "");
+            const api = typeof rec.api === "string" ? rec.api : (backup?.api ?? "openai-completions");
+            const name = typeof rec.name === "string" ? rec.name : (backup?.name ?? pId);
+            const rawModels = Array.isArray(rec.models) ? rec.models : (backup?.models ?? []);
+            const models = rawModels.map((m) => ({
+                id: typeof m?.id === "string" ? m.id : String(m),
+                name: typeof m?.name === "string" ? m.name : m?.id,
+                reasoning: Boolean(m?.reasoning),
+                imageInput: Array.isArray(m?.input) ? m.input.includes("image") : false,
+                contextWindow: typeof m?.contextWindow === "number" ? m.contextWindow : undefined,
+                maxTokens: typeof m?.maxTokens === "number" ? m.maxTokens : undefined,
+            }));
+            const apiKey = backup?.apiKey;
+            providers.push({
+                id: pId,
+                name,
+                baseUrl,
+                api,
+                ...(apiKey ? { apiKey } : {}),
+                hasAuthKey: Boolean(piAuth[pId]?.key || backup?.apiKey),
+                models,
+            });
+        }
+        for (const b of backupList) {
+            if (!seen.has(b.id)) {
+                providers.push(b);
+            }
+        }
+        return providers;
     }
     /** Writes the registry. The key lives here, so the file is 0600. */
     async save(providers) {
         await writeJsonAtomic(this.registryPath, { providers });
     }
     /**
-     * Makes Pi's files match the registry.
-     *
-     * `previousIds` are the providers Super Pi managed before this change: they are the only ones
-     * whose entries may be REMOVED. An id that is in Pi's `models.json` and not in `previousIds` belongs
-     * to the person who wrote that file, and touching it would be Super Pi editing a provider it does
-     * not own - so the write is refused with a message naming the id.
+     * Directly updates Pi's models.json and auth.json to match the new set of providers.
+     * Full visual editor semantics: any provider in models.json is editable and removable.
      */
     async applyToPi(previous, next) {
         const previousIds = new Set(previous.map((provider) => provider.id));
@@ -257,15 +290,9 @@ export class ProviderRegistry {
         const modelsPath = piModelsPath(this.piDir);
         const existing = await readJsonFile(modelsPath) ?? {};
         const existingProviders = existing.providers ?? {};
-        for (const provider of next) {
-            if (existingProviders[provider.id] !== undefined && !previousIds.has(provider.id)) {
-                throw new Error(`Pi 的 models.json 里已经有供应商「${provider.id}」，而它不是 Super Pi 添加的，所以没有动它。请换一个供应商 id，或者先在 Pi 的模型配置文件里删掉它。`);
-            }
-        }
         const mergedProviders = { ...existingProviders };
         for (const provider of next)
             mergedProviders[provider.id] = toPiProvider(provider);
-        // The ones we managed and no longer do.
         for (const id of previousIds)
             if (!nextIds.has(id))
                 delete mergedProviders[id];
@@ -274,16 +301,6 @@ export class ProviderRegistry {
     }
     /**
      * Writes the keys into Pi's `auth.json`.
-     *
-     * A credential is REMOVED only when it is the one Super Pi wrote: the same provider id and the
-     * same key. A person who replaced our key with their own - or who ran Pi's `/login` and put an
-     * OAuth token there - keeps it. Deleting somebody else's credential because they removed our
-     * provider would be the worst version of this feature.
-     *
-     * TWO CASES, and the second is the one that is easy to miss: the provider can be gone ENTIRELY
-     * (it was removed), or it can still be there with its key GONE (the person asked for the key to be
-     * cleared). Both have to take the credential with them, or "clear the key" would leave a working
-     * key sitting in Pi's auth file.
      */
     async applyKeysToPi(previous, next) {
         const authPath = piAuthPath(this.piDir);
@@ -295,7 +312,6 @@ export class ProviderRegistry {
         }
         for (const provider of previous) {
             const updated = nextById.get(provider.id);
-            // The key is still wanted (the provider is unchanged, or it has a new one) - nothing to do.
             if (updated && updated.apiKey)
                 continue;
             if (!updated && !provider.apiKey)
@@ -314,7 +330,7 @@ export function publicProviders(providers) {
         name: provider.name ?? provider.id,
         baseUrl: provider.baseUrl,
         api: provider.api,
-        hasKey: Boolean(provider.apiKey),
+        hasKey: Boolean(provider.apiKey || provider.hasAuthKey),
         models: provider.models.map(model => ({
             id: model.id,
             name: model.name ?? model.id,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@evandu/super-pi",
-  "version": "0.1.120",
+  "version": "0.1.121",
   "description": "Web control plane and companion for Pi",
   "license": "MIT",
   "type": "module",