Telegram/Slack bridge for local Codex agents
Running local Codex agents via Telegram is a clever hack for mobile coding sessions.
Run Cursor Cloud Agents from Telegram
Mobile access to Cursor agents is convenient, but it's a thin wrapper around existing proprietary API.
Remote developers, async teams, Cursor users who want mobile/chat-based agent control.
Cursor · Continue · GitHub CLI
The idea is simple: sometimes I want to start an agent run, reply to it, or check what changed without opening my laptop. With cursor-tg, I can talk to Cursor agents in Telegram, track their progress, view generated diffs/PRs, and handle simple review actions from chat.
I made this mainly for remote/asynchronous development workflows, where I want quick access to my coding agent while away from my desk.
It is really exciting to be finally be able to (help agent) code anywhere!
Running local Codex agents via Telegram is a clever hack for mobile coding sessions.
Cursor agent control panel, but Cursor.com UI already handles this in a browser.
Async Telegram workflow for local CLIs when Claude Code Channels hit limits.
Remote Cursor control over Nostr DMs paid in sats—solution seeking a problem.
Telegram-to-Claude bridge is nice UX, but continues a local session, not a true multi-device workflow.
Telegram bot wrapper for ACP agents when terminal notifications already exist.