The best recent Grok Bot videos

1. Use your chief of staff Bot to create the others, one job each.
2. Keep the inbox manager draft-only for weeks, then have it compare its drafts with what you sent every Friday.
3. A people Bot that never guesses spellings fixes names in emails.
4. Give business Bots read-only access and tell them to say when data is missing instead of guessing.
5. Pro tips: prefer APIs over clicking, use a shared password vault, and do a task once, save it as a skill, then schedule it.

Commenters: Mostly enthusiastic, with the people Bot singled out. Some push back on locking into one tool, note that Claude has scheduling too, or suggest starting with one routine and clear limits on data and spending.

1. Usage allowances changed suddenly and some accounts were later reset or restored.
2. Keep your Bot instructions, prompts and key files in a folder you control.
3. Have a fallback for important work in case limits change again.
4. Check your own usage page rather than relying on reports from others.

Commenters: The busiest comments of the day: dozens of viewers report usage jumping overnight and then dropping back, reset days moving, and plans running out early. Some say they now keep backups or have trimmed their filing system to use less.

1. Start with one main dashboard on your chief of staff Bot: waiting on me, recently finished, upcoming routines.
2. The routines column helps you cancel routines you no longer need and save usage.
3. Use a reverse prompt so your Bot, after checking with your other Bots, suggests five dashboards for you.
4. Pin the dashboard from the Library's three-dot menu, and share it by link if teammates need it.
5. His prompt says to use only real data and show anything missing as empty.

Commenters: Mostly requests for more Grok Bot videos. One viewer ran the reverse prompt and had the dashboard they needed in two minutes; another said it should help cut their usage costs.

1. Shopping now runs from search to checkout to order tracking inside Grok Bot.
2. Save payment methods and several contacts in the Vault and pick a primary one.
3. Team Bot managers can save logins that work for every user.
4. Share Team Bots with your team or whole organization and pin them in the Library.
5. Team Bot routines ask for missing connectors right in Slack.

Commenters: Most top comments ask why the video doesn't mention the new usage limits, with Ultra users saying their allowance ran out much faster this week. Others enjoy the beach walk format and ask for voice calls outside the US.

1. Build a benchmark from the tasks each assistant already does for you.
2. Give every assistant the same connectors and skills before comparing.
3. Use short prompts in your own voice and decide in advance what to say if it asks.
4. Grok Bot won the work tasks in her test; Muse did best on family-style output.
5. Pick the assistant per job instead of one for everything.

Commenters: Viewers found it helpful for deciding which agent to use. Several suggest a blind test next time and ask about cost; many loved the family newspaper idea and asked to see it.

1. Keep one Bot per area of your life so each one holds the right context.
2. His finance Bot reconciles transactions every Monday and asks him when something is unclear.
3. A content routine at 8 a.m. and 3 p.m. picks three topics from X and adds links to matching Notion idea cards.
4. For code he uses skills for worktrees, evidence-based testing and review, and only merges work that passes review.
5. AI video editing is promising for clips but not yet a full replacement for his editor, in his view.

Commenters: Lots of thanks and new subscribers. One viewer routes all inbound messages through a comms triage Bot; another says the Plaid finance connector misses merchant data on some accounts; one warns a Bot mixed demo data into a marketing text.

1. Check a repeat job once, then turn it into a script the skill runs.
2. Batch your fixes into one message instead of many small ones.
3. Brief with the goal, why, what to avoid and a 3 to 5 line done list.
4. Send text instead of full screenshots where you can, and crop images.
5. Keep one Bot per kind of job so each chat stays small.

Commenters: Split: some say it saved them and had their chief of staff watch it and apply the fixes, while others question the claim that Bots reread the whole chat, point to the reduced limits as the real cause, or criticise the paid community links.

1. Long chats get re-read on every step, which can dominate usage.
2. Write a short handoff file and continue in a fresh copy of the Bot.
3. Keep the old Bot rather than deleting it.
4. Cut watchdog routines that almost never find anything.

Commenters: Mostly short praise, which some viewers say looks automated. One asks for a shorter video since the answer is simple.

1. Let your Bot plan and check; hand the code to Claude Code or Cursor cloud agents.
2. Coding through your Bot uses the same weekly usage pool, so offload heavy work.
3. Score the backlog with reach, impact, confidence, effort and blast radius.
4. All your Bots share one computer, so a CLI logged in with a key there is usable by all of them.
5. Start with one loop: acceptance test, proof, pull request, report back.

Commenters: Viewers compare it with their own orchestrators in Claude Code and T3 Code; one team says manually reviewing most pull requests is their main bottleneck. A few are sceptical, calling it an ad for Grok Bot and asking to see a full build from start to finish.

1. Give the Bot your account details, current price and a real competing offer before it calls.
2. It asks clarifying questions first, then handles phone menus and hold time.
3. Tell it to check with you before agreeing; his call needed an approval link.
4. You get a live transcript and the full voice recording.
5. Other uses: phone-only cancellations, waiting on hold, reservations, contractor quotes.

Commenters: Viewers enjoy the AI-to-AI moments with the rep and see uses for car and medical appointments. Others ask how much usage a call takes, mention that some people hang up on a virtual assistant, and complain about the new usage limits.

1. A routine every 15 minutes runs almost 100 times a day; merge quiet ones into one daily and one weekly check.
2. Duplicating a Bot keeps its settings, skills and routines but not its chat or memory, so write a handoff note.
3. Ten small messages cost more than one message with ten things in it.
4. Copy text or crop screenshots; turn long PDFs into text first.
5. Set a monthly limit on additional usage credits so a busy week can't surprise you.

Commenters: A small, mostly thankful group. Some share their own usage numbers and daily routine checks; a few point out that each reply resends the whole conversation, and some are frustrated with the limits.

1. Write the role, tone and limits first; the Bot refers back to them on every run.
2. Ask the Bot to repeat its title, duties and handling of unverified sources before automating.
3. Connections are account-wide, so every Bot can use Gmail once it's connected.
4. Put the report format in a skill so a new topic keeps the same structure.
5. Share as template strips history, email addresses, IDs, tokens and keys before you publish a link.

