Security fixes are applied to the latest version on main.

Do not open a public issue for a suspected vulnerability. Use GitHub's Security → Report a vulnerability flow or contact the maintainer privately.

Include the affected version, impact, reproduction steps, and any suggested mitigation. Do not access calendar data that is not yours while validating a report.

Never include real Telegram tokens, OpenAI keys, or Google service-account credentials in an issue, pull request, log, or screenshot. If a credential may have been exposed, revoke or rotate it; deleting it from the latest commit is not sufficient.

Operators should restrict ALLOWED_CHAT_ID, set ALLOWED_USER_IDS, protect deployment secrets, and give the Google service account access only to the calendar Calbot manages.

Calendar event text is treated as untrusted data rather than instructions. Each current message independently authorizes no calendar tools, reads only, or writes; acknowledgments and small talk receive no tools or stale conversation history. Calendar writes are then validated and version-checked by the application, and a write is never reported as successful without a verified API result.