Linux: repeated keyring unlock prompts during subagent spawn can stall session progress

What version of Codex CLI is running?

codex-cli 0.98.0

What subscription do you have?

Pro

Which model were you using?

gpt-5.3-codex

What platform is your computer?

Linux 6.18.9-2-cachyos x86_64 unkown

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

Ghostty

What issue are you seeing?

On Linux, Codex CLI intermittently stalls during an active session when subagents are used, and I get a keyring unlock prompt (KeePassXC is my Secret Service backend). The stall lasts until I unlock the keyring, then the session continues. This is not deterministic, but in long sessions it happens multiple times (current session had 3+).

What steps can reproduce the bug?

Codex cli causes a system keyring unlock prompt reliably for me during MCP server initialization for the _first ever session in a new folder_.

I do not have a reliable reproduction for subagents causing system keyring unlock prompts. But details I can think of are:

• session used --yolo
• session was started in folder A, but work was being done in folder B. A session was never started in folder B, ever.
• long running session with frequent subagent use. subagent spawns do not reliably cause system keyring unlock prompts.

What is the expected behavior?

• no system keyring unlock prompts in the middle of sessions
• ideally just one system keyring unlock prompt for the first time a unique mcp is initialized.

Additional information

_No response_