Codex Desktop: ::archive directive is rendered as text instead of archiving the thread

Summary

In Codex Desktop, the assistant can emit the documented archive directive after an explicit user request, but the directive is rendered as plain chat text instead of archiving the current thread.

What happened

1. User explicitly asked to archive/end the current thread.
2. Assistant responded with a final message containing:

::archive{reason="Things Cloud / Iskra bridge Wave 1-6 rollout completed and user requested archiving"}

1. The directive appeared in the conversation as visible text.
2. The thread remained open / unarchived.

Expected behavior

When the assistant emits a valid ::archive{...} directive after an explicit user request, Codex Desktop should execute it and archive the current thread.

Actual behavior

The directive is displayed as text in the conversation and no archive action happens.

Environment

• Product: Codex Desktop
• OS: macOS
• Date observed: 2026-06-08
• Surface: local desktop thread

Impact

This makes the documented archive directive unusable for the “finish and archive this thread” workflow. The assistant cannot complete a user-requested archive action even when the user explicitly asks for it.

Notes

I found related issues about archive/session handling and a CLI /archive request, but not this exact Desktop directive execution failure.