RabiRoute

!RabiRoute mascot connecting communication, smart devices, and desktop automation to Agents

Let Agents connect everything around us.

Connect communication platforms, smart devices, and desktop workflows to the right Agent.

RabiRoute is a self-hosted message gateway and policy router for AI agents. Connect chats, desktop events and smart devices to the Agent you already use, with role context, scheduled tasks and recorded results.

RabiRoute connects and routes. Your Agent owns the model, tools and execution.

Overview · Get started · Architecture · Docs

What it connects

flowchart LR
    C["Chat<br/>QQ · WeChat · WeCom · Feishu"] --> R["RabiRoute<br/>Routes + role context"]
    T["Schedules<br/>Webhooks"] --> R
    I["Desktop<br/>Device events"] --> R
    R --> A["Your Agent<br/>Codex · DSH · WorkBuddy"]
    A --> O["Reply or action<br/>Sending rules + receipts"]
    classDef input fill:#e8f2ff,stroke:#4777b7,color:#162b48
    classDef router fill:#dcf5ed,stroke:#218468,color:#113d31
    classDef agent fill:#f0e7fa,stroke:#8254a8,color:#372044
    classDef output fill:#fff0df,stroke:#bf7b30,color:#51351c
    class C,T,I input
    class R router
    class A agent
    class O output

QQ and Codex Desktop have verified core paths. Other adapters and physical-device integrations have their own maturity and setup requirements; see integration status.

| Your goal | Start here | | --- | --- | | Ask an Agent from QQ, WeChat, WeCom or Feishu | Choose a message input | | Run a task on a schedule or webhook | First Route | | Keep role context, plans, memories and skills together | Roles and rules | | Send selected text, screenshots, voice or device events | Desktop and client guides |

From message to result

A Route selects the role, Agent task, workspace and reply rules. The diagram shows a chat-triggered run; schedules use their configured destination. Sending replies remains a separate, recorded action.

sequenceDiagram
    participant S as Chat or device
    participant R as RabiRoute
    participant A as Existing Agent task
    S->>R: Message
    R->>R: Match Route and attach recent context
    R->>A: Deliver to selected task and workspace
    A-->>R: Result or completion callback
    R->>R: Apply sending rules and record receipt
    R-->>S: Reply when the sending rule allows

Get started

| What you need | Entry point | | --- | --- | | Main application — Manager, WebGUI and Windows desktop | Windows installation/build guide · Source startup | | Another computer connected to your main application | Connect a computer | | Linux browser interface | Linux Host |

Connect another computer from the main app: generate an installation prompt and let an Agent on the target computer execute it. The prompt downloads and verifies a lightweight connector from your Manager; no separate GitHub installer is needed. The target needs Node.js 22.13+, npm and access to the Manager address. See PC onboarding for platform requirements.

flowchart LR
    P["Main app<br/>Copy installation prompt"] --> T["Target computer<br/>Execute the prompt"]
    T --> V["Verify signature<br/>Install connector"]
    V --> C["Computer connects<br/>Check version and digest"]

1. Start the main application and open WebGUI from the tray or the Host-provided address.
2. Choose a role. Add a message Route and bind its Agent, existing task and workspace.
3. Use Channel check → Delivery test. Confirm the original Agent conversation receives the message and the delivery record shows the result.

git clone https://github.com/vb2250158/RabiRoute.git
cd RabiRoute
bash Start-RabiRoute-FromSource.sh
npm run status:linux -- --json

Integration status

The repository version is 0.4.2.

| Area | Current scope | | --- | --- | | QQ / NapCat / OneBot + Codex Desktop | Core delivery path verified | | Routes, schedules, WebGUI, role plans and memory | Core paths verified | | Windows desktop | Core implemented; system interactions need device acceptance | | Personal WeChat (Weixin), WeCom and Feishu | Prototype / experimental; real-account acceptance varies | | DSH, WorkBuddy, Grok Bot and remote computer clients | Experimental; validate each backend and target computer | | Linux Host, RabiSpeech, phones, glasses, wearables and Home Assistant | Experimental; model, network and hardware acceptance is separate |

Full capability matrix · Changes and migrations

Architecture

The Windows package uses one Host to own Manager and the desktop surface. Manager owns routing and business state; plugins provide adapters and services. Agent tasks and optional speech/device services keep their own lifecycles.

flowchart TB
    H["Windows Host"] --> M["Manager"]
    H --> W["Desktop / tray"]
    U["Browser / WebGUI"] <--> M
    W <--> M
    M --> K["Plugin Kernel"]
    K --> P["Message adapters<br/>Routes · plans · memory"]
    P <--> D[("Private local data")]
    P <--> A["External Agent tasks"]
    P <--> S["Optional speech<br/>and device services"]

Documentation

| I want to… | Guide | | --- | --- | | Complete the first task | First Route · User guide | | Check status or troubleshoot | Interface and status · Operations | | Connect voice, devices or another computer | Client apps · RabiSpeech · Home devices · PC onboarding | | Integrate or extend RabiRoute | API discovery · Architecture · Function map | | Browse all documentation | Documentation index · Configuration |

License

MIT License.