@mindstudio-ai/remy 0.1.322 → 0.1.323

package/dist/headless.js

@@ -2334,11 +2334,23 @@ var bashTool = {
     const maxLines = input.maxLines === 0 ? Infinity : input.maxLines || DEFAULT_MAX_LINES2;
     const timeoutMs = input.timeout ? input.timeout * 1e3 : DEFAULT_TIMEOUT_MS;
     return new Promise((resolve4) => {
-      const child = spawn2("sh", ["-c", input.command], {
+      const child = spawn2("bash", ["-c", input.command], {
         // Pinned rather than inherited. `undefined` here means "wherever the
         // process happens to be", which is the project root only by luck.
         cwd: input.cwd ? path7.resolve(PROJECT_ROOT, input.cwd) : PROJECT_ROOT,
-        env: { ...process.env, FORCE_COLOR: "1" }
+        // Output is rendered in a terminal view in the IDE, so ask tools for
+        // color. The devbox image sets none of these — it declares only
+        // WORKSPACE_DIR, LANG, LC_ALL, PIP_BREAK_SYSTEM_PACKAGES,
+        // NPM_CONFIG_PREFIX and PATH — and a container gets no TERM unless
+        // something sets it, so without TERM anything driving terminfo assumes
+        // a dumb terminal. Same trio the sandbox's pty handler sets, for the
+        // same reason; FORCE_COLOR alone only reaches the Node/chalk ecosystem.
+        env: {
+          ...process.env,
+          TERM: "xterm-256color",
+          CLICOLOR: "1",
+          FORCE_COLOR: "1"
+        }
       });
       let output = "";
       child.stdout.on("data", (chunk) => {

package/dist/index.js

@@ -3519,11 +3519,23 @@ var init_bash = __esm({
         const maxLines = input.maxLines === 0 ? Infinity : input.maxLines || DEFAULT_MAX_LINES2;
         const timeoutMs = input.timeout ? input.timeout * 1e3 : DEFAULT_TIMEOUT_MS;
         return new Promise((resolve4) => {
-          const child = spawn2("sh", ["-c", input.command], {
+          const child = spawn2("bash", ["-c", input.command], {
             // Pinned rather than inherited. `undefined` here means "wherever the
             // process happens to be", which is the project root only by luck.
             cwd: input.cwd ? path7.resolve(PROJECT_ROOT, input.cwd) : PROJECT_ROOT,
-            env: { ...process.env, FORCE_COLOR: "1" }
+            // Output is rendered in a terminal view in the IDE, so ask tools for
+            // color. The devbox image sets none of these — it declares only
+            // WORKSPACE_DIR, LANG, LC_ALL, PIP_BREAK_SYSTEM_PACKAGES,
+            // NPM_CONFIG_PREFIX and PATH — and a container gets no TERM unless
+            // something sets it, so without TERM anything driving terminfo assumes
+            // a dumb terminal. Same trio the sandbox's pty handler sets, for the
+            // same reason; FORCE_COLOR alone only reaches the Node/chalk ecosystem.
+            env: {
+              ...process.env,
+              TERM: "xterm-256color",
+              CLICOLOR: "1",
+              FORCE_COLOR: "1"
+            }
           });
           let output = "";
           child.stdout.on("data", (chunk) => {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mindstudio-ai/remy",
-  "version": "0.1.322",
+  "version": "0.1.323",
   "description": "Remy coding agent",
   "repository": {
     "type": "git",