fix: type message action routing fallbacks

This commit is contained in:
FullerStackDev
2026-05-02 17:41:51 -06:00
parent a7b1aa44f2
commit 632ee6adc5
2 changed files with 4 additions and 2 deletions

View File

@@ -104,7 +104,8 @@ const discordMessageActions = {
ctx: Parameters<NonNullable<ChannelMessageActionAdapter["resolveExecutionMode"]>>[0],
) =>
resolveRuntimeDiscordMessageActions()?.resolveExecutionMode?.(ctx) ??
discordMessageActionsImpl.resolveExecutionMode?.(ctx),
discordMessageActionsImpl.resolveExecutionMode?.(ctx) ??
"local",
describeMessageTool: (
ctx: Parameters<NonNullable<ChannelMessageActionAdapter["describeMessageTool"]>>[0],
): ChannelMessageToolDiscovery | null =>

View File

@@ -222,7 +222,8 @@ async function sendTelegramOutbound(params: {
const telegramMessageActions: ChannelMessageActionAdapter = {
resolveExecutionMode: (ctx) =>
getOptionalTelegramRuntime()?.channel?.telegram?.messageActions?.resolveExecutionMode?.(ctx) ??
telegramMessageActionsImpl.resolveExecutionMode?.(ctx),
telegramMessageActionsImpl.resolveExecutionMode?.(ctx) ??
"gateway",
describeMessageTool: (ctx) =>
getOptionalTelegramRuntime()?.channel?.telegram?.messageActions?.describeMessageTool?.(ctx) ??
telegramMessageActionsImpl.describeMessageTool?.(ctx) ??