Commenters: Mostly viewers listing what they'd track with it: grant opportunities, competitor launches, case law, agency client news and patent filings. One calls the multi-Bot hand-off the standout.

1. Have a guard Bot ask each Bot before it pauses or changes a routine.
2. Never delete: hide old Bots and pause routines instead.
3. Restart a very long chat by writing a handoff note into a fresh copy of the Bot.
4. Paste five no-small-talk rules into every Bot that talks to others.
5. Run the check weekly, supervised for the first two weeks.

Commenters: Small but positive: viewers thank him for the clear explanation and the free guide, and like hiding old Bots instead of deleting them.

1. Use Grok Bot for quick, voice-friendly operational work across Bots that share one file system.
2. Group chats with many Bots can create back-and-forth that wastes usage.
3. Hook Bots into a structured tool such as Notion rather than relying on long chats.
4. Ask for a functional mock-up first before building a full app.
5. Keep your workflow tool-agnostic so you can pick the best tool per part.

Commenters: Viewers share hybrid setups, such as Claude for main work and Grok Bot as a personal assistant, or having a Bot install Claude Code in its terminal. Token use is a common worry, and one raises data privacy.

1. A page doesn't update itself; schedule a routine to refresh it.
2. Daily refreshes are usually enough; hourly updates use a lot more usage.
3. Pages can hold tables, charts, filters, switches and tabs, not just text.
4. Pages start private; personal accounts can share by link, team accounts with invited people or the whole team.
5. People you share with can use filters but can't change the page.

Commenters: One comment so far, praising how clearly it's explained.

1. Name and label is all a new Bot needs to start.
2. Ask a research Bot to verify against primary sources and flag claims that don't hold up.
3. Buying, sending, deleting and publishing stay behind your approval; ask-first beats allow when rules collide.
4. Teach a skill records you doing a task once and saves the steps.
5. Test runs can work on a copy so your real tracker stays clean.

Commenters: Few comments; one viewer says Grok Bot is the main reason they keep Cursor Pro, and others joke about the sponsorship.

1. Create an MCP server in Zapier, add YouTube and select the tools the Bot may use.
2. If the connection fails, select tools from the link the Bot gives you, or rotate the token and paste the new details.
3. Ask for a ranked list with real quotes and likes, not a vague summary.
4. The same method works on any pile of raw text: Slack messages, email or CSV exports.
5. A weekly run over the last 7 days of comments can feed your content plan.

Commenters: Few comments; one viewer is tired of 'agent does everything' videos and wants to see real workflows without babysitting, another asks what makes it 'for pros'.

1. Give each Bot one job.
2. Attach context files so a new Bot knows your preferences.
3. Use the Bot's own email address for sign-ups, and your main email for real outreach.
4. Ask for a Page with a calendar view and have the routine keep it updated.
5. Import memories from other assistants in Settings.

Commenters: Only a handful of comments: one asks whether Grok Bot can summarise Teams meetings, another complains about usage.

1. Give each Bot one job, like a coworker with a clear role.
2. Put your rules in the first message; the Bot keeps them for every future brief.
3. Say 'run it once now' when you create a routine so you see the first result straight away.
4. For comparisons, insist on official pricing pages and no signing in.
5. Ask for a file you can share, and start with public web jobs before connecting apps.

Commenters: Two comments, one of them advice: start with one narrow routine, such as a daily price check that only messages you on a change, and run it for a week before adding more.

1. Voice chat starts instantly and works the same on the phone.
2. A local app's MCP server can be reached by giving the Bot a Tailscale Funnel address and port.
3. Keep the MCP token out of chat and configure it securely.
4. One Bot can ask another, like a Discord triage Bot, and report back mid-call.
5. A daily news Bot can fill a board with cards and draft posts for X, Bluesky and Substack.

Commenters: A few comments: the creator notes it works the same on his phone, and viewers ask for more app-building videos.

1. A Bot with its own browser can test full funnels, not just read one page.
2. Ask for scores, top fixes and a click-by-click timeline.
3. Results depend on location; his ran from a UK IP.
4. Rerun the test on a schedule to catch flows that break.
5. A Bot's own email address can sign up to competitors' lists to see their follow-up emails.

Commenters: One comment so far, praising his website and resources.

1. Promote a Bot with plenty of context to director and let it create and manage the Bots under it.
2. Talk to between one and seven Bots yourself; directors filter everything else to a weekly summary.
3. Ask Bots for proof of work and source links so their manager can check them.
4. He starts his mornings in his drafts folder, where his Bot has prepared replies, rather than his inbox.
5. For bugs, a cloud agent reproduces, adds a failing test, fixes and opens a pull request that waits for an engineer.

Commenters: No comments yet on this video.

1. Ask your Bot to claim an email, then use plus aliases to route each kind of mail to its own routine.
2. A Bot can have its own Google account made with its address, so you can share docs with it.
3. With 1Password, the Bot asks for a login on a card and the password is filled without the Bot seeing it.
4. Pages shine for charts, tables and filters; iterate a few times before putting one on a routine.
5. The team backs up Bot context to tools like Notion, Obsidian, Google Drive or a private GitHub repo.

Commenters: No public comments on the video yet.

1. Put sensitive, must-be-identical workflows in one admin-managed Team Bot that everyone's Bots ask.
2. Team Bots can use service accounts, Vault secrets and their own browser to reach internal tools with no API.
3. Auto Review runs a separate check on high-risk actions and can require a human yes.
4. Route regulated wording through a compliance-checking Team Bot with human review.
5. For long-term memory, the built-in memory works; repos or third-party memory connectors are options.

Commenters: No public comments on the video yet.

1. Describe the Clay workflow you want to your Bot instead of configuring columns by hand.
2. Pair Grok Bot for thinking and research with Clay for repeatable enrichment.
3. An event Bot can merge CRM contacts with new ones from Clay into a Google Sheet.
4. The Clay CLI on the Bot's computer can read a legacy table and rebuild it as a workflow.

Commenters: No public comments on the video yet.

