> ## Documentation Index > Fetch the complete documentation index at: https://docs.liteclaw.ai/llms.txt > Use this file to discover all available pages before exploring further. # Commands > Complete reference for all bot commands. # Commands Reference All commands you can use with your Lite Claw bot in Telegram. ## Core Commands ### /start Initialize the bot connection. ``` /start ``` **Response:** * If unclaimed: Shows your Telegram ID and prompts to use `/claim` * If claimed: Confirms the assistant is online ### /help Display available commands. ``` /help ``` ### /claim Establish ownership of the bot. Only works once, before ownership is claimed. ``` /claim ``` | Response | Meaning | | --------------------------- | ---------------------------- | | "Claim successful..." | You are now the owner | | "Invalid claim code" | Wrong code | | "Too many claim attempts" | Rate limited, wait and retry | | "Ownership already claimed" | Bot already has an owner | *** ## /integrations Manage connections to Weather, Google Calendar, and Gmail. ### View Status ``` /integrations ``` Shows current integration status and available subcommands. ### Weather ``` /integrations weather San Francisco, CA ``` Configure your default weather location. ### Google Calendar ``` /integrations connect calendar ``` Start OAuth flow to connect Google Calendar. Opens a link to authorize. ``` /integrations calendar primary ``` Set which calendar to use (after connecting). ``` /integrations disconnect calendar ``` Revoke access and remove stored tokens. ``` /integrations disable calendar ``` Disable without revoking (keeps tokens for later). ### Gmail ``` /integrations connect gmail ``` Start OAuth flow to connect Gmail (read-only access). ``` /integrations gmail ``` Enable Gmail integration (must be connected first). ``` /integrations disconnect gmail ``` Revoke access and remove stored tokens. ``` /integrations disable gmail ``` Disable without revoking. *** ## /heartbeats Manage automated scheduled messages. ### View Status ``` /heartbeats ``` Shows which heartbeats are enabled and their schedules. ### Morning Briefing ``` /heartbeats morning on /heartbeats morning off ``` Daily briefing with weather, today's calendar, and email highlights. **Default schedule:** 7:00 AM in your timezone ### Weekly Review ``` /heartbeats weekly on /heartbeats weekly off ``` Weekly summary with week review and upcoming week preview. **Default schedule:** 6:00 PM Sunday in your timezone *** ## Confirmation System Write operations require explicit confirmation with a random code. ### Flow 1. You request an action: ``` Schedule dentist appointment Friday 2pm ``` 2. Bot shows preview and asks for confirmation: ``` I'll create this event: Title: Dentist appointment When: Friday, Feb 14, 2:00pm Calendar: Personal Reply YES 482193 to confirm, or NO to cancel. ``` 3. You confirm or cancel: ``` YES 482193 ``` or ``` NO ``` ### What Requires Confirmation | Action | Confirmation | | --------------------- | ------------ | | Read calendar | No | | Read email | No | | Get weather | No | | Create calendar event | **Yes** | | Modify settings | **Yes** | The random code prevents prompt injection attacks from auto-confirming actions on your behalf. *** ## Natural Language Any message that doesn't start with `/` is processed by the AI assistant. ### Examples ``` What's on my calendar tomorrow? ``` ``` Any important emails today? ``` ``` What's the weather this weekend? ``` ``` Schedule team standup Monday 9am for 30 minutes ``` The assistant will either respond directly (for read operations) or ask for confirmation (for write operations).