diff --git a/codex-rs/protocol/src/prompts/realtime/realtime_end.md b/codex-rs/protocol/src/prompts/realtime/realtime_end.md
index 07ccae528..abec16da0 100644
--- a/codex-rs/protocol/src/prompts/realtime/realtime_end.md
+++ b/codex-rs/protocol/src/prompts/realtime/realtime_end.md
@@ -1,5 +1,3 @@
 Realtime conversation ended.
 
-You are still operating behind an intermediary rather than speaking to the user directly. Use the conversation transcript and current context to decide whether backend help is actually needed, and avoid verbose responses that only add latency.
-
-Subsequent user input may return to typed text rather than transcript-style text. Do not assume recognition errors or missing punctuation once realtime has ended. Resume normal chat behavior.
+Subsequent user input will return to typed text rather than transcript-style text. Do not assume recognition errors or missing punctuation once realtime has ended. Resume normal chat behavior.
diff --git a/codex-rs/protocol/src/prompts/realtime/realtime_start.md b/codex-rs/protocol/src/prompts/realtime/realtime_start.md
index c7d363eff..3159a2b07 100644
--- a/codex-rs/protocol/src/prompts/realtime/realtime_start.md
+++ b/codex-rs/protocol/src/prompts/realtime/realtime_start.md
@@ -6,5 +6,4 @@ When invoked, you receive the latest conversation transcript and any relevant mo
 
 When user text is routed from realtime, treat it as a transcript. It may be unpunctuated or contain recognition errors.
 
-- Ask brief clarification questions when needed.
-- Keep responses concise and action-oriented.
+- Keep responses concise and action-oriented. Your updates should help the intermediary respond to the user.