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

Activity

1. sergx

   added

   bugSomething isn't workingSomething isn't working

   on Nov 1, 2025
2. github-actions

   added

   extensionIssues related to the VS Code extensionIssues related to the VS Code extension

   on Nov 1, 2025
3. github-actions commented on Nov 1, 2025

   

   github-actionsBot

   on Nov 1, 2025 – with GitHub Actions

   Contributor

   More actions

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

   • Unified exec never detaches from long-running streaming commands (e.g. docker compose logs --follow) #5948
   • Codex stuck at process #5159
   • Hang and no response after 15min #5849
   • Unable to interrupt when Codex stuck on terminal prompt #5905
   • Jobs stuck for hours; Stop often ineffective and blocks further prompts #5870

   Powered by Codex Action
4. carboni123 commented on Nov 12, 2025

   

   carboni123

   on Nov 12, 2025

   More actions

   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
     }),
   );
5. etraut-openai

   added

   tool-callsIssues related to tool callingIssues related to tool calling

   and removed

   extensionIssues related to the VS Code extensionIssues related to the VS Code extension

   on Nov 15, 2025
6. etraut-openai commented on Nov 15, 2025

   

   etraut-openai

   on Nov 15, 2025

   Contributor

   More actions

   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.
7. etraut-openai

   closed this as completedon Nov 15, 2025