Started playing with it a little over a week ago as mentioned here #1559321 and it actually does well what I wanted to do back with the OpenClaw hype months ago #1424081

Since I'm a Cursor user anyway, and it tightly integrates with that given it's made by them, its utility is starting to compound a bit.

My team and I work in a Telegram group, conversations can zigzag, priorities change, ideas context and knowledge easily get lost from disorganization. Trello cards get neglected as a result, which reduces velocity since one may not touch an area another is working on to not create a tangle of conflicts.

Well I got it working with telegram exactly how I wanted OpenClaw to work months ago.

GrokBot has a concept of "Chief of Staff", a bot that you interface with and delegates stuff to other bots that have their own routines and context.

My Chief of Staff now sits in the group Telegram channel, conducts stand-ups, distills conversations into cards/updates them, can reference, update, or make PR's on GitHub, request reviews from my team, and is generally just useful for tagging to bring an answer into the conversation. Trello has never looked better and what everyone is working on in a given day has never been more clear.

Since my post a little over a week ago, either limits increased, or it's gotten more efficient. I got this all set up and its been put to work and my utilization for the week is less than the initial setup:

($60 Cursor Pro plan, which makes it basically free since that $60 includes $60 worth of credit to external models like Anthropic, Gemini, GLM, Kimi)

https://m.stacker.news/155606

There's a gotchya with getting Telegram working like this that was not clear and one of the reasons it probably didn't work with OpenClaw as intended... to listen to everything in a channel it needs a webhook endpoint for Telegram to hit on your bot.

Cursor provides an endpoint for this through their reverse proxy:

https://m.stacker.news/155607

The other gotchya is that the Cursor endpoint requires a bearer header, and Telegram bots do not support that. So, I still needed to set up a directive to add that header, but I was able to do that entirely in a Caddy directive without a separate process.

So TG hits my Caddy instance, Caddy adds the header, then forwards that to the Cursor proxy endpoint... bot does it's thing.

I believe its on the GrokBot roadmap to make it multi-player, so this may be obsolete in a week and we just replace Telegram altogether with GrokBot (its a fairly nice chat app in its own right very similar to TG)

Putting this out there in case it helps someone searching for a similar solution.