From 2e2c281e49862e01044fc6ca15dd54c23994731d Mon Sep 17 00:00:00 2001
From: Jamie Chicago <87397251+jamiechicago312@users.noreply.github.com>
Date: Fri, 22 May 2026 11:17:26 -0500
Subject: [PATCH 1/6] fix: buildNpmScriptCommand always uses cmd.exe on Windows

On Windows, npm sets npm_execpath to a path like
  C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js
which contains spaces. buildNpmScriptCommand was returning that
path as a spawn argument with the full node.exe path as the command.
spawnService uses shell:true on Windows, so Node.js passes the
unquoted command to cmd.exe:

  cmd.exe /d /s /c C:\Program Files\nodejs\node.exe ...

cmd.exe splits on the space and fails with
  'C:\Program' is not recognized as an internal or external command
causing Vite to exit with code 1 immediately after npm run dev.

Fix: check platform === 'win32' BEFORE checking npm_execpath so
Windows always uses the safe cmd.exe /d /s /c npm run <script> form.

Co-authored-by: openhands <openhands@all-hands.dev>
---
 scripts/dev-safe.mjs | 19 +++++++++++++------
 1 file changed, 13 insertions(+), 6 deletions(-)

diff --git a/scripts/dev-safe.mjs b/scripts/dev-safe.mjs
index 437a7d1c4..5d088d64c 100644
--- a/scripts/dev-safe.mjs
+++ b/scripts/dev-safe.mjs
@@ -749,17 +749,24 @@ export function buildNpmScriptCommand(
   env = process.env,
   nodeExecPath = process.execPath,
 ) {
-  if (env.npm_execpath) {
+  // On Windows, always use cmd.exe regardless of whether npm_execpath is set.
+  // npm_execpath points to a path like
+  // "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" which contains
+  // spaces. When that path is passed as an argument with shell:true in
+  // spawnService, cmd.exe splits on the space and tries to run "C:\Program"
+  // as a command, producing "not recognized as an internal or external command".
+  // Using "npm" via cmd.exe avoids the problem entirely.
+  if (platform === "win32") {
     return {
-      command: env.npm_node_execpath || nodeExecPath,
-      args: [env.npm_execpath, "run", scriptName],
+      command: env.ComSpec || "cmd.exe",
+      args: ["/d", "/s", "/c", "npm", "run", scriptName],
     };
   }
 
-  if (platform === "win32") {
+  if (env.npm_execpath) {
     return {
-      command: env.ComSpec || "cmd.exe",
-      args: ["/d", "/s", "/c", "npm", "run", scriptName],
+      command: env.npm_node_execpath || nodeExecPath,
+      args: [env.npm_execpath, "run", scriptName],
     };
   }
 

From d6e83172f0bc0c7b1b3f3d48e5e78a39c78e6260 Mon Sep 17 00:00:00 2001
From: Jamie Chicago <87397251+jamiechicago312@users.noreply.github.com>
Date: Fri, 22 May 2026 11:17:27 -0500
Subject: [PATCH 2/6] fix: buildNpmScriptCommand always uses cmd.exe on Windows

On Windows, npm sets npm_execpath to a path like
  C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js
which contains spaces. buildNpmScriptCommand was returning that
path as a spawn argument with the full node.exe path as the command.
spawnService uses shell:true on Windows, so Node.js passes the
unquoted command to cmd.exe:

  cmd.exe /d /s /c C:\Program Files\nodejs\node.exe ...

cmd.exe splits on the space and fails with
  'C:\Program' is not recognized as an internal or external command
causing Vite to exit with code 1 immediately after npm run dev.

Fix: check platform === 'win32' BEFORE checking npm_execpath so
Windows always uses the safe cmd.exe /d /s /c npm run <script> form.

Co-authored-by: openhands <openhands@all-hands.dev>
---
 __tests__/scripts/dev-safe.test.ts | 41 ++++++++++++++++++++++--------
 1 file changed, 31 insertions(+), 10 deletions(-)

diff --git a/__tests__/scripts/dev-safe.test.ts b/__tests__/scripts/dev-safe.test.ts
index 2f540d149..62ca8f713 100644
--- a/__tests__/scripts/dev-safe.test.ts
+++ b/__tests__/scripts/dev-safe.test.ts
@@ -651,24 +651,45 @@ describe("getOrCreatePersistedSessionApiKey", () => {
 });
 
 describe("buildNpmScriptCommand", () => {
-  it("reuses npm's own CLI path when available", () => {
+  it("runs npm through cmd.exe on Windows even when npm_execpath is set", () => {
+    // npm_execpath points to a path with spaces like
+    // "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js".
+    // spawnService uses shell:true on Windows, so passing that path as an
+    // argument causes cmd.exe to split on the space and fail with
+    // "'C:\Program' is not recognized as an internal or external command".
+    // The win32 branch must fire BEFORE the npm_execpath branch.
     const command = buildNpmScriptCommand(
       "dev:frontend",
       "win32",
       {
-        npm_execpath: "C:\\nodejs\\node_modules\\npm\\bin\\npm-cli.js",
-        npm_node_execpath: "C:\\nodejs\\node.exe",
+        ComSpec: "C:\\Windows\\System32\\cmd.exe",
+        npm_execpath:
+          "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js",
+        npm_node_execpath: "C:\\Program Files\\nodejs\\node.exe",
       },
-      "C:\\fallback\\node.exe",
+      "C:\\Program Files\\nodejs\\node.exe",
     );
 
     expect(command).toEqual({
-      command: "C:\\nodejs\\node.exe",
-      args: [
-        "C:\\nodejs\\node_modules\\npm\\bin\\npm-cli.js",
-        "run",
-        "dev:frontend",
-      ],
+      command: "C:\\Windows\\System32\\cmd.exe",
+      args: ["/d", "/s", "/c", "npm", "run", "dev:frontend"],
+    });
+  });
+
+  it("reuses npm's own CLI path when available on POSIX", () => {
+    const command = buildNpmScriptCommand(
+      "dev:frontend",
+      "linux",
+      {
+        npm_execpath: "/usr/lib/node_modules/npm/bin/npm-cli.js",
+        npm_node_execpath: "/usr/bin/node",
+      },
+      "/fallback/node",
+    );
+
+    expect(command).toEqual({
+      command: "/usr/bin/node",
+      args: ["/usr/lib/node_modules/npm/bin/npm-cli.js", "run", "dev:frontend"],
     });
   });
 

From cea2a1fe4f008248dfbd0c7a234c31af517d2baf Mon Sep 17 00:00:00 2001
From: Jamie Chicago <87397251+jamiechicago312@users.noreply.github.com>
Date: Fri, 22 May 2026 11:40:52 -0500
Subject: [PATCH 3/6] fix: AnimatePresence mode=wait expects one child, not two

ChatStatusIndicator had two separately-keyed motion.span children inside
<AnimatePresence mode="wait">. framer-motion's wait mode expects exactly ONE
child to exit before the next enters; two children trigger the repeated warning:
  "attempting to animate multiple children within AnimatePresence,
   but its mode is set to 'wait'"

Fix: wrap both elements in a single motion.span with unified key={status}
and className="contents" (CSS display:contents preserves flex layout).

Co-authored-by: openhands <openhands@all-hands.dev>
---
 .../features/chat/chat-status-indicator.tsx   | 30 +++++++++----------
 1 file changed, 15 insertions(+), 15 deletions(-)

diff --git a/src/components/features/chat/chat-status-indicator.tsx b/src/components/features/chat/chat-status-indicator.tsx
index bf1de033d..8919e3b8a 100644
--- a/src/components/features/chat/chat-status-indicator.tsx
+++ b/src/components/features/chat/chat-status-indicator.tsx
@@ -18,29 +18,29 @@ function ChatStatusIndicator({
         "w-full max-w-full rounded-[100px] p-1 bg-[var(--oh-surface)] flex items-center gap-1",
       )}
     >
+      {/* Wrap both elements under a single keyed motion.div so AnimatePresence
+          mode="wait" sees one child instead of two. Having two separately-keyed
+          children inside mode="wait" triggers the framer-motion warning
+          "attempting to animate multiple children" because wait mode expects
+          only one child to exit before the next one enters. */}
       <AnimatePresence mode="wait">
-        {/* Dot */}
         <motion.span
-          key={`dot-${status}`}
-          className="flex-shrink-0 animate-[pulse_1.2s_ease-in-out_infinite]"
+          key={status}
+          className="contents"
           initial={{ opacity: 0 }}
           animate={{ opacity: 1 }}
           exit={{ opacity: 0 }}
           transition={{ duration: 0.3 }}
         >
-          <DebugStackframeDot className="w-4 h-4" color={statusColor} />
-        </motion.span>
+          {/* Dot */}
+          <span className="flex-shrink-0 animate-[pulse_1.2s_ease-in-out_infinite]">
+            <DebugStackframeDot className="w-4 h-4" color={statusColor} />
+          </span>
 
-        {/* Text */}
-        <motion.span
-          key={`text-${status}`}
-          initial={{ opacity: 0, y: -2 }}
-          animate={{ opacity: 1, y: 0 }}
-          exit={{ opacity: 0, y: 2 }}
-          transition={{ duration: 0.3 }}
-          className="pr-1.5 font-normal text-[11px] leading-[16px] normal-case break-words whitespace-normal"
-        >
-          {status}
+          {/* Text */}
+          <span className="pr-1.5 font-normal text-[11px] leading-[16px] normal-case break-words whitespace-normal">
+            {status}
+          </span>
         </motion.span>
       </AnimatePresence>
     </div>

From 53cd7ef8c8cbfac63f479a7939a47954f9706c25 Mon Sep 17 00:00:00 2001
From: Jamie Chicago <87397251+jamiechicago312@users.noreply.github.com>
Date: Fri, 22 May 2026 11:44:59 -0500
Subject: [PATCH 4/6] fix: set PYTHONUTF8=1 in agent-server/automation env on
 Windows
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Python on Windows defaults to the system ANSI codepage (cp1252). The agent-server
writes metadata JSON containing emoji (e.g. U+2705 ✅) that cp1252 cannot encode,
producing UnicodeEncodeError → POST /api/conversations 500. Old UTF-8 conversation
files also fail to load at startup (UnicodeDecodeError). PYTHONUTF8=1 enables
Python's UTF-8 mode (PEP 540) for the process, matching Linux/macOS behaviour.

Co-authored-by: openhands <openhands@all-hands.dev>
---
 scripts/dev-safe.mjs | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/scripts/dev-safe.mjs b/scripts/dev-safe.mjs
index 5d088d64c..57fad9b74 100644
--- a/scripts/dev-safe.mjs
+++ b/scripts/dev-safe.mjs
@@ -602,6 +602,17 @@ function buildConfigFromPorts(ports, cwd, env) {
  */
 export function buildAgentServerEnv(config) {
   return {
+    // Force Python to use UTF-8 for all file I/O and streams.
+    //
+    // On Windows, Python defaults to the system ANSI codepage (e.g. cp1252).
+    // The agent-server writes conversation metadata JSON that can contain
+    // emoji (e.g. ✅ U+2705) which cp1252 cannot encode, producing:
+    //   UnicodeEncodeError: 'charmap' codec can't encode character '\u2705'
+    // Setting PYTHONUTF8=1 enables Python's UTF-8 mode (PEP 540) for the
+    // entire agent-server process, matching the behaviour on Linux/macOS
+    // where the locale is already UTF-8.
+    // This is a no-op on Linux/macOS where the locale is already UTF-8.
+    PYTHONUTF8: "1",
     TMUX_TMPDIR: config.tmuxTmpDir,
     OH_CONVERSATIONS_PATH: config.conversationsPath,
     OH_BASH_EVENTS_DIR: config.bashEventsDir,

From 87dc55504bb80a8d4c371aff60633c9a98ffd7fb Mon Sep 17 00:00:00 2001
From: Jamie Chicago <87397251+jamiechicago312@users.noreply.github.com>
Date: Fri, 22 May 2026 11:45:00 -0500
Subject: [PATCH 5/6] fix: set PYTHONUTF8=1 in agent-server/automation env on
 Windows
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Python on Windows defaults to the system ANSI codepage (cp1252). The agent-server
writes metadata JSON containing emoji (e.g. U+2705 ✅) that cp1252 cannot encode,
producing UnicodeEncodeError → POST /api/conversations 500. Old UTF-8 conversation
files also fail to load at startup (UnicodeDecodeError). PYTHONUTF8=1 enables
Python's UTF-8 mode (PEP 540) for the process, matching Linux/macOS behaviour.

Co-authored-by: openhands <openhands@all-hands.dev>
---
 scripts/dev-with-automation.mjs | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/scripts/dev-with-automation.mjs b/scripts/dev-with-automation.mjs
index a8a82b841..ef2935737 100644
--- a/scripts/dev-with-automation.mjs
+++ b/scripts/dev-with-automation.mjs
@@ -603,6 +603,9 @@ function startAutomationBackend(config) {
     {
       cwd: config.stateDir,
       env: {
+        // Force UTF-8 for all Python file I/O (same reason as agent-server;
+        // see buildAgentServerEnv in dev-safe.mjs).
+        PYTHONUTF8: "1",
         // The URL the automation backend itself uses to call the
         // agent-server's REST API (tarball upload + bash dispatch).
         //

From 0a4efac1826340ff1093f0e8d816716988bb196d Mon Sep 17 00:00:00 2001
From: hieptl <hieptl.developer@gmail.com>
Date: Thu, 28 May 2026 16:11:59 +0700
Subject: [PATCH 6/6] refactor: remove unrelated file

---
 .../features/chat/chat-status-indicator.tsx   | 30 +++++++++----------
 1 file changed, 15 insertions(+), 15 deletions(-)

diff --git a/src/components/features/chat/chat-status-indicator.tsx b/src/components/features/chat/chat-status-indicator.tsx
index 8919e3b8a..bf1de033d 100644
--- a/src/components/features/chat/chat-status-indicator.tsx
+++ b/src/components/features/chat/chat-status-indicator.tsx
@@ -18,29 +18,29 @@ function ChatStatusIndicator({
         "w-full max-w-full rounded-[100px] p-1 bg-[var(--oh-surface)] flex items-center gap-1",
       )}
     >
-      {/* Wrap both elements under a single keyed motion.div so AnimatePresence
-          mode="wait" sees one child instead of two. Having two separately-keyed
-          children inside mode="wait" triggers the framer-motion warning
-          "attempting to animate multiple children" because wait mode expects
-          only one child to exit before the next one enters. */}
       <AnimatePresence mode="wait">
+        {/* Dot */}
         <motion.span
-          key={status}
-          className="contents"
+          key={`dot-${status}`}
+          className="flex-shrink-0 animate-[pulse_1.2s_ease-in-out_infinite]"
           initial={{ opacity: 0 }}
           animate={{ opacity: 1 }}
           exit={{ opacity: 0 }}
           transition={{ duration: 0.3 }}
         >
-          {/* Dot */}
-          <span className="flex-shrink-0 animate-[pulse_1.2s_ease-in-out_infinite]">
-            <DebugStackframeDot className="w-4 h-4" color={statusColor} />
-          </span>
+          <DebugStackframeDot className="w-4 h-4" color={statusColor} />
+        </motion.span>
 
-          {/* Text */}
-          <span className="pr-1.5 font-normal text-[11px] leading-[16px] normal-case break-words whitespace-normal">
-            {status}
-          </span>
+        {/* Text */}
+        <motion.span
+          key={`text-${status}`}
+          initial={{ opacity: 0, y: -2 }}
+          animate={{ opacity: 1, y: 0 }}
+          exit={{ opacity: 0, y: 2 }}
+          transition={{ duration: 0.3 }}
+          className="pr-1.5 font-normal text-[11px] leading-[16px] normal-case break-words whitespace-normal"
+        >
+          {status}
         </motion.span>
       </AnimatePresence>
     </div>