You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix: cache PostableObjects in history with real message ID
PostableObject posts (e.g., Plan) now cached in thread/channel message
history using the real adapter-returned message ID and fallback text.
This is an intentional divergence from upstream TS, which skips history
for PostableObjects (a gap, not a design choice — regular posts and
streaming posts both cache, only PostableObjects were missed).
Changes:
- post_postable_object() now returns the RawMessage
- Thread/Channel _handle_postable_object returns RawMessage
- History append uses raw.id (not synthetic "postable-obj" constant)
- Documented as intentional divergence in UPSTREAM_SYNC.md non-parity
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: docs/UPSTREAM_SYNC.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -392,6 +392,8 @@ stay explicit instead of being rediscovered in code review.
392
392
|`ast_to_plain_text`| Joins blocks with `\n`| Concatenates directly | More readable output |
393
393
|`renderPostable` on unknown input | Returns `str(message)`| Throws `Error`| More resilient |
394
394
| Chat resolver | 3-level: explicit → ContextVar → global | Process-global singleton | See [DECISIONS.md](DECISIONS.md#why-3-level-chat-resolver)|
395
+
| PostableObject history | Cached in message history with real message ID | Not cached (skips history) | Upstream gap — posted messages should appear in thread/channel history |
396
+
| Teams `msteams` transport key | Stripped from action values | Not stripped | Upstream gap — SDK-injected metadata should not leak to handlers |
0 commit comments