1. Clone a working personal Bot and convert the copy into a team Bot.
2. Decide which plugins, secrets, skills and memories the team gets.
3. Teammates can use the Bot without seeing the keys behind it.
4. Add it to Slack so the team can ask it directly.

Commenters: No public comments on the video yet.

1. Keep an X Bot read only and write your replies yourself.
2. Filter for posts that invite replies, are fresh, have reach and where you can add something.
3. Message only for Act now; everything else waits for the morning brief.
4. Have the Bot keep its role and rules written in Notion and update it when they change.
5. Use it as an editor: paste your reply and ask what could read badly.

Commenters: No public comments on the video yet.

1. Connect email and calendar first; ask questions like whether an invoice got paid.
2. A morning routine drafts replies to overnight email; another makes a prep doc before each meeting.
3. A write-like-me skill built from 120 of his sent emails.
4. His engineering head Bot has eight product Bots reporting to it, which start cloud agents on the model he names.
5. Reply to any Bot message to send it to Slack or email, with an editable card before it goes.

Commenters: Most of the 228 comments are viewers commenting "Bots" to get Nat's Bot templates, so the count overstates discussion. One viewer described their own daily newspaper routine.

1. Use your chief of staff Bot to create the others, one job each.
2. Keep the inbox manager draft-only for weeks, then have it compare its drafts with what you sent every Friday.
3. A people Bot that never guesses spellings fixes names in emails.
4. Give business Bots read-only access and tell them to say when data is missing instead of guessing.
5. Pro tips: prefer APIs over clicking, use a shared password vault, and do a task once, save it as a skill, then schedule it.

Commenters: Mostly enthusiastic, with the people Bot singled out. Some push back on locking into one tool, note that Claude has scheduling too, or suggest starting with one routine and clear limits on data and spending.

1. On the trip, Grok Bot reached a flight site that blocked the other two and found cheaper options; commenters point to the Route traffic through this computer setting as the likely reason.
2. Grok Bot's team of Bots and an orchestrator Bot are his main reasons to pick it for work; one Bot per job avoids context rot.
3. You can import skills you already use in Claude Code into a new Bot by asking it to copy them into its files.
4. Usage was his main complaint: he hit his plan limit during the tests and paid for on-demand usage.
5. His verdict: Grok Bot for work, Muse as a free personal assistant, Dots not there yet.

Commenters: Lots of praise for how much work went into the tests. Several viewers explain the unblocking as traffic routed through his own computer, and some note Grok Bot can hand coding to Cursor or other models.

1. Usage allowances changed suddenly and some accounts were later reset or restored.
2. Keep your Bot instructions, prompts and key files in a folder you control.
3. Have a fallback for important work in case limits change again.
4. Check your own usage page rather than relying on reports from others.

Commenters: The busiest comments of the day: dozens of viewers report usage jumping overnight and then dropping back, reset days moving, and plans running out early. Some say they now keep backups or have trimmed their filing system to use less.

1. Start with one main dashboard on your chief of staff Bot: waiting on me, recently finished, upcoming routines.
2. The routines column helps you cancel routines you no longer need and save usage.
3. Use a reverse prompt so your Bot, after checking with your other Bots, suggests five dashboards for you.
4. Pin the dashboard from the Library's three-dot menu, and share it by link if teammates need it.
5. His prompt says to use only real data and show anything missing as empty.

Commenters: Mostly requests for more Grok Bot videos. One viewer ran the reverse prompt and had the dashboard they needed in two minutes; another said it should help cut their usage costs.

1. Pages turn analysis into a visual page you can keep private or share; he uses them for posting activity, training and sales.
2. Vault stores passwords and personal details encrypted, and the Bot fills them in without seeing them.
3. Grok Bot now works with Apple Home, Reminders, Location, Contacts, Alarms and Calendar. His example: a 5pm routine that turns off lights left on.
4. Ask for a video and it uses the Imagine models; subagents can now make images and video too.
5. Smaller changes: pin items in a Bot's Library, fewer approval cards, > for block quotes, Cmd+/ for all shortcuts, and a .docx you send can become a Google Doc.

Commenters: Mostly thanks for the weekly format, plus requests (smarter voice mode, CarPlay, Google Home) and some complaints about usage limits and 1Password asking before each login.

1. Star one main bot to talk to; it can pass work to your other bots.
2. Bots can now hand tasks to other leading models behind the scenes.
3. Ask your bot 'what can you work on to further my goals?'
4. Tagging @bot on X can send a task straight to your Grok Bot.
5. You don't have to pick one agent; use whichever fits the job.

Commenters: Positive. Viewers liked the short, direct format, and one said they would reuse the 'further my goals' prompt.

1. You keep one bot and one chat while the model behind it can change.
2. Routing is automatic; there is no model setting to pick.
3. Pricing for the multi-model setup was not announced when filmed.
4. When a better model ships, the bot can switch without you changing anything.
5. It is not yet clear which tasks go to which model.

Commenters: Positive about the update. Several still want to choose models themselves, and one noted you can pick a model for Cursor cloud agents a bot spins up.

1. The bot's computer responds about 3x faster.
2. Revised drafts for Slack or Gmail now show highlighted edits.
3. Bots can read and reply to your X Chat DMs, with anti-spam limits.
4. New connectors include Robinhood, Coinbase and Trello.
5. Team bots get access lists, and you can set Grok Bot as your Android assistant.

Commenters: Very positive. Viewers love the weekly walking updates; the main complaints were about usage running out and top-up pricing.

1. He migrated one role at a time with his lead Bot: keep, merge, instructions or shared skill.
2. Too many procedures made his old rules contradict each other.
3. Eight group chats replaced his old work stream files.
4. Everything is files on the Bot's computer; you can ask a Bot to zip and send them.
5. Write down what each Bot must never do, and start small.

Commenters: Mixed. Viewers who followed his folder method were interested; some pushed back on the course promotion at the end.

