dsh-mobile-remote

LIMITATIONS

Known limitations

- **No voice recognition**: voice messages always get「无法识别语音消息」(not downloaded/transcribed/stored) — a deliberate design decision - **No multimodal pipeline**: images/files are only saved to disk with a path hint for the model; the plugin does not parse content (pair with a vision tool such as `vision_analyze`) - **No scheduled tasks**: no cron-style "do X every day" - **No remote approval buttons**: full-permission mode means no human-in-the-loop confirmations and no approve/reject interaction in WeChat; `strict` mode is a reserved escape hatch (approval flow not implemented) - **Depends on an undocumented protocol**: iLink may drift and break features; misuse risks a ban - **Single account binding**: one credential set per dsh instance; multiple WeChat accounts need multiple profile instances (no built-in multi-instance management) - **No content-level file dedup**: resending the same file in different messages lands duplicate copies (only crash replays of the same message are deduplicated) - **Chinese-only commands and copy**: slash commands, help text and prompts are Chinese; no English/i18n - **No graphical settings panel**: all configuration is via environment variables / cordis patch (the login page only offers QR scan, a status bar and the health endpoint) - **Requirements**: Node ≥ 22.12, a dsh web profile, and a WeChat account that can scan-bind an iLink bot