Home Extensions · 03 — Connector

Connectors

Four doors into the same agent: two chat platforms, one personal account, one microphone. The answer arrives where the question already was.

Four connectors Started by the bridge Python · Node One IM helper set v1.0.0

What a connector is

The answer arrives where the question already was.

A connector is a long-lived client that Quanta's bridge starts for you. It receives a message, turns it into an agent turn, and sends the answer back into the same thread — with de-duplication, chunking and attachment download shared across all of them.

None of them is a daemon you launch by hand. Quanta holds the credentials, starts the client, and routes each message as if it had been typed into the window — same memory, same pages, same tools.

Long connection or gateway

Feishu and QQ hold a socket open, so nothing needs a public callback URL, a tunnel or a server of your own.

Reply inside the window

QQ only accepts a passive reply for a while after the message. The connector tracks that clock; the agent does not get to be late.

Local stays local

WeChat and voice run on your machine against your own account or microphone. Nothing is relayed through a Quanta server.

Skill A written procedure plus a script. Loaded when its description matches the request. SKILL.md
Plugin Code inside the agent runtime. Changes how a run behaves rather than what it can call. dsh ACP
Connector A door into the agent from somewhere else — a chat app, a microphone. bridge
MCP Server A separate process exposing tools over stdio JSON-RPC. stdio
The four

Three inboxes and a microphone.

Each demo below is the same shape: a message comes in, a turn runs, an answer goes back. What changes is the chrome and the rules.

CONNECTOR-01feishu

A long connection, no callback URL.

A Feishu self-built app opens a WebSocket long connection and receives every message on it; replies go back through the OpenAPI. Quanta supplies the app_id and app_secret, and each message becomes an agent turn.

  • Self-built app. Not a marketplace app — your tenant, your bot, your permissions.
  • No public address. The connection runs outbound, so a laptop behind a router works.
  • Needs lark-oapi. One Python dependency. Attachments are downloaded and filed like any other input.
Download · zip quanta-connector-feishu.zip
feishu · websocket → agent → openapi simulated
Q
Quanta
feishu · self-built app
connected
dedupe · chunk · attachments
Press send: the message arrives on the long connection, runs as a turn, and comes back through the OpenAPI. Long replies are chunked; a file would be downloaded first.
CONNECTOR-02qq

Official bot, passive replies.

QQ's official bot gateway is a WebSocket too, but it answers with a rule: a reply is only valid for a short window after the message, and it must carry that message's id. The connector keeps the clock and the id, so a slow turn still lands.

  • Passive, not push. The bot may not message first. A reply is bound to one incoming message.
  • msg_id bound. The id travels with the turn so the answer has somewhere to go.
  • Needs websocket-client. No framework, no SDK — one small dependency and a socket.
Download · zip quanta-connector-qq.zip
qq · official bot gateway simulated
Q
Quanta · QQ bot
gateway · passive reply
connected
passive · 5:00
The reply is sent as a passive answer inside the window, with the incoming message's id — the reason the footer shows a clock instead of a chat box.
CONNECTOR-03wechat

Your own account, your own machine.

The WeChat connector bridges a personal account to the agent on the same computer. It is not a platform API, and it is not pretending to be one: the client runs locally, keeps the session on your disk, and needs an npm install before it starts.

  • Local session. The login lives on your machine, not in a service. Sign out and it is gone.
  • npm install first. It is the only connector here with a Node dependency tree.
  • Use it on your own account. A personal account is not an enterprise tenant. Keep it to yourself, on your own machine.
Download · zip quanta-connector-wechat.zip
wechat · local bridge · personal account simulated
Q
Quanta
wechat · local bridge
online
npm start · session on disk
A personal chat, answered by the same agent. Files sent to it are downloaded, filed, and readable in the next turn.
CONNECTOR-04voice · rhema

Voice in, voice out, one sidecar.

Rhema is a streaming VAD / ASR / TTS sidecar. It decides when you have started and stopped speaking, transcribes while you talk, and speaks the answer back — the device is not asked to type.

  • Streaming, not a file. VAD cuts the utterance; the transcript grows while you speak.
  • MLX on Apple silicon. The ASR path wants mlx-audio and huggingface_hub; on other machines it falls back.
  • Interruptible. Speaking over the answer stops the voice and keeps the transcript — the text is the record.
Download · zip quanta-connector-voice.zip
rhema · vad → asr → agent → tts simulated
waiting for a voice…
▶ rhema · tts
3.4s
interruptible · transcript kept
Speak: the transcript is written while the waveform moves, then the answer is read back. The simulation stops short of audio — the shape is the point.
Setup

Started by the bridge, not by you.

A connector is a module Quanta starts when the app starts. You choose the door and give it credentials; the bridge does the launching.

  1. 01Unzip and install the one dependency. lark-oapi for Feishu, websocket-client for QQ, npm install for WeChat, mlx-audio for voice on Apple silicon.
  2. 02Give it credentials. Feishu app_id and app_secret, a QQ bot token, or a WeChat sign-in on your own machine.
  3. 03Let the bridge start it. The connection state shows in the log. If the socket dies, the bridge reopens it — you do not babysit it.
$ pip install lark-oapi websocket-client
$ npm install --prefix connectors/wechat
$ pip install mlx-audio huggingface_hub

# started by Quanta's bridge, not by hand:
feishu  · ws open · tenant xyc
qq      · gateway ready · bot 1029…
wechat  · session restored
voice   · vad · asr · tts ready

Credentials live where Quanta keeps its settings, not in the connector folder. The connectors are replaceable; the account is not.

Next

Nine small instruments on one bench.