#Hi folks, been working on the Telegram

1 messages · Page 1 of 1 (latest)

brazen jacinth
#

I create thread for reporting test result.
I will test once and report result here. ❤️

brazen jacinth
#

@onyx panther Tested PR #79649 end-to-end on a real Mac gateway (single-bot DM with @GenieSpeedyBot). Built and ran the PR head 1466e4785c against the live gateway.

Repro steps in DM:

  1. Sent old marker: Marker A — what was the deployment outcome? (msg 120, bot replied)
  2. Sent unrelated chatter (msg 123)
  3. Sent unrelated chatter 1 (msg 125)
  4. Sent unrelated chatter 2 (msg 127)
  5. Replied to msg 120 with quick reminder of A (msg 129)

Captured prompt body for msg 129 contains both new context blocks:

Nearby reply target window (untrusted, chronological, around replied-to message):
  #112 ... #115 ... #120 [reply target] ... #123 ... #125

Current local chat window (untrusted, chronological, before current message):
  #105 ... #106 ... #110 ... #112 ... #115 ... #120 ... #123 ... #125 ... #127

Bot response correctly reflected both contexts: recalled A = deployment succeeded (from the reply-target window) AND surfaced earlier active-chat detail about the daily-9PM feed setup (from the live chat window). Pre-fix, only the reply ancestry would have reached the model. Looks good — works exactly as advertised.

#

👍