Cursor From Telegram. On Purpose, Thin.

I run Cursor from my phone now. Telegram in, agent out.

And the whole point is that it can't do everything.

There's a whole category of "phone agents" that want to sound like an employee in your pocket - heartbeat, persona, proactive whatnot. I built the opposite. Allowlisted senders only. Permission modes you can flip: locked, readonly, standard. Call-and-response. No heartbeat. No "I took the liberty."

You message. It answers. If you want it to touch something outside the workspace, you said so - or the mode already forbade it.

I've been running this on my own box for a bit. Useful enough that I cleaned it up for strangers: a small open-source bridge, your bot token, your Cursor API key, your machine. DIY on purpose. I'm not hosting yours (unless you throw me cash, I'm salesy like that).

Here's the actual point of this all: the interesting part isn't that an agent lives on Telegram. It's the constraints. Permission modes are the product. I can let it own and manage the machine, when I let it. I can tighten the sandbox, above the LLM layer. Everything else is wiring.

I put a short page up - a staged chat demo, a FAQ, the repo link if you want to poke at it. No pitch deck energy. Just the thing.

• Landing page: https://www.tinthe.dev/telegram-cursor-agent
• Skip straight to GitHub: https://github.com/TinMarkovic/telegram-cursor-agent