False positive

What version of Codex CLI is running?

...

What subscription do you have?

PRO

Which model were you using?

gpt-5.6-sol

What platform is your computer?

linux

What terminal emulator and version are you using (if applicable)?

Konsole

Codex doctor report

posting my paths, no fucking way

What issue are you seeing?

i am doing some graphics programming in my own game framework and asked it to review my modkit-mcp server and it gave me this.

A concrete lifecycle fault has emerged in the new shutdown logic: closing MCP stdin does not
  terminate the server because the keepalive timer remains active, so normal client
  disconnects can leave both the MCP process and launched apps behind. I’m reproducing that
  and checking the session/port behavior with real built examples now.

• Ran timeout 3s node ./dist/index.js </dev/null; code=$?; printf 'eof_exit_code=%s\n'
  │ "$code"; printf '%s\n' '--- lock versions ---'; npm ls @modelcontextprotocol/sdk ws hono
  │ @hono/node-server express-rate-limit fast-uri path-to-regexp qs ip-address --all
  └ [modkit-mcp] Server started on stdio transport
    [modkit-mcp] Shutting down (SIGTERM)
    … +17 lines (ctrl + t to view transcript)
    └── ws@8.20.0


• Ran node --input-type=module -e 'import {start,getLogs,stopAll} from "./dist/tools/
  │ start.js"; const port=19876; try { console.log("FIRST", await
  │ start({target:"01_hello",remotePort:port,waitReady:5})); console.log("SECOND", await
  │ … +2 lines
  └ [modkit-mcp] start: /home/timelord/projects/modkit_workspace/modkit/build-linux/
    bin/01_hello  (session=modkit:01_hello:1783828439019:1, port=19876, waitReady=5s)
    … +18 lines (ctrl + t to view transcript)



• Ran node --input-type=module -e 'import {start,getLogs,stopAll} from "./dist/tools/
  │ start.js"; const port=19876, env={MK_RENDERER:"noop"}; try { console.log("FIRST", await
  │ start({target:"01_hello",remotePort:port,waitReady:5,env})); console.log("SECOND", await
  │ … +3 lines
  └ [modkit-mcp] start: /home/timelord/projects/modkit_workspace/modkit/build-linux/
    bin/01_hello  (session=modkit:01_hello:1783828451388:1, port=19876, waitReady=5s)
    … +18 lines (ctrl + t to view transcript)



ⓘ This content can't be shown
  We take extra caution with cybersecurity requests. If you’re a security professional, you
  may be able to apply for Trusted Access.
  Trusted Access: https://openai.com/form/enterprise-trusted-access-for-cyber/
  Learn more: https://help.openai.com/en/articles/20001326

• Feedback uploaded. Please open an issue using the following URL:

  https://github.com/openai/codex/issues/new?template=3-cli.yml&steps=Uploaded%20thread:%20019f52e6-473e-7293-9040-6da8a924386a

  Or mention your thread ID 019f52e6-473e-7293-9040-6da8a924386a in an existing issue.

I just want to say, this is ridiculous.

What steps can reproduce the bug?

Uploaded thread: 019f52e6-473e-7293-9040-6da8a924386a

What is the expected behavior?

_No response_

Additional information

_No response_