fix(telegram): namespace slash SessionKey by agent#38680
fix(telegram): namespace slash SessionKey by agent#38680obviyus merged 2 commits intoopenclaw:mainfrom
Conversation
Greptile SummaryThis PR fixes a session key namespacing bug in the Telegram native slash command handler. The Key changes:
Observation (no action required): Several other test files ( Confidence Score: 5/5
Last reviewed commit: 2f556c7 |
2f556c7 to
0e037e9
Compare
0e037e9 to
17a527d
Compare
|
Landed via temp rebase onto main.
Thanks @0xtangping! |
(cherry picked from commit bfc36cc)
(cherry picked from commit bfc36cc)
Summary
Telegram native slash commands were storing session metadata under a bare key (
telegram:slash:<id>), which omitted theagent:<agentId>:namespace. This could collide with agent-scoped sessions and lead to duplicate delivery routing.Changes
agent:${route.agentId}:...in native command context.Testing
pnpm exec vitest run src/telegram/bot-native-commands.session-meta.test.ts --config vitest.channels.config.tsFixes #38648