Engineering

Botski helps people get better work from Grok Bots. Guides, workflows, and Plan your bot.

What Grok Bot is: named AI agents, each with a persistent cloud computer. Platforms, shared-computer basics, and a safe first task, from official docs.

Sign-in, access, and action approval are different. How Grok Bot asks first — Auto Review, prompt injection, secrets, shared-computer privacy, and Teams.

Calm recovery when a Grok Bot goes quiet: check approvals and the computer, Stop now, reopen the app, Recover before Reset. Official docs win.

How a quick chat differs from a Grok Bot that keeps a job and a cloud computer.

Cloud work can continue after you close the app. What still waits, and how that differs from a coding session.

Save a working method as a skill, then schedule a routine. Test before you enable.

Stop now, check approvals and the computer, then Recover before Reset.

Plain pattern for clear Grok Bot instructions: result, sources, what to ask first, timing, example.

A simple scheduled Grok Bot job: check one URL and send you a short digest.

Templates are recipes, not clones: others get your setup, not your computer or history. Strip API keys, customer data, and internal URLs before you share.

Write what your Grok Bot must never do without you — sends, spends, deletes, public posts.

Short path when a bot stalls: Stop now, reopen the app, Recover before Reset.

Templates are checked automatically, and anyone can report one. Ribbons show who made it. Templates open on x.ai.

Secondary tools Grok Bot builders often need, plus scenario cards for common builds. Ballpark costs — check vendors.

A Grok Bot template copies configuration: identity, description, skills, and routines. It does not clone the computer, logins, or history.

After you add a Bot, read what landed, remember it shares your computer, and run one small task before any routine.

A Grok Bot share link can fail or no longer match what you were told. Read the preview. bot.ski does not invent template ids.

Three doors: the public Bot Marketplace, plugin shelves, and a template recipe. Grok Build’s plugin marketplace stays separate.

Who can open Grok Bot, and what the preview add control does. No prices. The plans page and the docs FAQ disagree on stacking.

A field note on the public Haggle Bot listing: the job, the refusals, and what Botski does not install.

A new Grok Bot feature can appear in the app before any official page explains it. Here's how Botski wrote up Primary Bot, plus a checklist you can reuse.

When a Grok Bot opens a file for you, it doesn't pick the app. The computer it's working on does.

Your bot's cloud computer never sleeps, but a PC you've registered can. Here's how to tell which jobs need it and what to do when it's offline.

What deleting a Grok Bot removes, what stays on the shared computer, and how a bot.ski directory card is separate.

Understand conversation context, saved memory, retrieved files, and summaries so your bot has the right information for the next step.

See how a bot can find relevant passages before answering, why retrieval can fail, and how to check the evidence behind a reply.

Understand input and output tokens, context capacity, and usage limits without confusing AI tokens with passwords, design values, or credits.

Review an AI bot's proposed website change by checking its purpose, destination, preview, changed files, and evidence before accepting it.

Understand why Git changes conflict, how to ask a bot to resolve them, and how to choose a recovery plan that preserves other people's work.

Understand APIs, connectors, plugins, webhooks, and MCP through one simple order-tracking example, including access and approval.

Learn what Model Context Protocol does, how it relates to APIs, and why a compatible connection still needs permissions and testing.

Follow a simple website from its address to a saved RSVP. Learn what runs in your browser, what happens on a server, and when a database is needed.

Understand domain names, DNS records, nameservers, hosting, and HTTPS. Learn how a preview becomes a live website and what to check after publishing.

Understand the method, the schedule, and the whole job, with a practical Grok Bot example and a clear way to test before automating.

"Practical Grok Bot tricks from popular creator tutorials, each checked against the official docs: get past site blockers, Projects, Slack approvals and more."

Ask your Grok Bot to launch new features with the switch off, back up before data changes, ask for a separate yes on each risky step, and turn on less at launch.

When your Grok Bot ships a change you didn't want, ask for a clean revert first, turn your objection into a written rule, then redo the change through normal review.

Acceptance criteria are the specific conditions a result must meet before you treat the task as done.

Agentic AI describes systems that work toward a goal by choosing steps, using tools, and adjusting to results within the access and limits they are given.

An AI model is the trained system an application uses to make predictions or generate responses.

An AI token is a unit a model uses to process content. For text, a token may be a word, a word fragment, or punctuation.

