Which agent should answer a question that just arrived in your QQ group, and how much of the conversation should it see? RabiRoute is the self-hosted message gateway that answers those routing questions before your agent ever wakes up. Chat messages from QQ groups and direct chats (through NapCat and OneBot), webhooks, schedules, voice, desktop selections, and device events all arrive at one gateway, and message Routes decide which agent or local program receives each one. Every role keeps its own message history plus references to plans, memories, and skills, while each Route limits how many recent messages travel with a delivery. Roles can also fire agents on interval, time-window, daily, or one-time schedules, or run a configured local script, so recurring checks and reports happen without anyone typing a prompt. Replies to QQ, RabiLink, and other channels leave through a single sending API that validates targets, quoted messages, and sender identity, then records receipts for everything delivered. The Windows desktop side adds selected-text actions, screenshots, and annotations; speech, phone, glasses, wearable, and remote-computer clients connect as experimental integrations, and the Linux Host serves the Manager and browser WebGUI from a Node.js process. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.