Thanks for pointing out the possible security issue. But it's worth noting that, this connector works with cursor *cloud agent* API and telegram bot API, which means it does not exposes any reachable service to the public. This would lead to polling cursor cloud agent API for receiving new messages, but since this is a tool meant for personal use so I guess it's fine.
Is your test suite meant for this scenario? If so, I would be glad to provide a live sandboxed instance for you to test.
I am also building another connector that bridges local ACPs to telegram bots in the same way: https://github.com/tb5z035i/telegram-acp-connector. Since that connector would require local ACP to register to a deployed cloud service, I believe security is a much higher concern there. If you are interested, you can also run the test suite there when it's ready ;)
Is your test suite meant for this scenario? If so, I would be glad to provide a live sandboxed instance for you to test.
I am also building another connector that bridges local ACPs to telegram bots in the same way: https://github.com/tb5z035i/telegram-acp-connector. Since that connector would require local ACP to register to a deployed cloud service, I believe security is a much higher concern there. If you are interested, you can also run the test suite there when it's ready ;)