An API key is a credential an application sends so an API can identify or authorize the caller.

An application programming interface, or API, is a defined way for software to request data or actions from other software.

Artificial intelligence is software that performs tasks associated with human abilities, such as recognizing patterns, understanding language, and making predictions.

Auto Review is Grok Bot's automated check of proposed tool calls and computer actions before they run.

Automation is software carrying out work according to rules or triggers, so a person does not repeat the same action by hand.

A clone is a new copy of a Git repository, history included, created in a new directory.

A cloud agent is an AI coding agent that runs on a computer the vendor hosts, instead of only on the machine in front of you.

A coding agent is an AI agent that works on software tasks by reading a project, changing files, and using development tools, then preparing the changes for review.

A commit records a project state in Git, plus history information such as the parent commit, the author, and a message.

Recover saves what it can, then rebuilds the Bot computer from your saved data. Installed apps are removed.

Reset rebuilds the Bot computer from your last saved data. It is the last resort and can lose very recent changes.

Computer takeover is when a person takes manual control of Grok Bot's Agent Computer to finish a step, then returns control to the Bot.

A merge conflict happens when Git cannot automatically reconcile competing changes.

A context window is how much content a model can handle at once, measured in tokens, with limits that depend on the model.

Continuous integration is the practice of committing code to a shared repository often, and building and testing those commits so errors show up sooner.

Conversation history is the record of earlier messages, and in some products tool activity, that an app saves so you can reopen or search it.

Cursor is a coding agent for building software: you use it to understand a codebase, plan and build features, fix bugs, and review changes.

To deploy is to make a version of software available where it can run or be served, such as a preview, a test system, or production.

Disk Saver is a built-in Bot that checks what is using space on the Bot computer and suggests cleanup. Nothing is deleted unless you confirm.

A draft is work that is not finalized yet.

A draft pull request is a pull request shared as work in progress. GitHub's docs say it cannot be merged, and code owners are not automatically asked to review it.

The frontend is the part of an application that people see and use, usually in a browser or on a device.

Git is a version-control tool that records changes to files and helps people combine work over time.

GitHub Actions is GitHub's continuous integration and continuous delivery platform. It automates checks such as building and testing a pull request.

Grok is xAI's assistant for conversation, writing, and working with files you upload, on the web and in its mobile apps.

In Grok Bot, a Project is a Cloud Agent a Bot starts for a big job. It plans the work and runs its own agents.

In Grok Bot, a secret is a key or credential saved in a masked, write-only field. Bots can use it, but the value is never shown again.

A group chat is one conversation with several of your Bots. Bots answer in the group, and @name sends a request to one Bot.

A hallucination is AI-generated information that is false or unsupported even when the response sounds confident.

A handoff passes a piece of work to the next person, bot, or session, with the notes needed to continue it.

Force the browser to reload files from the server, not from its cache, so you see the newest version of a page.

A headless browser is a web browser that runs without showing its windows, so a script can load pages when nobody is watching the screen.

Hosting is providing the computers that keep a website or application available to the people who use it.

A large language model is an AI model trained on large amounts of text and other data to understand and generate language.

A memory file is a file a coding agent loads at the start of a session so instructions or notes from earlier work are present again.

A usage limit is a cap on how much of a service you can use.

A migration is a controlled change in the structure or location of data or content.

A migration rollback undoes a change to how stored data is structured, or records that a failed change was undone.

Model Context Protocol is an open standard that lets AI applications connect to external tools and information through compatible servers.

Model routing is Grok Bot choosing a model for each task, from xAI or a third party, instead of letting you pick one.

Muse is Meta's personal AI agent for carrying out tasks across apps and websites a person connects.

The Muse Secure VM is Muse's dedicated cloud computer, with its own file system, terminal, and browser.

Sentinel is a separate Meta agent that checks Muse's outbound internet actions before they happen.

Muse Spark is the family of AI models from Meta that powers the Muse assistant.

On-demand usage is paid usage after your weekly included usage runs out. You can cap it with a monthly limit.

A one-liner is a command or a small piece of code written on one line.

Parallel means more than one job is progressing at the same time.

A plugin is an optional piece of software that adds a feature to a larger application.

A reduced-motion preference is a person's request for less animation. The CSS prefers-reduced-motion query lets a site detect that request and respond.

