Issue Station
Sign In
Tools hereToolbox

codex - 💡(How to fix) Fix Codex Desktop transcript shows internal XML-like context/control blocks

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Codex Desktop is showing internal structured/context messages directly in the visible chat transcript. These appear as XML-like blocks such as:

<command-name>/exit</command-name>
<command-message>exit</command-message>
<command-args></command-args>

and:

<local-command-stdout>See ya!</local-command-stdout>

It also surfaced larger internal context sections such as workspace instructions and environment context in XML-like wrappers.

Root Cause

Codex Desktop is showing internal structured/context messages directly in the visible chat transcript. These appear as XML-like blocks such as:

<command-name>/exit</command-name>
<command-message>exit</command-message>
<command-args></command-args>

and:

<local-command-stdout>See ya!</local-command-stdout>

It also surfaced larger internal context sections such as workspace instructions and environment context in XML-like wrappers.

Code Example

<command-name>/exit</command-name>
<command-message>exit</command-message>
<command-args></command-args>

---

<local-command-stdout>See ya!</local-command-stdout>
RAW_BUFFERClick to expand / collapse

Summary

Codex Desktop is showing internal structured/context messages directly in the visible chat transcript. These appear as XML-like blocks such as:

<command-name>/exit</command-name>
<command-message>exit</command-message>
<command-args></command-args>

and:

<local-command-stdout>See ya!</local-command-stdout>

It also surfaced larger internal context sections such as workspace instructions and environment context in XML-like wrappers.

Expected behavior

Internal control/context messages should not be visible to the end user in the normal chat transcript. If some diagnostic metadata is needed, it should be hidden behind a debug/verbose view rather than interleaved with the conversation.

Actual behavior

The XML-like control/context blocks are rendered inline in the user-visible conversation, creating noise and making it unclear what is user-facing conversation vs assistant/runtime metadata.

Impact

This is confusing and disruptive during normal use. The user has to mentally filter out internal protocol messages that are not actionable and were not intentionally requested.

Environment

  • App: Codex Desktop
  • Platform: macOS
  • Observed in a normal conversation after exiting an agent/session with /exit

Notes

The examples above are sanitized; no private paths or secrets are included. The issue appears to be transcript/rendering leakage rather than a model behavior problem.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

Internal control/context messages should not be visible to the end user in the normal chat transcript. If some diagnostic metadata is needed, it should be hidden behind a debug/verbose view rather than interleaved with the conversation.

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING