@arjunkhera/atlas 0.3.5 → 0.3.7

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "atlas",
-  "version": "0.3.5",
+  "version": "0.3.7",
   "description": "Atlas: the delivery lifecycle, its crews and the Atlas tools, for any repository.",
   "author": {
     "name": "Arjun Khera"

package/.mcp.json

@@ -7,6 +7,7 @@
       ],
       "env": {
         "ATLAS_ENGRAM": "${user_config.engram_connection}",
+        "ATLAS_ENGRAM_CLOUD": "${ATLAS_ENGRAM:-}",
         "ATLAS_WORK_OWNER_PRESENT": "1",
         "ATLAS_WORK_JOURNAL": "",
         "ATLAS_WORK_SESSION": "",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@arjunkhera/atlas",
-  "version": "0.3.5",
+  "version": "0.3.7",
   "description": "Atlas: the delivery lifecycle, its crews and the Atlas tools, as a Claude Code plugin for any repository.",
   "type": "module",
   "license": "UNLICENSED",

package/work/lib/child-env.mjs

@@ -1,11 +1,25 @@
 // The variables a program started by Atlas receives: a short list, never the
 // Engram connection, never an ATLAS_WORK_* setting (F11 study, fix one).
 const CHILD_VARIABLES = ['PATH', 'HOME', 'USER', 'LOGNAME', 'LANG', 'LC_ALL', 'TMPDIR', 'XDG_CONFIG_HOME', 'SSL_CERT_FILE', 'SSH_AUTH_SOCK'];
+// A Claude cloud session reaches GitHub only through Claude's own proxy on the
+// loopback address. Its GH_TOKEN is a stand-in that only that proxy turns into
+// a real credential, so `gh` with no proxy gets "Bad credentials". In a cloud
+// session only, a program also receives the proxy variables, and only when the
+// proxy is a loopback address (owner, 7 October 2026: "yes fix it and test").
+const CLOUD_PROXY_VARIABLES = ['HTTPS_PROXY', 'https_proxy'];
+const CLOUD_NO_PROXY_VARIABLES = ['NO_PROXY', 'no_proxy'];
+const LOOPBACK_PROXY = /^http:\/\/(127\.0\.0\.1|localhost|\[::1\]):\d{1,5}\/?$/;
 
 export function childEnvironment(env = process.env) {
   const out = {};
   for (const [name, value] of Object.entries(env)) {
     if (CHILD_VARIABLES.includes(name) || name.startsWith('GH_') || name === 'GITHUB_TOKEN') out[name] = value;
   }
+  if (env.CLAUDE_CODE_REMOTE === 'true') {
+    const proxies = CLOUD_PROXY_VARIABLES.filter((name) => env[name] !== undefined);
+    if (proxies.length && proxies.every((name) => LOOPBACK_PROXY.test(env[name]))) {
+      for (const name of [...proxies, ...CLOUD_NO_PROXY_VARIABLES]) if (env[name] !== undefined) out[name] = env[name];
+    }
+  }
   return out;
 }

package/work/mcp.mjs

@@ -8,8 +8,11 @@
 // The Engram address and key arrive together, as one setting, in
 // ATLAS_ENGRAM. When that setting arrives empty, the server reads the same
 // value from one owner-only file, ~/.config/atlas/engram-connection (atlas#101:
-// Claude Desktop starts the server with the sensitive setting empty). It reads
-// them from nowhere else.
+// Claude Desktop starts the server with the sensitive setting empty). In a
+// Claude cloud session only, it reads the cloud environment's own ATLAS_ENGRAM
+// variable first, which .mcp.json passes on as ATLAS_ENGRAM_CLOUD, because the
+// empty plugin setting hides it and a cloud setup script cannot see it. It
+// reads them from nowhere else.
 import { execFileSync } from 'node:child_process';
 import { randomUUID } from 'node:crypto';
 import { resolve, isAbsolute, dirname, join, delimiter } from 'node:path';
@@ -111,6 +114,7 @@ function readConnectionFile(env) {
 }
 export function readConnection(env, { allowLoopbackHttp = false, now = Date.now() } = {}) {
   let raw = unset(env.ATLAS_ENGRAM) ? '' : String(env.ATLAS_ENGRAM).trim();
+  if (!raw && inClaudeCloud(env) && !unset(env.ATLAS_ENGRAM_CLOUD)) raw = String(env.ATLAS_ENGRAM_CLOUD).trim();
   if (!raw) {
     const file = readConnectionFile(env);
     if (file.refused) return { state: 'bad', message: `The Engram connection file is refused. ${file.refused}` };