Primary Bot is a role the Grok Bot app introduces for your go-to Bot, one that works proactively on everyday tasks and checks in when it needs your help.

A proactive assistant offers help or starts permitted work without waiting for a new message each time, for example on a schedule, after a change, or toward a goal you already gave it.

Prompt injection is an attempt to make an AI follow untrusted instructions instead of the task and rules it was given.

A queue is work waiting to be processed.

A rate limit is a restriction on how many requests, or how much work, a service accepts in a period.

A repository is a project's stored files and their recorded change history, commonly managed with Git.

Route traffic through this computer is a setting that sends the Bot computer's web traffic through your own connection, so sites that block cloud computers see you instead.

In Grok Bot, a routine tells one Bot when to run a workflow: on a schedule or, where supported, after an event. A test of a routine does real work.

A Secure Form is a chat card that opens a window for a login or other form, showing the site's name and icon, so you fill it in without handing over the screen.

A SHA is the identifier Git gives one commit, so people can name that exact recorded snapshot.

In Grok Bot, every Bot on an account uses the same cloud computer. Files, browser sessions, and command-line credentials on it are shared.

The Shopify connector is a plugin that connects a Shopify store so a Bot can check orders, track inventory and update listings.

A sidebar section is a named group in the Grok Bot sidebar for organizing Bots by project or client. Sections sync between devices.

A snapshot is the set of file contents Git recorded at one moment.

A spending limit is a cap on how much money an account is allowed to use with a service.

The sub-processor list is the official list of outside providers that may process your data, including the model providers Grok Bot can use.

Tagging @bot means mentioning @bot in an X post or reply to hand that post to your main Grok Bot as a task.

A technology stack is the combination of languages, frameworks, databases, and services used to build and run a product.

Tool use is an AI system's ability to request an action from connected software, such as searching files or running code.

Voice chat is a live spoken conversation with one Bot. It talks back until you hang up.

Voice typing turns what you say into text in the message box, for you to edit and send. The Bot replies in text.

A workflow is a connected sequence of steps that takes a task from a starting input to an intended result.

A worktree is an additional working folder attached to the same Git repository.

A Grok Bot is a named AI teammate you keep around. It has a job, its own conversation, and context that builds up over time. It works on a persistent cloud computer with a browser, files, and a terminal, so tasks can finish in real tools instead of only as chat drafts. You message it with the task, the context, and the access it needs. It comes back when something needs your approval.

Install the official Grok Bot app, then sign in. Desktop builds are for macOS, Windows, and Linux. There is also a companion app for iPhone, iPad, and Android. Official get-started says to open the Grok Bot downloads page and choose the download for your computer. Sign-in uses a Cursor account. If your access comes from an individual SuperGrok or X Premium+ subscription, link that account when the app asks. bot.ski does not host an installer, and this page does not name a download file. Get Botski on this site stays empty until a real installer exists.

Official FAQ lists macOS on Apple silicon and Intel, Windows on x64 and Arm64, and Linux on x64 and Arm64 as a deb package, an rpm package, or an AppImage. Mobile is iPhone on iOS 18 or later, iPad on iPadOS 18 or later, and Android 9 or later. The same Bots and conversations sync across signed-in devices. The computers the Bots work on run in Cursor’s cloud, not as a local virtual machine you install yourself.

Give one Bot one primary job. Official get-started says a strong first request names five things: the outcome, the sources, the constraints, the deliverable, and the point where it should stop for you. A five-minute start that needs no website login is to attach a document and ask for five bullets, a separate list of every date, decision, and open question, a citation for each item, and a rule not to change the source file. Put standing rules in the Bot description, such as never sending without approval. Put this task in the message. Plan your bot on bot.ski can write that prompt. It does not start a Grok Bot or install anything.

No. Botski is an independent project. These pages are not official xAI documentation, and Botski is not endorsed by X, xAI, or Grok. The FAQ is prepared text. It is not a live chat model, and it cannot install a Grok Bot, start one, or speak for xAI. When a product fact matters, use the official docs named after the answer.

It depends on the tool, the risk, and your Auto-review rules when those are turned on. Official FAQ says sensitive or consequential actions can stop for approval. Put standing boundaries in each Bot’s description, and add narrow ask-first rules for sending, publishing, deleting, purchasing, or changing production systems. Passwords, two-factor codes, CAPTCHA checks, and similar human-only steps use a computer takeover. You type those yourself. Do not paste them into chat. A test of a routine is still real work, so keep writes behind that same approval line.

