@elliotsystems/eai 0.1.0 → 0.1.2

package/bin/eai

@@ -24,6 +24,7 @@ const {
   isExplicitlyConfigured,
   resolveOpencodeBin,
 } = require("../lib/resolve.js")
+const { injectToken } = require("../lib/token-env.js")
 
 /**
  * Resolve symlinks before deriving the package root.
@@ -81,6 +82,11 @@ if (process.env.ELLIOT_LAUNCHER_DEBUG) {
   process.stderr.write(`eai: launching ${resolved.path} (via ${resolved.source})\n`)
 }
 
+// Make the current Elliot token available to the runtime's `elliot` provider
+// (which reads it as ELLIOT_TOKEN). Best-effort and side-effect-free on failure;
+// the child inherits process.env, so setting it here is enough.
+injectToken(process.env)
+
 // argv passes through untouched and WITHOUT a shell, so quoting, spaces and
 // shell metacharacters in a prompt reach the runtime as the user typed them and
 // are never re-interpreted by an intermediate shell.

package/lib/token-env.js

@@ -0,0 +1,48 @@
+"use strict"
+
+/**
+ * Inject the Elliot access token into the environment the OpenCode runtime
+ * inherits, so its `elliot` provider (configured by `elliot-ai setup` to use
+ * `apiKey: "{env:ELLIOT_TOKEN}"`) authenticates against the LightLLM proxy.
+ *
+ * ~/.elliot/config.json is the single source of truth for the token; the CLI
+ * (`elliot-ai`) refreshes it there. We only READ it here and copy the current
+ * `jwt_token` into ELLIOT_TOKEN — no network, no writes, so this adds no latency
+ * and cannot corrupt the config.
+ *
+ * Entirely best-effort: a missing/unreadable/corrupt config, or an env that
+ * already sets ELLIOT_TOKEN, leaves things exactly as they were. The launcher's
+ * one job — spawning the runtime — must never be blocked by token wiring.
+ */
+
+const fs = require("fs")
+const os = require("os")
+const path = require("path")
+
+/**
+ * @param {NodeJS.ProcessEnv} env the environment to mutate (defaults to process.env)
+ * @returns {boolean} true iff ELLIOT_TOKEN was set from the config file
+ */
+function injectToken(env) {
+  const target = env || process.env
+
+  // An explicit ELLIOT_TOKEN in the environment wins — it lets a caller point
+  // `eai` at a specific token without touching the config file.
+  if (target.ELLIOT_TOKEN) return false
+
+  try {
+    const configPath = path.join(os.homedir(), ".elliot", "config.json")
+    const raw = fs.readFileSync(configPath, "utf-8")
+    const config = JSON.parse(raw)
+    if (config && typeof config.jwt_token === "string" && config.jwt_token) {
+      target.ELLIOT_TOKEN = config.jwt_token
+      return true
+    }
+  } catch {
+    // No config yet (setup not run), unreadable, or malformed — the runtime
+    // will simply have no elliot token, which is the pre-existing behaviour.
+  }
+  return false
+}
+
+module.exports = { injectToken }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@elliotsystems/eai",
-  "version": "0.1.0",
+  "version": "0.1.2",
   "description": "Elliot AI CLI entry point (eai) - launches the Elliot runtime with arguments forwarded verbatim.",
   "bin": {
     "eai": "./bin/eai"
@@ -24,10 +24,10 @@
     "access": "public"
   },
   "optionalDependencies": {
-    "@elliotsystems/eai-darwin-arm64": "0.1.0",
-    "@elliotsystems/eai-darwin-x64": "0.1.0",
-    "@elliotsystems/eai-linux-x64": "0.1.0",
-    "@elliotsystems/eai-linux-arm64": "0.1.0",
-    "@elliotsystems/eai-windows-x64": "0.1.0"
+    "@elliotsystems/eai-darwin-arm64": "0.1.2",
+    "@elliotsystems/eai-darwin-x64": "0.1.2",
+    "@elliotsystems/eai-linux-x64": "0.1.2",
+    "@elliotsystems/eai-linux-arm64": "0.1.2",
+    "@elliotsystems/eai-windows-x64": "0.1.2"
   }
 }