1. The Bot's server and its Linux computer sleep and wake separately, so the computer can be rebuilt without losing the agent's state.
2. Expensive work goes to helpers with fresh context; only results come back, which keeps the main chat small.
3. The harness tries the cheapest reliable option first: what it knows, a plugin or API, web search, the browser, the desktop, then you.
4. Untrusted inputs such as email are not treated as instructions, and irreversible actions like sending ask first.
5. Memory works in layers: core facts in every prompt, dated logs, short-lived scratch notes, and everything else in searchable files.

Commenters: Very positive; viewers call it one of the clearest explanations of agent harnesses and ask for the rest of the lecture series.

1. Tell your X Bot to move routines off the paid X developer API onto the built-in X search, then tell your other Bots.
2. His Bot reported a free allowance of 1,000 X reads a day.
3. Bots share one file system but each has its own screen and a terminal.
4. Ask a Bot to install Claude Code or Codex in its terminal, then take over to sign in.
5. Clone your repo and move your skills and agent file over so the Bot works like your own desktop.

Commenters: Positive. One viewer called running Claude Code in the Bot's terminal a life changer.

1. Treat each bot like an employee with its own desk (its context window).
2. Keep chats well under the context limit; quality drops when they get very long.
3. A subscription-audit bot found services he no longer used.
4. Long question lists, like due diligence, are a good fit for a bot.
5. Use it daily; most people quit before they build momentum.

Commenters: Enthusiastic. Viewers asked for more on grouping bots and more flexible usage, and one joked about the video's editing.

1. Star a primary Bot and send it most requests; it hands work to the others, and you can voice-call it.
2. Team Bots start clean: teammates connect their own logins, and routines stay personal.
3. Ask for drafts of the replies you owe, then send or discard each card in chat.
4. Turn on Settings, Computer, Network, Route traffic through this computer so sites block the cloud machine less.
5. Bonus: he keeps plugins in Composio so they move with him between agent apps.

Commenters: Positive. Viewers liked that it explained the updates without a bunch of random hype.

1. Shopping now runs from search to checkout to order tracking inside Grok Bot.
2. Save payment methods and several contacts in the Vault and pick a primary one.
3. Team Bot managers can save logins that work for every user.
4. Share Team Bots with your team or whole organization and pin them in the Library.
5. Team Bot routines ask for missing connectors right in Slack.

Commenters: Most top comments ask why the video doesn't mention the new usage limits, with Ultra users saying their allowance ran out much faster this week. Others enjoy the beach walk format and ask for voice calls outside the US.

1. Ask your Bot for an email handle and it claims its own inbox.
2. X search works without connecting a developer account.
3. Shopify joins the connectors.
4. Draft cards are better formatted and let you pick the sender.
5. The Bot's computer is faster with a bigger screen, and routines get a right-click menu.

Commenters: Positive. Requests for custom email domains and iCloud support came up a few times.

1. Star a main bot that sees what your other bots are doing.
2. Bots can be proactive, such as warning you a ride no longer matches a changed flight.
3. Bots can manage PRs through Origin and GitHub.
4. A slides skill sends you real PPTX files.
5. Team bots get feedback threads and group voice calls.

Commenters: Positive about the format. The top request by far was letting bots see their own usage, with some frustration about billing.

1. A chief of staff sends a Monday brief and manages the other bots.
2. An email bot screens brand deals and only flags the good ones.
3. Record yourself doing a task so the bot copies every step.
4. Approval and login requests appear in that bot's own chat, not the group chat.
5. Have bots log their work to a sheet or Notion, since you can't browse their memory.

Commenters: Glowing. Many called it the best Grok Bot explainer they had seen, and several subscribed.

1. Build a benchmark from the tasks each assistant already does for you.
2. Give every assistant the same connectors and skills before comparing.
3. Use short prompts in your own voice and decide in advance what to say if it asks.
4. Grok Bot won the work tasks in her test; Muse did best on family-style output.
5. Pick the assistant per job instead of one for everything.

Commenters: Viewers found it helpful for deciding which agent to use. Several suggest a blind test next time and ask about cost; many loved the family newspaper idea and asked to see it.

1. Keep one Bot per area of your life so each one holds the right context.
2. His finance Bot reconciles transactions every Monday and asks him when something is unclear.
3. A content routine at 8 a.m. and 3 p.m. picks three topics from X and adds links to matching Notion idea cards.
4. For code he uses skills for worktrees, evidence-based testing and review, and only merges work that passes review.
5. AI video editing is promising for clips but not yet a full replacement for his editor, in his view.

Commenters: Lots of thanks and new subscribers. One viewer routes all inbound messages through a comms triage Bot; another says the Plaid finance connector misses merchant data on some accounts; one warns a Bot mixed demo data into a marketing text.

1. Check a repeat job once, then turn it into a script the skill runs.
2. Batch your fixes into one message instead of many small ones.
3. Brief with the goal, why, what to avoid and a 3 to 5 line done list.
4. Send text instead of full screenshots where you can, and crop images.
5. Keep one Bot per kind of job so each chat stays small.

Commenters: Split: some say it saved them and had their chief of staff watch it and apply the fixes, while others question the claim that Bots reread the whole chat, point to the reduced limits as the real cause, or criticise the paid community links.

1. Weekly included usage is spent first; credits only kick in after it, up to the monthly additional usage cap.
2. Buying credit doesn't raise the cap; edit the cap on the billing page.
3. If you never unified, Grok Bot may be metered on cursor.com, so Grok or X credits won't help.
4. Hourly or 15-minute routines and third-party models are big drains; add a check-first line or slow them down.
5. Rebuild a usage audit page once a month with a routine.

Commenters: Mostly positive; some set it up as a skill or weekly routine. One says a team engineer told them context is compressed so long chats matter less, another notes the app does show the exact reset time, and several call the handoff and audit workarounds for missing features.

1. The Work guide's four Bots: Inbox Manager, Calendar EA, Intel Scout and a Bot Boss that you talk to instead of the others.
2. Guide Bots are created turned off; nothing runs until you hit Enable.
3. Marketing and recruiting Bots can be imported from the marketplace or a template link.
4. Keep sends, posts and refunds behind your approval, as every guide does.
5. The PM guide's attention list: an hourly routine that tracks what you are really working on.

