Grok Bot,
made simple.
Understand the platform.
Start with one useful task.
Redeem your meetup credits.
Use the credit link from your email on a single-user Cursor account, not a Team plan, for this meetup offer. Use the same account and browser throughout.
- Account + app. Sign in to your personal Cursor account, or create one. Download Grok Bot for Mac or Windows from x.ai/bot, then sign in with that same account.
- Start the trial, if offered. Choose Activate Trial and follow the verification prompts, including card details if requested. If your plan already includes access, skip this step.
- Redeem the credits. While still signed in, open the credit URL from your email and choose Get Started. Check for the credit in Cursor Dashboard under Billing or Credits before upgrading.
- Choose the Cursor upgrade. When you are ready to upgrade, or the trial reaches its limit, choose Upgrade to Pro for this credit offer. Upgrade with Grok uses a different subscription route. If your screen uses different labels, open Dashboard > Billing > Adjust plan and select Pro.
- Check out and return to Grok Bot. In Cursor's checkout, confirm the credit is applied and the amount due today is $0, including any tax. Check the plan, renewal price and renewal date. Complete checkout only if those details match your offer, then reopen Grok Bot and check its plan screen. If the credit is missing or money is due, stop and ask Ben before paying.
Notes
- Use the correct personal account before redeeming. This meetup credit flow is for individual accounts; it does not apply to a Team plan. Follow the expiry and redemption terms in your email.
- Card details or bank verification may be requested more than once. Follow the prompts shown for your account.
- The desktop trial has limited usage and a seven-day window. It can run out sooner, and exhausted trial credit does not refill. Check the plan screen for your actual remaining usage.
- Check whether the offer covers tax as part of the $0 total. If credit is missing, refresh the dashboard or sign out and back into the same account. Ask Ben if it still does not appear.
Credit redemption steps are based on the meetup organizer's supplied process. Trial details, plan changes and billing were checked on September 22, 2026. Your email and checkout show your offer's terms.
Get to know the platform.
A short explanation. One simple example.
BotsWho does the work
A Bot is an AI teammate with a name, a job and its own ongoing conversation. Start with one clear role. Use this as the description for a Bot named Day Planner.
Help me plan tomorrow from my to-do list. Use my deadlines and time estimates. Keep the plan in chat.
Chat & tasksWhat you want done
A task is a specific request you send in chat. Give the Bot your list and available time, then review the answer. After pasting your list, try:
I have 2 hours tomorrow. Pick up to 3 priorities from my list and put them in a realistic order. Show what will have to wait.
Computer & appsWhere work happens
Bots can use connected apps and a shared cloud computer. Your Bots share its files and logins. For your first exercise, just paste a list into chat.
Use only the to-do list I pasted here. Do not open other apps or change any files.
SkillsHow work gets done
A skill saves a method you can reuse. Correct the result first, then save the instructions and try them with a different list.
Save our corrected planning method as a skill called Plan Tomorrow. Check deadlines and time estimates, fit the available time, and ask if the tasks do not fit.
RoutinesWhen work runs
A routine starts work on a schedule or supported event. Once the skill works, choose the time, time zone and source of fresh information. Start by asking for a proposal:
Propose a weekday routine for 6 PM, America/New_York, using Plan Tomorrow. Ask where my current task list will come from. Show the settings first; do not enable it yet.
ApprovalsWhere you decide
Tell the Bot which actions need your approval. Review proposed changes before allowing them.
Draft my plan in this chat. Ask me before changing my calendar, editing files or sending messages.
Try it at your level.
Start with Beginner. The other examples are optional.
Plan tomorrow.
Create a Bot called Day Planner, select its chat and paste this example. No app connections are needed.
I am free tomorrow from 9 to 11 AM.
My tasks:
- Finish proposal: 45 minutes, due 10 AM.
- Prepare client call: 30 minutes, due 11 AM.
- Reply to venue: 10 minutes, due noon.
Draft a plan with start and finish times. Keep my estimates and deadlines unchanged. Show total work and spare time. Keep the answer in chat; do not send messages or change my calendar.
Check that the plan includes 85 minutes of work and 35 minutes spare. If it gets something wrong, explain the correction in the same chat.
Reuse a method that works.
After checking and correcting your first plan, save the method:
Save our corrected method as a skill called Plan Tomorrow. Ask for the task list, deadlines, time estimates and available hours. Check the total, flag anything that does not fit, and return a draft in chat. Do not save today's tasks as permanent instructions.
Then type / in chat, select Plan Tomorrow, and give it a new list:
I am free from 2 to 4 PM tomorrow.
- Prepare an invoice: 30 minutes, due 3 PM.
- Prepare a call: 35 minutes, due 4 PM.
- Research a train route: 15 minutes, due 4 PM.
Plan these in the listed order. Keep the draft in chat; do not send, book or edit anything.
Check for 80 minutes of work and 40 minutes spare. If the saved method is wrong, correct it and test again.
Check two sources before drafting.
Try a meeting follow-up that compares notes with an existing task list. This fictional example contains a date conflict and a missing deadline.
Compare these two sources.
Existing task list:
- Maya: send the workshop agenda by October 2, 2026.
New meeting notes:
- Maya: send the same agenda by October 3, 2026.
- Leo: check room availability. No deadline was given.
Find the existing task so it is not duplicated. Flag the conflicting agenda dates and ask for Leo's deadline. Do not choose dates yourself. Wait for clarification before drafting the follow-up email. Keep everything in chat; do not update tasks or send anything.
The Bot should ask which agenda date is correct and when Leo's task is due. Once the answers are supplied, ask for the follow-up draft. Test the method before saving it as a skill or adding a routine. A routine's Test run performs real work.
More ideas to explore
For more ideas, browse botdirectory.ai, a community prompt directory operated by Inbox Zero Inc. It is separate from Grok Bot's in-app Marketplace. Credit belongs to each prompt's creator.
- Bot Advisor, credited to @petergyang: help define a Bot's role.
- Webby, credited to @farzyness: website and newsletter work.
- Chief of Staff (Avid), credited to @Av1dlive: organize priorities and specialist Bots.
These are examples to explore, not workflows tested for this workshop.
Sources and credits
Community guide and original practice examples by Ben Milshtein / Palma Labs. All exercise data is fictional. Product documentation is credited to SpaceXAI and Cursor; community prompts are credited above.
- Grok Bot overview
- Get started
- Sign in through Cursor
- Bots
- Chat and tasks
- Computer and apps
- Skills and routines
- Approvals
- Grok Bot plans and trial
- Cursor billing
- About botdirectory.ai
Product details checked September 22, 2026. The redemption path is based on the meetup organizer's supplied instructions; the email offer and checkout control eligibility and amounts.