Open source
telegram-cursor-agent
Cursor from Telegram - on a leash.
A thin bridge to a local Cursor SDK agent. One workspace. An allowlist. Permission modes you can switch. Call-and-response only: no heartbeat, no "autonomous employee on your phone." Keep the utility of OpenClaw, don't set your tokens on fire.
FAQ
What is this?
A Telegram bot that forwards your messages to a Cursor SDK agent running on your machine, against your workspace. You bring the bot token, the Cursor API key, and the allowlisted Telegram ID. The repo is the product. This page is just the explainer.
What do I need to run it?
A Telegram bot (BotFather), a Cursor API key, a local workspace path, and your Telegram user ID on the allowlist. Copy config.example.toml and .env.example, fill them in, start the service. No hosted signup. No cloud runtime of mine.
What can / can't it do?
Three modes: locked (bot ignores prompts), readonly (read + git status/diff, no writes), standard (in-repo write, commit, push). You switch with /perms. It answers when you message it. It does not ping you. No persona store out of the box (unless you build one into the workspace). No proactive loop. Interactive approve/deny and multi-workspace routing are not in v0.1. Don't expect them.
Is this a hosted bot I can DM?
No. There is no public bot waiting for strangers. Clone the repo, stand up your own instance, talk to yours. Contact me if you'd like me to set one up for you.
How is this different from "autonomous agent on Telegram" tools?
It doesn't set your tokens on fire, for one. Most of that stack is useless magic with a few productive features buried underneath. This keeps the productive parts: phone in, agent out, hard gates. Want a persona? Build or load your own. Nobody's stopping you. The tool just won't pretend it shipped one.
Is it safe?
Safer than an open bot with no gates. Not magic. Sender allowlist (default: nobody). Explicit modes. Secrets live in your .env on your machine; they never go in the repo. You still chose to put a Cursor key behind a chat app. Treat that like the power tool it is.
Who is this for?
People already in Cursor who want a phone door with hard gates: technical founders, solo operators, anyone who finds "agent on Telegram" interesting and "no leash" terrifying. Cursor's own agent paths lean cloud or magic; they don't give you a simple agent that just runs on your machine. This does. Straightforward, yours. Not for toy-seekers who want a vibe employee in their pocket.
Where's the code?
github.com/TinMarkovic/telegram-cursor-agent - MIT, DIY, bring your own keys.
Are you going to expand this?
Yeah. More tools for pragmatic professionals are coming. Subscribe to the posts if you want them when they land.
Pairing with Seneschal
This is the phone door. Seneschal is the gate for Google-scoped actions: agent requests, human approves, then Gmail / Calendar / Drive. They pair naturally. The glue isn't public yet.