error message in a middle of a session: the encrypted content could not be verified

Resolved 💬 2 comments Opened Dec 16, 2025 by vkryukov Closed Dec 16, 2025

What version of Codex is running?

0.73.0

What subscription do you have?

Pro

Which model were you using?

gpt-5.2 medium

What platform is your computer?

Linux 6.17.9-arch1-1 x86_64 unknown

What issue are you seeing?

In the middle of a session, a red error message appeared, and the execution stopped:

``› discovered a bug when running a command (e.g., /rerun gemini`): the command name and the user input appears additionally at the very top of the chat. That duplicated
entry disappears again when the message is finalized, but it is still visible while the streaming is performed. Your tasks is to identify and solve this issue.

• Updated Plan
└ Investigate how /rerun is rendered during streaming, then adjust LiveView message streaming so optimistic/placeholder entries don’t appear as a duplicate at the top.
□ Locate rerun command handling
□ Reproduce streaming duplication path
□ Implement rendering/stream fix
□ Run quality and precommit checks

• Explored
└ Search \\/rerun|rerun in lib
Search handle_event\(\"rerun\"|:rerun|Rerun in lib
Search continue_message\(|create_message\( in lib
Search phx-update=\"stream\"|stream\(socket, :messages in lib
Read chat_live.ex
Search defp handle_message|def handle_message in chat_live.ex
Read chat_live.ex
Search defp reply_chat\( in chat_live.ex
Read chat_live.ex
List agents
Read rerun.ex, slash_commands.ex
Search def reply_chat\b in llm
Search reply_chat\( in llm_chat
List llm_chat
Read llm.ex, chat.ex, execute_agent.ex, reply_chat.ex
Search defp user_text\( in chat_live.ex
Read chat_live.ex
Search streaming_(text|html|message_id) in chat_live.ex
Read chat_live.ex
Search chat_mode in chat_live.ex
Read chat_live.ex, message.ex

■ {
"error": {
"message": "The encrypted content gAAA...KA== could not be verified.",
"type": "invalid_request_error",
"param": null,
"code": "invalid_encrypted_content"
}
}


### What steps can reproduce the bug?

Uploaded thread: 019b288d-8a2c-76a3-a237-419d0c15e88b

### What is the expected behavior?

_No response_

### Additional information

_No response_

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