@pwguler/pi-pengepul-provider 0.5.2 → 0.5.3

package/extensions/credential.ts

@@ -10,7 +10,7 @@
  * override, then the credential, then the loopback default pengepul binds to.
  */
 
-import { API_KEY_ENV } from "./config.ts"
+import { API_KEY_ENV, RELAY_BASE_ENV } from "./config.ts"
 import { normalizeRootBaseUrl } from "./dialect.ts"
 import { DEFAULT_RELAY_BASE } from "./models.ts"
 
@@ -30,9 +30,18 @@ function nonEmptyString(value: unknown): string | undefined {
   return trimmed === "" ? undefined : trimmed
 }
 
-/** The relay base stored on the credential, when the user set one. */
+/**
+ * The relay base stored on the credential, when the user set one.
+ *
+ * `baseUrl` is where the stored credential keeps it. The credential pi hands
+ * the network phase of a refresh is not the stored one: pi rebuilds it from
+ * `resolve()` as `{ type, key, env }`, so the base only survives as the
+ * `PENGEPUL_BASE_URL` entry `resolve()` writes into `env`. Missing that
+ * fallback sends the catalog fetch to loopback - which on any machine but the
+ * relay's is some other listener, or nothing.
+ */
 export function credentialRelayBase(credential: PengepulCredential | undefined): string | undefined {
-  return nonEmptyString(credential?.baseUrl)
+  return nonEmptyString(credential?.baseUrl) ?? credentialEnv(credential)?.[RELAY_BASE_ENV]
 }
 
 /** The API key stored on the credential, when the user set one. */

package/extensions/provider.ts

@@ -212,11 +212,20 @@ export function createPengepulProvider(options: PengepulProviderOptions): Provid
         resolve: async (input): Promise<AuthResult | undefined> => {
           const resolved = resolveKey(input.credential)
           if (!resolved) return undefined
-          const env = credentialEnv(input.credential as PengepulCredential | undefined)
+          const credential = input.credential as PengepulCredential | undefined
+          const relayBase = credentialRelayBase(credential)
+          const credentialVars = credentialEnv(credential)
+          const env =
+            credentialVars || relayBase
+              ? { ...credentialVars, ...(relayBase ? { [RELAY_BASE_ENV]: relayBase } : {}) }
+              : undefined
           // No `baseUrl` here on purpose: pi would apply it to every model and
-          // collapse the two dialect base URLs into one.
+          // collapse the two dialect base URLs into one. The relay base rides
+          // in `env` instead, because the network phase of a refresh gets a
+          // credential pi rebuilds from this result, and `env` is the only
+          // field of ours that survives the rebuild.
           //
-          // `env` is here because pi only reads it off the credential itself
+          // The credential's own `env` is here because pi only reads it off the credential itself
           // when the provider brings no `resolve()` of its own — this one does,
           // so a value like PI_CACHE_RETENTION=long is dropped unless it is
           // handed back. Dropping it is silent and costs money: the cache falls

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pwguler/pi-pengepul-provider",
-  "version": "0.5.2",
+  "version": "0.5.3",
   "type": "module",
   "description": "pi custom provider for pengepul, a relay that pools your Claude/Codex subscriptions. Key and relay base live in auth.json; both native wires (Anthropic Messages, OpenAI Chat Completions) come from one catalog.",
   "license": "MIT",