Grok Bot Hands-On Guide: From Setup to Your First AI Assistant

Why Choose Grok Bot

The author used Hermes for several months as a personal AI assistant but found it lacking. After hearing that Grok Bot would use top-tier models like Opus 5.5, they decided to try it and found it indispensable. Grok Bot is defined as a Personal AI Bot, comparable to Meta Muse and OpenAI dots.

Key reasons for switching from Hermes to Grok Bot:

Overlapping positioning: Both serve as personal assistants; the author wanted to keep only one.

Simple and easy to use: Grok Bot starts fast, has a simple interface, and very low learning curve. Multiple bots can work in the same group or message each other to divide tasks.

24/7 cloud computer: Includes a cloud computer that stays online all day. Can also work with a local computer.

Convenient mobile control: The mobile app lets you view scheduled task results, chat with bots, and monitor group chats. If a local Mac mini is set to never sleep, you can remotely command the computer or access local files anytime for emergencies.

Scheduled tasks and scheduling: Once rules and output formats are set, it reliably reminds you daily or on demand.

The author notes that for focused coding work, dedicated coding agents like Claude Code or Codex are more efficient. Grok Bot's underlying model isn't fixed, so assigning coding tasks directly to it is currently less efficient than using a CLI directly. However, for handling miscellaneous fragmented tasks, this type of personal AI assistant is worth trying.

A new subscription tier has been launched; if a plan includes only X and Grok Bot, it would be the most cost-effective, as the current Grok model is still considered weak.

Quick Start

00 Download and Install

Download the desktop version for your platform from the official website. The new subscription bundles Grok Bot and Coding usage together, which may be less economical than the old separate quotas, but consolidating all platforms is a reasonable choice depending on needs.

01 Start with the Default Chief of Staff

After logging in, a bot named Chief of Staff is created by default. Practice using it first. The author recommends treating it as a manager bot: delegate all uncategorized miscellaneous tasks to it, and only have it create specialized bots when a specific job arises — no need to create bots manually.

02 Authorize Your Computer

The cloud computer stays online 24/7, but the author found the remote connection experience laggy and not very usable. They also advise against storing important files on the cloud computer due to risks of file loss and loss of access if the subscription lapses; only temporary files should be kept there.

To access a local computer, configure as shown in the accompanying screenshot. The critical step is instructing Chief of Staff on security and privacy rules: specify which directories it may read/write, forbid reading sensitive data like keys, and require immediate notification and sanitization if any key is accidentally read.

Additionally, set the Mac mini (or other machine running Grok Bot) to never sleep (7×24).

03 Connect GitHub Repositories

Important files should not reside on the cloud computer. Instead, store them in private GitHub repositories. Even if Grok Bot cannot reach the local machine, it can read files from authorized remote GitHub repos.

This is especially useful for bots that create routine tasks (scheduled tasks) needing to read files beyond just remembering rules. Authorizing GitHub access removes dependence on the local computer.

In the connect-applications dialog, select commonly used apps such as GitHub and Gmail.

Closing Thoughts

After using Grok Bot for a while, the author rarely opens Hermes anymore. Grok Bot can modify code and run tests, but for coding the author still prefers dedicated coding agents like Codex and Pi. They delegate topic selection, publishing, and note organization to Grok Bot, reserving their energy for higher-priority work. The next article will cover how these bots divide labor and collaborate in groups.