Codex stuck on bash task, that finished, but not quited

Resolved 💬 3 comments Opened Nov 1, 2025 by sergx Closed Nov 15, 2025

💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What version of Codex is running?

VSCode extension 0.4.34

What subscription do you have?

Plus

Which model were you using?

gpt-5-codex medium

What platform is your computer?

_No response_

What issue are you seeing?

This step of solving a task is stuck for 5 min+ And did not end untill i did not press stop.

Running npm run test:unit

$ bash -lc 'npm run test:unit'

> frontend@0.0.0 test:unit
> vitest


 DEV  v2.1.9 E:/platform_boilerplate/frontend

 â^\^S tests/unit/formatters.spec.js (4 tests) 24ms
 â^\^S tests/unit/AppAlert.spec.js (2 tests) 15ms

 Test Files  2 passed (2)
      Tests  6 passed (6)
   Start at  07:58:08
   Duration  696ms (transform 45ms, setup 0ms, collect 119ms, tests 39ms, environment 669ms, prepare 131ms)

 PASS  Waiting for file changes...
       press h to show help, press q to quit

What steps can reproduce the bug?

...

What is the expected behavior?

_No response_

Additional information

_No response_

View original on GitHub ↗

3 Comments

github-actions[bot] contributor · 10 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

#5948
#5159
#5849
#5905
#5870

Powered by Codex Action

carboni123 · 9 months ago

try setting "pool":"threads" in vitest config
Here is my vitest.config.ts file for reference

/// <reference types="vitest" />

import { defineConfig, mergeConfig } from "vitest/config";
import viteConfig from "./vite.config";

export default mergeConfig(
  viteConfig,
  defineConfig({
    test: {
      globals: true,
      environment: "jsdom",
      include: ["src/**/*.{test,spec}.{ts,tsx}"],
      exclude: ["e2e/**"],
      setupFiles: ["./vitest.setup.ts"],
      pool: "threads", // avoid fork workers crashing in Node 22 sandbox
    },
    // Remove the plugins array here, as it will inherit from vite.config.ts
    // The resolve alias is also inherited, so you can remove it if identical
  }),
);

etraut-openai contributor · 9 months ago

We recently fixed a bug that I suspect is the cause of this. It affects tools that open a child process and share the stderr/stdout handle with their child. The logic in the CLI was waiting (indefinitely) for these to be closed. We've added a hard timeout to work around this issue. I'm going to close this. If you see similar problems in the future, please open a new bug report and use the recently-added /feedback slash command if you're using the CLI. We're planning to add support for /feedback in the extension soon.