Commenters: Mostly positive. Viewers liked the department-by-department approach, and one pointed to x.ai/bot/guides for the originals.

1. Bots share long-term memory, which he likes, but he wants to read and edit it directly.
2. Ask a Bot to work on its computer when you want to watch the steps.
3. Group chats work, but Bots share one computer and could overwrite each other's files.
4. Only automate a process you've done by hand for a while; use a generalist Bot for one-off jobs.

Commenters: Viewers called it an honest review. Several agreed usage runs out quickly, and some noted that Bots share one computer.

1. The spam shield reads your inbox and spam folder each morning; he says it pulled 21 real emails out of his spam, including a contract.
2. Only create a new Bot if it needs its own memory, different permissions or its own schedule. Otherwise ask your chief of staff.
3. The deal hunter gets its own email address to ask suppliers for quotes, and sends nothing until you approve.
4. The CFO Bot is read-only and reports what each Bot and subscription costs you.
5. One chief of staff beats talking to six Bots, each with its own chat to keep up with.

Commenters: Positive overall. Several commenters singled out the 'when to create a new bot' section as the most useful part.

1. One Bot per type of job. You don't start new chats; you message the Bot.
2. Connect Gmail from the chat, and add more than one account per connector. The inbox Bot set itself an hourly routine.
3. On a Mac, Teach a task records one QuickBooks entry and turns it into a skill you run with /.
4. Attach your SOPs so the support Bot drafts answers that follow your rules, then schedule it for business hours.
5. Group chats let Bots pass context to each other but use your weekly allowance faster.

Commenters: Mostly positive. People liked the one Bot per job framing and the group chat handoff; a few raised token use.

1. You can ask your bot which model it is using for a task.
2. Native X search helps find posts you half remember.
3. Write routines carefully so bots can handle recurring business tasks.
4. Add a check step so the bot verifies its own work before reporting back.
5. Speed and accuracy have improved, so it is worth retrying.

Commenters: Mostly positive. Some said they used a week of usage in days, and one warned about tying a business to a social account.

1. Ask for a report, memo or dashboard and the bot builds a Page.
2. A routine can keep a Page up to date.
3. A subscription Page can flag possible double charges and unused services.
4. Pages can show a client the before and after of a project.
5. Ask for design changes in plain words, like making urgent items red.

Commenters: Positive. One viewer is building video reports with Pages, and a few wanted clearer usage numbers for the $30 plan.

1. Grok Bot can run commands on your computer, which can reach devices on your home network.
2. Prototype the page layout with a Bot before automating it.
3. Reuse Bots that already have your calendar, bookmarks and workouts.
4. An always-on computer (Raspberry Pi, Mac mini) makes the morning routine reliable.

Commenters: Warm response with lots of ideas: a daily news podcast instead of paper, printers with their own email address, a ping to ask if the laptop is open, and adding a daily verse. A few raise usage worries and multiple Google logins.

1. Long chats get re-read on every step, which can dominate usage.
2. Write a short handoff file and continue in a fresh copy of the Bot.
3. Keep the old Bot rather than deleting it.
4. Cut watchdog routines that almost never find anything.

Commenters: Mostly short praise, which some viewers say looks automated. One asks for a shorter video since the answer is simple.

1. Ask first rules beat Allow rules when they conflict, and a Bot can't loosen its own Auto-review rules.
2. Test prompt injection by emailing your Bot hidden instructions; add a rule that email and web content are information, not orders.
3. Email routines can be limited to chosen senders or domains and given their own alias.
4. After a computer update, files and logins stay but installs are removed; keep a restore skill.
5. All your Bots share one computer, so a login or install is available to every Bot.

Commenters: Many ask for a copy of his house rules file. One viewer warns that local execution can drop if the Grok Bot app loses focus; another asks whether a long rules file costs extra usage.

1. Start at cursor.com/unify and check each account it matches before connecting.
2. Two Grok accounts on different logins can block linking; match logins first.
3. The plan screen defaults to a pricier plan; compare with what you pay now.
4. Third-party models are billed at API pricing, outside the plan's usage.
5. Linking is permanent, and intro prices rise after the first months.

Commenters: Thankful for the coverage, but many report account-linking problems or feel usage got worse after switching. Several ask how to undo it or keep only Cursor, and one advises people on grandfathered plans with API credits to stay put.

1. Let your Bot plan and check; hand the code to Claude Code or Cursor cloud agents.
2. Coding through your Bot uses the same weekly usage pool, so offload heavy work.
3. Score the backlog with reach, impact, confidence, effort and blast radius.
4. All your Bots share one computer, so a CLI logged in with a key there is usable by all of them.
5. Start with one loop: acceptance test, proof, pull request, report back.

Commenters: Viewers compare it with their own orchestrators in Claude Code and T3 Code; one team says manually reviewing most pull requests is their main bottleneck. A few are sceptical, calling it an ad for Grok Bot and asking to see a full build from start to finish.

1. Each routine is one line that runs a skill; the skill holds every instruction.
2. Skills live in a GitHub repo and a nightly routine syncs them onto the Bots.
3. Bots log each run so his chief Bot can see who did what.
4. Each Bot has its own email address and sends a few fixed types of email.
5. Numbered items let him approve with short replies from his phone.

Commenters: Mixed to positive.

1. Tag @bot under a post to send the request to your Grok Bot privately.
2. X reads are free with limits: he cites 1,000 a day and up to 25 posts per search.
3. Ask for a sentiment comparison or an analysis of your own posts' performance.
4. Give your Bot an email name that isn't yours, so copying it into threads makes sense.
5. Scheduled email reports, such as a Friday weekend plan, get read more than chats.

Commenters: Mixed. Viewers liked the use cases; several disputed the claim about which model is the default, and one disliked the rap battle demo.

1. The iPhone tab lists Calendar, Home, Reminders, Contacts, Location and Alarms; Messages is not included.
2. Group Bots into folders by long-pressing a Bot and choosing Move to.
3. His texting demo used a separate Twilio number given to the Bot, not the phone's Messages app.
4. In his live test the alarm didn't appear at first; he later commented that it worked but didn't show in the app.
5. Keep card and login details in the Vault rather than pasting them into chat.

