Josh Lehman 9d50ebad7d feat(routing): route replies to originating channel ...

Implement reply routing based on OriginatingChannel/OriginatingTo fields.
This ensures replies go back to the provider where the message originated
instead of using the session's lastChannel.

Changes:
- Add OriginatingChannel/OriginatingTo fields to MsgContext (templating.ts)
- Add originatingChannel/originatingTo fields to FollowupRun (queue.ts)
- Create route-reply.ts with provider-agnostic router
- Update all providers (Telegram, Slack, Discord, Signal, iMessage)
  to pass originating channel info
- Update reply.ts to pass originating channel to followupRun
- Update followup-runner.ts to use route-reply for originating channels

This addresses the issue where messages from one provider (e.g., Slack)
would receive replies on a different provider (e.g., Telegram) because
the queue used the last active dispatcher instead of the originating one.

2026-01-07 04:51:33 +00:00

..

index.ts

feat: unify poll support

2026-01-06 04:51:05 +00:00

monitor.test.ts

feat(commands): unify chat commands (#275)

2026-01-06 20:17:56 +00:00

monitor.tool-result.test.ts

feat(commands): unify chat commands (#275)

2026-01-06 20:17:56 +00:00

monitor.ts

feat(routing): route replies to originating channel

2026-01-07 04:51:33 +00:00

probe.ts

feat(commands): unify chat commands (#275)

2026-01-06 20:17:56 +00:00

send.test.ts

feat: unify provider reaction tools

2026-01-07 04:16:39 +01:00

send.ts

feat: unify provider reaction tools

2026-01-07 04:16:39 +01:00

token.ts

fix: apply biome formatting

2025-12-26 14:38:37 +01:00