Copilot CLI Feishu WeChat Bridge

What It Solves

When you are away from your machine, GitHub Copilot CLI is still mostly tied to a local terminal. This skill connects Copilot CLI to Feishu, DingTalk, or WeChat so that a phone message can start a CLI session and receive text, files, or images back in chat. It is useful for continuing a task from a mobile device without opening a laptop.

How It Works

• Two bridge tools: cc-connect targets Feishu/Lark, Slack, DingTalk, and Telegram; wechat-acp targets WeChat and is a community, hook-based bridge.
• Official messaging channel: the Feishu path uses an enterprise app, im:message permissions, WebSocket long connections, and event subscriptions to receive messages and return results.
• Copilot authentication: it supports interactive login, environment variables, GitHub CLI tokens, secret managers, or wrapper scripts. Use the real copilot binary rather than the VS Code shim to avoid authentication failures.
• Context continuity: because each IM message may start an isolated session, the skill can use a history-sync pattern to persist chat history in cc-connect session JSON and rebuild .github/copilot-instructions.md on message.sent, seeding the next session.
• File delivery: cc-connect send can return files or images to chat, and you can instruct Copilot to auto-send them from .github/copilot-instructions.md.
• Long-running service: it can be persisted as a macOS LaunchAgent, Windows Scheduled Task, or Linux systemd unit.

Boundaries

It does not share conversation memory between VS Code Copilot and IM Copilot, but they can share the same project filesystem. For remote runs, --yolo is recommended to reduce confirmation blocking. Use a separate work_dir or filter_external_sessions to avoid session conflicts. The WeChat path relies on hooks, has weaker file and image support than Feishu, and may need extra attention to Chinese path encoding, permissions, and process persistence.