Commenters: Short thread: one viewer says Android has the same option, another says their alarm was set but not switched on, and some can't see the Apple apps yet.

1. Give the Bot your account details, current price and a real competing offer before it calls.
2. It asks clarifying questions first, then handles phone menus and hold time.
3. Tell it to check with you before agreeing; his call needed an approval link.
4. You get a live transcript and the full voice recording.
5. Other uses: phone-only cancellations, waiting on hold, reservations, contractor quotes.

Commenters: Viewers enjoy the AI-to-AI moments with the rep and see uses for car and medical appointments. Others ask how much usage a call takes, mention that some people hang up on a virtual assistant, and complain about the new usage limits.

1. A routine every 15 minutes runs almost 100 times a day; merge quiet ones into one daily and one weekly check.
2. Duplicating a Bot keeps its settings, skills and routines but not its chat or memory, so write a handoff note.
3. Ten small messages cost more than one message with ten things in it.
4. Copy text or crop screenshots; turn long PDFs into text first.
5. Set a monthly limit on additional usage credits so a busy week can't surprise you.

Commenters: A small, mostly thankful group. Some share their own usage numbers and daily routine checks; a few point out that each reply resends the whole conversation, and some are frustrated with the limits.

1. Think of a team bot as an internal tool your whole team can use.
2. A simple one can review copy against your marketing rules.
3. Team bots can be tagged in Slack as well as used in Grok Bot.
4. Custom tools with your own API key can be connected.
5. Pair team bots with routines, such as checking Slack for missed mentions.

Commenters: Positive. Viewers wanted more setup detail and asked how team bots differ from regular bots and how sharing works.

1. pstack, by Lauren Tan, adds skills such as unslop and bro.
2. A Bot email address is one per account and the name is permanent.
3. Built-in X search needs no connector; there is a daily limit.
4. Keep the primary Bot as a manager, not a worker.
5. More Bots means more usage, so add one only when a job needs it.

Commenters: Positive. One viewer said their chief of staff Bot doesn't report back after delegating.

1. Mark one Bot as primary; it gets a star and is the one other Bots defer to.
2. Restart to update on desktop and update the phone app too, or new options won't show.
3. Tell your Bot it can read public X posts with the built-in tools, so it doesn't reach for paid API credits.
4. Example Gmail prompt: find a client email in spam from the last 7 days and list it first, without moving anything.
5. Search 'finance' in Connect apps to link accounts through Plaid for spending check-ins.

Commenters: A handful of comments. One viewer suggests a duplicate check when the same email can reach several Bots by different routes; others ask about Apple connectors and upgrading plans.

1. Write the role, tone and limits first; the Bot refers back to them on every run.
2. Ask the Bot to repeat its title, duties and handling of unverified sources before automating.
3. Connections are account-wide, so every Bot can use Gmail once it's connected.
4. Put the report format in a skill so a new topic keeps the same structure.
5. Share as template strips history, email addresses, IDs, tokens and keys before you publish a link.

Commenters: Mostly viewers listing what they'd track with it: grant opportunities, competitor launches, case law, agency client news and patent filings. One calls the multi-Bot hand-off the standout.

1. Have a guard Bot ask each Bot before it pauses or changes a routine.
2. Never delete: hide old Bots and pause routines instead.
3. Restart a very long chat by writing a handoff note into a fresh copy of the Bot.
4. Paste five no-small-talk rules into every Bot that talks to others.
5. Run the check weekly, supervised for the first two weeks.

Commenters: Small but positive: viewers thank him for the clear explanation and the free guide, and like hiding old Bots instead of deleting them.

1. Pages can hold callouts, to-dos, tables with tabs, filters and search, and charts; you edit them by chatting.
2. He turned 449 X bookmarks into a searchable Page his Bots can reference.
3. Payment cards must be in the Vault; 1Password is for logins and asks for approval each time, while Vault logins fill without a prompt.
4. His daily planner sets phone alarms for each meeting from his calendar.
5. Settings has a memory import: copy the prompt into ChatGPT or Claude and paste the result back.

Commenters: A handful of comments: a request to compare with ChatGPT's pages, a question about running out of usage, and a viewer who can't see the iPhone connections yet.

1. Grok Bot is a separate product from the Grok chat app; install the right one.
2. Set local execution to ask every time while you learn.
3. Once a tool is connected, a one-line request can create a Notion page or a LinkedIn post draft.
4. The Bot's own computer can test your website's sign-up flow; approve each step when asked.
5. Keep your profile, tone of voice and brand rules in a GitHub repository your Bots update, so the context is portable.

Commenters: Among the top comments: a team with a subscription that wants to learn it, and one viewer who uses Grok for phone screening, calendar and speech writing.

1. Use Grok Bot for quick, voice-friendly operational work across Bots that share one file system.
2. Group chats with many Bots can create back-and-forth that wastes usage.
3. Hook Bots into a structured tool such as Notion rather than relying on long chats.
4. Ask for a functional mock-up first before building a full app.
5. Keep your workflow tool-agnostic so you can pick the best tool per part.

Commenters: Viewers share hybrid setups, such as Claude for main work and Grok Bot as a personal assistant, or having a Bot install Claude Code in its terminal. Token use is a common worry, and one raises data privacy.

1. A page doesn't update itself; schedule a routine to refresh it.
2. Daily refreshes are usually enough; hourly updates use a lot more usage.
3. Pages can hold tables, charts, filters, switches and tabs, not just text.
4. Pages start private; personal accounts can share by link, team accounts with invited people or the whole team.
5. People you share with can use filters but can't change the page.

Commenters: One comment so far, praising how clearly it's explained.

1. Name and label is all a new Bot needs to start.
2. Ask a research Bot to verify against primary sources and flag claims that don't hold up.
3. Buying, sending, deleting and publishing stay behind your approval; ask-first beats allow when rules collide.
4. Teach a skill records you doing a task once and saves the steps.
5. Test runs can work on a copy so your real tracker stays clean.

Commenters: Few comments; one viewer says Grok Bot is the main reason they keep Cursor Pro, and others joke about the sponsorship.

