Pasted terminal output is Markdown-escaped before reaching the Codex model

What version of the Codex App are you using (From “About Codex” dialog)?

26.903.71938 (build 8576)

What subscription do you have?

Plus

What platform is your computer?

macOS, Apple Silicon

What issue are you seeing?

Examples seen by the model:
#!/bin/sh became \#!/bin/sh
$LOG_DIR became $LOG\_DIR
--delete-after became \--delete-after
.log became \.log
user@host became user\@host

Independent checks on the source file confirmed none of those backslashes
actually existed.

What steps can reproduce the bug?

1. Copy terminal output from cat containing a shell script.
2. Paste it as plaintext into a Codex task.
3. Send the message.
4. Codex interprets inserted escape characters as literal script contents.

What is the expected behavior?

Expected:
Terminal/code text should reach the model byte-for-byte, or the model should
receive metadata indicating that backslashes were introduced solely for
Markdown presentation.

Actual:
The model treated presentation-layer escaping as file content and incorrectly
reported that the valid script was malformed.

Impact:
This can cause false code reviews and potentially harmful recommendations to
modify valid shell scripts.

Additional information

No response

Reproduce the issue by pasting the listed shell examples into a Codex task, then trace the path from terminal paste through Markdown handling to the model message. Done means shell text reaches the model without presentation-only backslashes, or the message clearly distinguishes those escapes from file content.