English | 中文 Stop babysitting your local AI agents. No new mobile app required; receive timely, secure notifications through existing channels Zero-intrusion setup: no hooks, no skills, no MCP, no project changes; scan a QR code and start using it in one step Agents run on your local computer, so you can step away while WeChat / Telegram keep you synced on key progress Permission approvals, clarifying questions, and…
Stop babysitting local AI agents. Just notifications, approve, and resume your Codex,Pi,Grok, or Claude code sessions anywhere. 0-Intrusion mobile control bridge via Telegram/微信/飞书. No hooks, no skills, no MCP.
See the full command reference at docs/commands.md. This README keeps only the core paths.
WeChat: quote-to-route
Lucarne pushes agent progress to WeChat.
Quote a notification and reply; Lucarne automatically restores the matching agent session.
Continue the conversation with the original context attached.
If rate limits delay pushes, send /latest or /l to clear the backlog and deliver only the latest notification round per workspace (no help menu reply; does not replay the full queue).
WeChat quote routing uses two strategies: it prefers message_id, then falls back to a quoted-text hash.
Telegram: mobile multi-agent console
Telegram needs Topics/thread mode for the entry chat. A private chat with the bot can use the bot’s own topic mode (Bot API 9.4+ reports this as has_topics_enabled from getMe); use that private chat ID as entry_chat_id. A forum supergroup also works, but is not required.
Send /panel in the entry chat.
Tap New or send /aN to create an agent workspace.
Enter the workspace topic and assign tasks to agents like a normal chat.
When an agent asks for permission, tap [Approve] / [Deny].
Send /status to inspect state, /interrupt to stop work, or /fork to branch a session.
Telegram workspaces map to Forum Topics. One project gets one topic; one topic can bind one live agent session.
评论