Deploy Now

Stars

492

Forks

0

Watchers

0

Developer links

RabiRoute

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.

RabiRoute
RabiRoute
RabiRoute

Benefits

  • One Gateway, Every Channel
  • QQ groups and direct chats via NapCat and OneBot, webhooks, schedules, voice, desktop, and device events all enter through one gateway instead of separate bots per channel.
  • Routes Decide Before Agents
  • Each message Route selects the receiving agent or program, attaches role context, and caps how many recent messages travel with the delivery, keeping agent inputs deliberate.
  • Controlled, Receipted Replies
  • External sends pass through one API that validates targets, quoted messages, and sender identity, then records receipts so every outbound reply can be audited afterwards.
  • Scheduled Agent Work Built-In
  • Role rules trigger agents by interval, time window, daily time, or one-time schedule, or run a configured local script, turning recurring checks into unattended routines.

Features

  • Message Routing Core
  • Receives messages, persists events, matches routing rules, builds agent context, delivers to a handler, and records replies and delivery results end to end.
  • QQ via NapCat OneBot
  • Binds one NapCat instance to each Route with quick, password, or QR login and security confirmation managed inside the Route card itself.
  • Roles, Plans, Memories
  • Each role owns its conversation history plus plan status keys, labels, views, approval behavior, memories, and skills that agents can evolve without a code release.
  • WebGUI and Linux Host
  • A Node.js 20 Host runs the Manager and browser WebGUI on Linux from source; Windows adds tray, screenshots, and global hotkeys on the desktop path.
  • Experimental Device Clients
  • RabiSpeech voice, RabiLink phone and glasses clients, wearables, and remote computer clients expose terminals, files, windows, and screenshots as experimental integrations.

Apps Similar to RabiRoute