Bug: Multi-agent LINE routing — secondary account DMs route to default agent
Bug: Multi-agent LINE routing — secondary account DMs route to default agent
I have two agents configured: main (default) and secondary with a separate LINE bot.
Config:
Expected: DMs to secondary LINE bot → agent:secondary:main session
Actual: All DMs route to agent:main:main. Session shows accountId: "secondary" but session key stays agent:main:main. No agent:secondary:main session is ever created.
Gateway log confirms the secondary provider starts: [line] [secondary] starting LINE provider
I traced the source — resolveAgentRoute() logic looks correct (binding match → agentId → sessionKey), but runtime behavior doesn't match. Suspecting session key override downstream or sticky session matching.
Workaround: Using secondary bot for push-only (webhook off).
I have two agents configured: main (default) and secondary with a separate LINE bot.
Config:
Expected: DMs to secondary LINE bot → agent:secondary:main session
Actual: All DMs route to agent:main:main. Session shows accountId: "secondary" but session key stays agent:main:main. No agent:secondary:main session is ever created.
Gateway log confirms the secondary provider starts: [line] [secondary] starting LINE provider
I traced the source — resolveAgentRoute() logic looks correct (binding match → agentId → sessionKey), but runtime behavior doesn't match. Suspecting session key override downstream or sticky session matching.
Workaround: Using secondary bot for push-only (webhook off).
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
83,815Members
Resources
Similar Threads
Was this page helpful?