1. The built-in Slack connection acts as you; Inkbox gives the Bot its own Slack account.
2. A webhook routine wakes the Bot when someone messages it.
3. Approve which teammates the agent can see.
4. Grok Bot's own Team Bots can also work in Slack, so check that first.

Commenters: Few comments: one asks whether two agents can talk to each other over Slack, another points out Grok Bot already connects to Slack natively.

1. Drafts, not sends: the client finder saves pitches in Gmail for you to read.
2. Sign into YouTube yourself in the Bot's browser before asking it to read your Watch Later list.
3. Make a builder Bot restate what you want and ask up to three questions before it builds.
4. A chief of staff can collect status from other Bots and hand the brief to a builder.
5. Bots share one computer, so files one Bot makes are there for the others.

Commenters: Only a few comments: thanks, and one viewer wishing the video had timestamps.

1. His expense Bot scans two inboxes for receipts and fills a Notion table, with a rule never to send or mark mail as read.
2. Teach a task turned a recording of a billing page into a reusable skill.
3. A daily standup group chat with six Bots, run by a morning routine.
4. Templates bring across instructions, memories, skills and plugins; installers connect their own accounts.

Commenters: Only a few comments. One viewer corrected the video: Bots share one computer, each with its own screen.

1. Create an MCP server in Zapier, add YouTube and select the tools the Bot may use.
2. If the connection fails, select tools from the link the Bot gives you, or rotate the token and paste the new details.
3. Ask for a ranked list with real quotes and likes, not a vague summary.
4. The same method works on any pile of raw text: Slack messages, email or CSV exports.
5. A weekly run over the last 7 days of comments can feed your content plan.

Commenters: Few comments; one viewer is tired of 'agent does everything' videos and wants to see real workflows without babysitting, another asks what makes it 'for pros'.

1. Give each Bot one job.
2. Attach context files so a new Bot knows your preferences.
3. Use the Bot's own email address for sign-ups, and your main email for real outreach.
4. Ask for a Page with a calendar view and have the routine keep it updated.
5. Import memories from other assistants in Settings.

Commenters: Only a handful of comments: one asks whether Grok Bot can summarise Teams meetings, another complains about usage.

1. Give each Bot one job, like a coworker with a clear role.
2. Put your rules in the first message; the Bot keeps them for every future brief.
3. Say 'run it once now' when you create a routine so you see the first result straight away.
4. For comparisons, insist on official pricing pages and no signing in.
5. Ask for a file you can share, and start with public web jobs before connecting apps.

Commenters: Two comments, one of them advice: start with one narrow routine, such as a daily price check that only messages you on a change, and run it for a week before adding more.

1. Voice chat starts instantly and works the same on the phone.
2. A local app's MCP server can be reached by giving the Bot a Tailscale Funnel address and port.
3. Keep the MCP token out of chat and configure it securely.
4. One Bot can ask another, like a Discord triage Bot, and report back mid-call.
5. A daily news Bot can fill a board with cards and draft posts for X, Bluesky and Substack.

Commenters: A few comments: the creator notes it works the same on his phone, and viewers ask for more app-building videos.

1. Copy a page link or open it in a browser to share it.
2. Ask for changes from the box at the bottom of the page; it tells you when the page has updated.
3. Pin pages from the Bot's Library so they're easy to find.
4. Pages can track things your platform's analytics don't show, such as which replies work best.
5. Point it at a dashboard you like and ask for a similar layout.

Commenters: A few short positive comments.

1. Ask the Bot to research X with filters like date and views.
2. Log the Bot into Uber Eats to reorder from your history or check spending.
3. Have it check Reddit for reseller complaints before buying tickets.
4. Give a budget up front for travel searches.

Commenters: Only a few short comments.

1. Ask your Bot to look at your whole setup and suggest where Pages would help.
2. A project page pulls from Notion and links back to each source item.
3. A spend page reads the coding Bot's session logs and estimates cost per run against a monthly budget. It's an estimate, not exact billing.
4. A newsletter page groups past emails by topic from their subject lines and sorts open and click rates.
5. A shareable team map shows each Bot's job, rules and approval points, and can act as a blueprint for rebuilding the setup.

Commenters: Only a couple of comments; one praised the team map for showing where approvals sit.

1. Give each Bot one job and let a Chief of Staff route work between them.
2. A note taker's webhook can wake a routine that reads and files each transcript.
3. Email triage can hand transaction emails straight to a coordinator Bot.
4. A Bot connected to an ads manager can launch, pause and report on campaigns.
5. You can share a working Bot as a template for others in your field.

Commenters: One comment, from a second-year agent who says the setup looks ideal for simplifying their own work.

1. A Bot with its own browser can test full funnels, not just read one page.
2. Ask for scores, top fixes and a click-by-click timeline.
3. Results depend on location; his ran from a UK IP.
4. Rerun the test on a schedule to catch flows that break.
5. A Bot's own email address can sign up to competitors' lists to see their follow-up emails.

Commenters: One comment so far, praising his website and resources.

1. Group project Bots into launch rooms with your chief of staff in each one.
2. Bots in the same room check each other's work.
3. Ask quick one-off questions in a general chatbot to keep your Bots' context clean.
4. Tell Bots that information you mark as new replaces the old version.
5. Keep sending email behind your approval while the Bot drafts.

Commenters: Only the creator's pinned link so far.

1. Each Bot keeps one long conversation and its memory, so you message it like a colleague instead of opening new chats.
2. Each Bot gets its own desktop on a shared cloud computer, so a login made once works for all of them.
3. Use connectors first and computer use where they fall short; the demo uses computer use to work inside Figma.
4. Teach a task: he builds one Google Form while the Bot watches, and it saves a reusable form skill. Skills save usage and give more consistent results.
5. Promote one Bot to chief of staff in a group chat with the others, then talk only to it.

Commenters: No comments on the official upload.

