fix(telegram): distill native metadata session key · openclaw/openclaw@c57960b
obviyus
·
2026-04-28
·
via Recent Commits to openclaw:main
| Original file line number | Diff line number | Diff line change |
|---|
@@ -992,13 +992,10 @@ export const registerTelegramNativeCommands = ({
|
992 | 992 | OriginatingChannel: "telegram" as const, |
993 | 993 | OriginatingTo: originatingTo, |
994 | 994 | }); |
995 | | -const sessionMetaKey = |
996 | | -ctxPayload.CommandTargetSessionKey?.trim() || ctxPayload.SessionKey || route.sessionKey; |
997 | | - |
998 | 995 | await nativeCommandRuntime.recordInboundSessionMetaSafe({ |
999 | 996 | cfg: executionCfg, |
1000 | 997 | agentId: route.agentId, |
1001 | | -sessionKey: sessionMetaKey, |
| 998 | +sessionKey: commandTargetSessionKey, |
1002 | 999 | ctx: ctxPayload, |
1003 | 1000 | onError: (err) => |
1004 | 1001 | runtime.error?.(danger(`telegram slash: failed updating session meta: ${String(err)}`)), |
|
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。
