CursorTgBot v1.4.0

What's new

Terminal agent tgBot. The same Cursor local agent now runs in the terminal, without Telegram.

• tgBot — interactive session in the directory you launched from; the session is kept across restarts
• tgBot -p "fix the failing test" — one shot, then exit
• tgBot --new or /new — drop the session and start fresh
• --workspace PATH — another directory, with its own session
• Старт / F2 / /start and Стоп / F3 / /stop start and stop the Telegram bot
• /settings — token, API key, repository, model, and autostart

./run.sh is still the Telegram bot. The CLI does not poll Telegram.

Desktop app files from earlier experiments are removed. Workspace trust prompts are gone.

CursorTgBot v1.3.0

What's new

• Telegram / command menu with descriptions (/task, /ask, /backlog, /status, /cancel, /diff, /new, /info, /phpunit, /phpstan, /help)
• Agent replies stay Telegram-friendly: no markdown tables, backlog lists as spaced blocks (ID effort · status + title)
• Cursor rule .cursor/rules/telegram-reply-format.mdc keeps that format in this bot, not in the target repo

Docs

• README notes how /backlog and agent replies are formatted

CursorTgBot v1.2.0

What's new

Simpler install and first-run setup:

• ./run.sh creates the venv, copies .env, and interactively asks only for Telegram token and Cursor API key
• REPO_CWD defaults to the directory you launched run.sh from
• CURSOR_MODEL defaults to auto
• Empty ALLOWED_USER_IDS: the first user who messages the bot is allowlisted automatically (written to .env, no restart)
• Minimal .env.example and shorter README install section

Upgrade

Pull v1.2.0 (or main). Existing .env keeps working; optional keys can be removed if you rely on defaults.

CursorTgBot v1.1.0

What's new

Telegram-friendly backlog list from REPO_CWD/.cursor/backlog:

• /backlog — active tasks (proposed / ready / doing)
• /backlog deferred — deferred tasks
• Phrases like «покажи список задач» answer instantly (no agent run)
• HTML layout: priority sections, one task per block, multi-message chunks without truncating the head
• Agent replies guided away from markdown tables for Telegram

Docs

• README commands table updated for /backlog

CursorTgBot v1.0.2

What's new

Cursor project rule (.cursor/rules/bot-lifecycle.mdc): when you ask to start or stop the bot, the agent runs the standard lifecycle (single ./run.sh instance / pkill for python -m bot).

CursorTgBot v1.0.1

What's new

Bootstrap without @userinfobot: leave ALLOWED_USER_IDS empty, start the bot, send any message — it replies with your Telegram user id. Put it in .env and restart. In a group, /info still returns the chat id for ALLOWED_CHAT_IDS / FORUM_CHAT_ID.

Docs

• README and .env.example updated for the new setup flow

CursorTgBot v1.0.0

CursorTgBot v1.0.0

First public release: control a Cursor local agent from Telegram and edit a git repo on the same machine.

Features

• /task — start a new agent run against REPO_CWD
• /ask / plain text — follow-ups in the same session
• Forum mode — each /task opens a Telegram topic; sessions keyed by (chat, thread)
• /status, /cancel, /diff, /new
• Optional /phpunit and /phpstan helpers (if scripts exist in the target repo)
• Long polling (no public webhook)
• Access limited by ALLOWED_USER_IDS / optional ALLOWED_CHAT_IDS

Requirements

• Python 3.11+
• Cursor API key
• Telegram bot token
• Local git repository path (REPO_CWD)

Quick start

git clone https://github.com/starline/CursorTgBot.git
cd CursorTgBot
python3 -m venv .venv && source .venv/bin/activate
pip install -r requirements.txt
cp .env.example .env   # fill TELEGRAM_BOT_TOKEN, ALLOWED_USER_IDS, CURSOR_API_KEY, REPO_CWD
./run.sh

See the README for forum mode and full command list.