@mono-agent/agent-runtime 0.17.0 → 0.17.1

package/MIGRATION.md

@@ -72,6 +72,11 @@ the runtime applies them only when Bash, Exec, or a nested subagent process is
 spawned. It does not mutate `process.env` or persist the values in prompts,
 metadata, history, traces, or long-lived tool context.
 
+- **0.17.1 Pi auth classification:** Pi 0.83 may report a missing credential as
+  `Provider is not configured: <provider>`. The runtime now classifies that
+  exact signature as `provider_auth`, allowing a configured fallback route to
+  run while avoiding a same-route retry that cannot repair absent credentials.
+
 ## 0.16.x
 
 This baseline carries the whole 0.15.x contract forward and adds:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mono-agent/agent-runtime",
-  "version": "0.17.0",
+  "version": "0.17.1",
   "description": "Agent runtime supporting Claude SDK/CLI, Codex, OpenCode, and Pi SDK bridges out of the box",
   "type": "module",
   "license": "GPL-3.0-only",

package/src/ai/failure.js

@@ -72,7 +72,11 @@ export const FAILURE_KINDS = [
 
 const CONTEXT_LIMIT_RE = /(?:context[_ ](?:length|window|budget)|token[_ ]limit|(?:input|prompt)(?:[_ ]tokens?)?[_ ](?:is[_ ])?too[_ ]long|(?:input|prompt|request)(?:[_ ]tokens?)?[_ ]exceeds?[_ ](?:the[_ ])?(?:context|maximum|max|limit|allowed[_ ]size)|too[_ ]many[_ ](?:input[_ ])?tokens?|tokens?[_ ]exceed(?:s|ed)?[_ ](?:the[_ ])?(?:context|maximum|max|(?:model[_ ])?limit))/i;
 const USAGE_LIMIT_RE = /(rate limit|usage limit|max(?:imum)?(?:[_ ]output)?[_ ]tokens?|max turns)/i;
-const PROVIDER_AUTH_RE = /(no api key|missing api key|api key required|invalid api key|incorrect api key|authentication|authorization|not authorized|forbidden|oauth (?:refresh|auth|authentication|token).*failed|credential store (?:read|modify) failed|401|403)/i;
+// Pi's Models layer emits the exact `Provider is not configured: <id>` message
+// only after it has found the provider but cannot resolve that provider's auth.
+// Treating it as availability left credential fallbacks pinned to the dead
+// route because the router only advances on provider_auth or retryable outages.
+const PROVIDER_AUTH_RE = /(no api key|missing api key|api key required|invalid api key|incorrect api key|provider is not configured:|authentication|authorization|not authorized|forbidden|oauth (?:refresh|auth|authentication|token).*failed|credential store (?:read|modify) failed|401|403)/i;
 // Mirrors the conservative connection-error/refused/failed alternation added to
 // RETRYABLE_PROVIDER_RE / retryableProviderSubkind below for pi 0.80's terse
 // "Connection error." — without it, classifyFailure (used directly by hosts
@@ -81,7 +85,7 @@ const PROVIDER_AUTH_RE = /(no api key|missing api key|api key required|invalid a
 // "provider_unavailable".
 const PROVIDER_UNAVAILABLE_RE = /(econn|enotfound|etimedout|timed? ?out|service unavailable|503|502|gateway|fetch failed|network|websocket|\bconnection (?:error|refused|failed)\b|\bcould not connect\b)/i;
 const TOOL_FAILURE_RE = /(tool .* failed|mcp tool|permission denied|EACCES|read-only file system)/i;
-const NON_RETRYABLE_PROVIDER_RE = /(invalid[_ ]request|unknown parameter|no api key|missing api key|api key required|invalid api key|incorrect api key|authentication|authorization|not authorized|forbidden|billing|insufficient[_ ]quota|quota exceeded|model[_ ]not[_ ]found|unsupported model|permission denied|bad request|401|403|404)/i;
+const NON_RETRYABLE_PROVIDER_RE = /(invalid[_ ]request|unknown parameter|no api key|missing api key|api key required|invalid api key|incorrect api key|provider is not configured:|authentication|authorization|not authorized|forbidden|billing|insufficient[_ ]quota|quota exceeded|model[_ ]not[_ ]found|unsupported model|permission denied|bad request|401|403|404)/i;
 // pi 0.80's openai-client-style bridge collapses a connection-refused/unreachable
 // provider down to a terse "Connection error." with no cause text (no ECONNREFUSED,
 // no fetch failed) — the `\bconnection (?:error|refused|failed)\b|\bcould not connect\b`