kritya 0.8.41-beta → 0.8.43-beta

package/dist/commands/doctor.js

@@ -2,7 +2,7 @@ import fs from "node:fs";
 import os from "node:os";
 import path from "node:path";
 import { createRequire } from "node:module";
-import { BUILTIN_PROVIDERS, CONFIG_DIR, CONFIG_FILE, legacyGlobalModel, loadConfig, privacyModeFor, resolveProvider, } from "../config/config.js";
+import { BUILTIN_PROVIDERS, CONFIG_DIR, CONFIG_FILE, legacyGlobalModel, loadConfig, loadDotEnv, privacyModeFor, resolveProvider, } from "../config/config.js";
 import { DEFAULT_MODEL, contextWindowFor } from "../config/models.js";
 import { retentionDaysFor } from "../config/retention.js";
 import { assertJsonWithinLimits } from "../config/jsonSafety.js";
@@ -368,6 +368,13 @@ export async function runDoctorCli(argv, options = {}) {
     const offline = argv.includes("--offline");
     const dirArg = argv.find((a) => !a.startsWith("-"));
     const workspace = path.resolve(options.workspace ?? dirArg ?? ".");
+    // The user's own global .env is unconditionally trusted and is where the
+    // interactive and headless paths both pick up provider keys (see
+    // `runInteractive` in index.tsx and `runHeadless` in headless.ts). Without
+    // loading it here the provider check below sees only the ambient
+    // environment, so a key that lives solely in ~/.kritya/.env is reported as
+    // missing — a false "no API key" that also flips the exit code to 1.
+    loadDotEnv([path.join(CONFIG_DIR, ".env")]);
     const sections = await collectDiagnostics({ ...options, workspace, offline });
     const report = summarize(sections, workspace);
     if (json) {

package/dist/shell/sandbox.js

@@ -3,9 +3,29 @@ import fs from "node:fs";
 import { createRequire } from "node:module";
 import os from "node:os";
 import path from "node:path";
+import { CONFIG_DIR, loadDotEnv } from "../config/config.js";
 import { classifyDanger } from "../permissions/danger.js";
 let cachedTool;
 let cachedMxcExec;
+let dotEnvLoaded = false;
+/**
+ * Load `~/.kritya/.env` before the backend is resolved, once per process.
+ *
+ * `locateMxcExecutable` reads `KRITYA_MXC_EXEC` and `MXC_BIN_DIR` from the
+ * environment, but the sandbox module is callable from frontends that never
+ * load the global `.env` themselves (the tool executor reaches
+ * `sandboxAvailable()` directly). Without this, a user who configured the MXC
+ * path in `.env` would have it honoured only when some *other* entry point
+ * happened to load the file first — and because `sandboxTool()` memoizes its
+ * answer, a miss could not self-correct later in the session. Loading here
+ * makes discovery independent of who calls it first.
+ */
+function loadSandboxEnv() {
+    if (dotEnvLoaded)
+        return;
+    dotEnvLoaded = true;
+    loadDotEnv([path.join(CONFIG_DIR, ".env")]);
+}
 function commandExists(bin) {
     const finder = os.platform() === "win32" ? "where" : "which";
     try {
@@ -73,11 +93,13 @@ function mxcExecutable() {
 export function resetSandboxToolCache() {
     cachedTool = undefined;
     cachedMxcExec = undefined;
+    dotEnvLoaded = false;
 }
 /** Which sandbox backend (if any) is usable on this platform, cached after the first check. */
 function sandboxTool() {
     if (cachedTool !== undefined)
         return cachedTool;
+    loadSandboxEnv();
     const platform = os.platform();
     if (platform === "linux") {
         cachedTool = commandExists("bwrap") ? "bwrap" : null;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "kritya",
-  "version": "0.8.41-beta",
+  "version": "0.8.43-beta",
   "description": "Kritya — Superintelligence at your command line",
   "type": "module",
   "publishConfig": {