Deleting a Bot removes its active profile, conversation, and routines from Grok Bot. Because Bots share a computer, files and sign-ins on that computer may remain. Official FAQ says backend retention follows the applicable Cursor terms. If you might need the work later, hide the Bot instead of deleting it. Hiding removes it from the main sidebar and does not pause the Bot or its routines. Open Hidden Bots to unhide it. Deleting a routine by itself is immediate and has no undo.

Post as the Slack user you connected, only in channels that user can post in. It cannot post in a private channel that user is not in.

Named on the official Connect plugins page so agents can use Notion in chat. Public docs do not list specific Notion actions yet.

Named as a Connect plugin, but official docs say it cannot be connected until Zoom authorization is fixed.

On October 15 Elon Musk told people to ask their Grok Bot to remove their phone number from spam call and text lists, quoting a free third-party skill by Arash (MinimalDuck). Here's what the skill does, how to add it, and a few safety notes.

An email that really came from noreply@x.ai carried a fake “Accept invitation” button, and every authentication check passed. A Grok Bot spotted it. Here is what went wrong, why the checks could not catch it, and how to put your own Bot on email watch.

You can only claim one Grok Bot email address, but plus aliases let it act like several. Send and receive on an alias, and set routines that only run for mail to that alias. Here's how to plan aliases, set them up, and avoid the rough edges.

Builders are asking their Bots to install the Claude Code and Codex CLIs, sign in once, and route writing and coding work to those subscriptions. Here's how it works step by step, what the vendors' own docs say, and the caveats nobody mentions in a tweet.

X is quietly paying some creators when others use their shared Grok Bot templates. What the pilot terms say, who's eligible, and how payouts work.

People handed tax returns and forms to Grok Bot. Here's what they tried, a prompt you can reuse, and why a human CPA stays in the loop.

On October 10 Nicki Minaj talked about Grok Bot at the X Takeover, and Grok Bot lead Lauren Tan asked people what they got done with @bot this week. Here's what was said, with links.

On October 4 Elon Musk pointed people at a community guide on hiring your first Grok Bot. What he posted, the guide he quoted, and what official docs say about a first job.

Creators noticed Opus showing up in Grok Bot. The official help page explains that Grok Bot chooses a model for each task, that you can't pick one, and that it doesn't change your per-token cost.

A dated timeline of every Grok Bot development from October 1 to 10, with links to our full write-ups.

Official skills-and-routines guidance: prove the job once by hand, save a skill, then attach a routine. Automating a broken one-off only repeats the mess on a clock.

Official chat and collaboration docs describe Bots talking to teammates. Treat those messages like real side effects — useful for handoffs, noisy if every Bot pings every other Bot.

When my Bots' shared computer filled up, a Grok Bot helper called Disk Saver showed up on my team, checked the disk read-only first, sorted safe from risky, and freed space without breaking any of my sites. Here's what it did both times, and what I learned.

Official sharing terms and template guides: Add/Import copies description, skills, routines, and first-party plugins. It does not copy the shared computer, logins, private files, or chat history.

Official docs say a routine can run on a schedule or when an event arrives, even while you are gone. Saving a skill first, then wiring the routine, keeps the repeatable work honest.

Official order is one successful pass, then a saved method with sources and the approval rule, then a schedule. A skill is how. A routine is when. Missing source data should report failure, not reuse old data.

Official docs want allowed actions and wait-for-you actions in the first message. Passwords, passkeys, two-factor codes, CAPTCHAs, and payments are take-over steps on the Agent Computer — not chat text.

Serio’s Icon Studio taught the capsule-eyed look; Shub wrapped it as Pfp Bot on the Marketplace. Community project — not an official Botski bot — with the posts, screenshots, and how to try it.

Official docs put files, browser cookies, and signed-in sessions on one persistent machine. Separate Bots are not a privacy wall. A job that needs its own logins needs its own Cursor user.

Official get-started still asks for an eligible paid plan or a linked individual SuperGrok account, plus the official app. SuperGrok Lite and team SuperGrok plans do not open Grok Bot.

Official pages treat Grok Bot as a named teammate with a cloud computer, not a louder chat box. The first beginner mistake is asking it only for text.

Your X history as a reel