1. Your primary Bot can wake on its own to suggest work; tell it what you liked and it does more of that.
2. A meeting prep tip: ask for the context, the goal and the expected outcome, and ask what it thinks the outcome should be.
3. Team Bots can use personal plugins (each person's own Salesforce login) or shared ones, such as a read-only data key.
4. Team Bots can talk to each other in Slack, for example a deal desk Bot.
5. Connect X and 1Password from Connect apps; you choose which 1Password items the Bot may use.

Commenters: No comments on the official upload.

1. Team Bots: a colleague's Bot can join your team, and they push its skills and memory updates to you.
2. Group chats can mix your Bots and human teammates.
3. The fan-out method: one brief, three cloud agents on different models, pick the best.
4. Talk a plan through by voice, then ask the Bot to kick off a cloud agent.
5. A daily orchestrator skill reads the analytics, drops the bottom three, designs three new and deploys.

Commenters: Comments are turned off on the official channel.

1. Christa's Bot keeps CRM notes current from Granola, Gong, email and Slack and pushes next steps to Salesforce.
2. A Bot can watch a webinar or read a prospect's posts to find personal hooks for outreach.
3. Kevin's research Bot finds event planners at 146 target hotels and hands each lead to a drafting Bot; he reviews every draft.
4. His chief of staff Bot has its own email: his team forwards client requests and gets a draft quote back as a PDF.
5. His Bot's emails went to spam until he proved he owned the domain; the Bot fixed what it could and gave him links for the rest.

Commenters: No comments on the official upload.

1. A bug thread with a triage Bot, a reproduction Bot and two people went from report to merged fix in about an hour and a half.
2. Build a narrow reproduction Bot, publish it as a Team Bot, and teammates use it from Slack.
3. Add a skill each time you correct it; memory helps it pick the right skill later.
4. Use the Bot Development Kit (BDK) when you need deterministic routing, versioning and a trace of each run.
5. Bots can start Cursor cloud agents that use a prepared environment for your repo.

Commenters: No comments on the official upload.

1. Admins can allow or block plugins and MCP servers, disable single tools, turn local execution off and set a network allow list.
2. Team rules are added to every Bot's instructions, and auto-review rules can be enforced.
3. Audit logs, export of Bot actions to an OpenTelemetry collector, and spend limits per team or user.
4. Start with a pilot group, then widen with invite links. Team plans are on by default; Enterprise is enabled manually.
5. Team Bots keep shared memory in Slack and per-user memory in DMs, and use the connectors of whoever is talking to them by default.

Commenters: No comments yet on the official upload.

1. Promote a Bot with plenty of context to director and let it create and manage the Bots under it.
2. Talk to between one and seven Bots yourself; directors filter everything else to a weekly summary.
3. Ask Bots for proof of work and source links so their manager can check them.
4. He starts his mornings in his drafts folder, where his Bot has prepared replies, rather than his inbox.
5. For bugs, a cloud agent reproduces, adds a failing test, fixes and opens a pull request that waits for an engineer.

Commenters: No comments yet on this video.

1. Six steps, one Bot each: trends, the plan, the event page, events for account execs, outbound drafts and RSVP tracking.
2. Each Bot starts when the one before finishes, so a plan becomes a registration page and outbound drafts.
3. The RSVP Bot posts who's attending by account in Slack, answers 'has X registered?' and can approve by title.
4. Give Bots success criteria and examples of good output, then climb a trust ladder: show output, repeat, then automate.
5. Review your Bots weekly; one host runs a bot auditor routine that flags redundant Bots.

Commenters: No comments on the official upload.

1. Ask your Bot to claim an email, then use plus aliases to route each kind of mail to its own routine.
2. A Bot can have its own Google account made with its address, so you can share docs with it.
3. With 1Password, the Bot asks for a login on a card and the password is filled without the Bot seeing it.
4. Pages shine for charts, tables and filters; iterate a few times before putting one on a routine.
5. The team backs up Bot context to tools like Notion, Obsidian, Google Drive or a private GitHub repo.

Commenters: No public comments on the video yet.

1. Put sensitive, must-be-identical workflows in one admin-managed Team Bot that everyone's Bots ask.
2. Team Bots can use service accounts, Vault secrets and their own browser to reach internal tools with no API.
3. Auto Review runs a separate check on high-risk actions and can require a human yes.
4. Route regulated wording through a compliance-checking Team Bot with human review.
5. For long-term memory, the built-in memory works; repos or third-party memory connectors are options.

Commenters: No public comments on the video yet.

1. Describe the Clay workflow you want to your Bot instead of configuring columns by hand.
2. Pair Grok Bot for thinking and research with Clay for repeatable enrichment.
3. An event Bot can merge CRM contacts with new ones from Clay into a Google Sheet.
4. The Clay CLI on the Bot's computer can read a legacy table and rebuild it as a workflow.

Commenters: No public comments on the video yet.

1. Imported routines arrive paused; ask the Bot to turn them on and run them now.
2. You can rename a template Bot and change its icon.
3. The health check proposes skills, routine trims and new checks per Bot.
4. Dr. Eggbot asks for the core job, how often the Bot should wake, and sets anti-jobs.
5. Routine work that can run as a script on the Bot's computer is done that way instead.

Commenters: No comments yet on this video.

1. Test the Bot on one source before giving it the full job.
2. Cap the brief: up to three updates, under a word limit, so quiet days aren't padded.
3. Add a source status section so 'nothing new' and 'couldn't open the page' look different.
4. Keep a record of the last successful check so later runs don't repeat stories.
5. Check a routine's owning Bot, time zone and time before turning it on.

Commenters: No public comments on the video yet.

1. Clone a working personal Bot and convert the copy into a team Bot.
2. Decide which plugins, secrets, skills and memories the team gets.
3. Teammates can use the Bot without seeing the keys behind it.
4. Add it to Slack so the team can ask it directly.

Commenters: No public comments on the video yet.

1. Keep an X Bot read only and write your replies yourself.
2. Filter for posts that invite replies, are fresh, have reach and where you can add something.
3. Message only for Act now; everything else waits for the morning brief.
4. Have the Bot keep its role and rules written in Notion and update it when they change.
5. Use it as an editor: paste your reply and ask what could read badly.

Commenters: No public comments on the video yet.