project-router

To route multiple projects over a single IM platform connection, configure your projects in a config.toml file and initialize the routers to share the platform credentials. This setup routes incoming messages to the correct Engine based on per-session bindings.

Per-session binding for multi-project routing works by assigning a specific project to each user session via the /project command. This ensures incoming messages are routed to the correct Engine, with binding persistence surviving restarts to support fallback routing.

Yes, you can use one Feishu bot to serve multiple projects simultaneously by sharing the same IM platform credentials. ProjectRouter maintains a single platform connection and routes incoming messages to the correct Engine based on per-session bindings.

Multi-project routing supports thread-isolation using an optional BaseSessionKeyer and offers button-based selection UI when supported by the platform. If buttons are unsupported, it automatically falls back to text-based project selection.

The best way to switch between projects on a shared bot connection is using the /project command. This workflow allows users to bind and switch between projects dynamically, with router-level binding persistence ensuring configurations survive restarts.

You need to configure multiple projects in config.toml for routing to define the shared platform credentials and initialize the routers. Starting all engines after this setup enables the router to correctly map incoming messages to the appropriate Engine.