Cursor/xAI personal agent (Bots on persistent cloud computer; desktop+mobile)
Official source ↗ · Source checked 2026-10-25
Check official pricing and availability. Model versions must be checked in each case.
These labels share this page. Original identifiers are preserved; versions may differ in capability or availability.
541 tag-associated cases; tool roles have not all been reviewed. This is not the product’s full capability range.
Latest case update：2026-11-02
Put result, audience, source material, guardrails, and done-state in your opening message
No extra tools or setup needed. Open a Grok Bot conversation, fill in the five-element structure in your first message, and send. Works for any text-generation or editing task.
Grok Bot
Associated by case tags. Verify costs, permissions and actual results in the case.
Start from Gmail, gradually connect calendar and custom apps, build a multi-Bot team for daily tasks
Requires The X Subscription Premium ($30/month) or higher. Needs account access for Gmail, Google Calendar, etc. Custom apps require self-developed MCP endpoints. Slack connection has a known issue (may show Salesforce card). Start with one tool and expand gradually.
Grok Bot
Associated by case tags. Verify costs, permissions and actual results in the case.
Create a dedicated Bot in Grok Bot → enable ChatGPT device-code login → install Codex on cloud or call local instance → assign tasks or chain to GPT Image
Source: X user @AndyCui0's summary of a video tutorial cross-checked with OpenAI docs; author verified codex-cli installs on cloud and codex login --device-auth exists. Requires: Grok Bot account, ChatGPT account (personal: enable device-code login beta; workspace: admin-enabled), optional local Codex CLI or cloud environment. Costs: Codex usage may incur OpenAI API/subscription fees; OpenCode is MIT-licensed and free but third-party models may cost extra.
Grok Bot
Associated by case tags. Verify costs, permissions and actual results in the case.
A 4-step follow-up loop to give Grok Bot code ownership, drive cloud agents, verify evidence, and maintain a task board
Requires Grok Bot access, a code repository (e.g. GitHub/GitLab), Cursor cloud agent environment, and CI/task board tooling. Source does not specify credential setup or cost.
Grok Bot
Associated by case tags. Verify costs, permissions and actual results in the case.
Input: Ask @grok on X for the next episode plot → Process: Grok Bot runs a 6-step pipeline (script / consistency lock / generation / assembly / QC / publish) → Output: Daily AI anime episodes distributed across platforms
Prerequisites: X account, YouTube channel, TikTok account; access to Grok Bot and Grok Imagine. A human retains final approval: new characters and ideas require a person's OK, TikTok videos are posted manually from a phone, and articles are approved before publishing. Cost and permission details not stated by source.
Grok Bot
Associated by case tags. Verify costs, permissions and actual results in the case.
Input: multiple Grok Bot Agent conversation states → Process: aggregate into a four-panel dashboard in Pages → Output: one-screen view of waiting, in-progress, finished, and timeline with filters
Requires a Grok Bot account with the Pages feature enabled. Create a new Page in the Grok Bot interface and add four sections matching the author's panel fields. No additional cost information available.
Grok Bot
Associated by case tags. Verify costs, permissions and actual results in the case.
Input: research question; Process: Codex calls Grok Bot's built-in X tools via BDK MCP or Cloudflare Worker bridge; Output: structured search results with original post links and summaries
Requires: Grok Bot account (with Bot creation permission), Cursor account (for BDK login), Node.js ≥22.13, npm; Webhook option additionally requires Cloudflare account and Wrangler. BDK path needs a local persistent Node process; Worker path requires deploying and maintaining a Worker, D1, and callback scripts. Grok Bot quota: 1,000 calls/day, 30 calls/minute built-in X tool usage.
Grok Bot
Associated by case tags. Verify costs, permissions and actual results in the case.
Open Grok Bot on phone → authorize GitHub repo → describe feature in natural language → Cursor cloud agent writes on a branch and opens PR → confirm to deploy
Requires: Grok Bot app, GitHub account, existing code repository. No need to leave a home computer on. Actual coding is done by Cursor cloud agent in the cloud, submitted via PR, and requires manual confirmation before merge. Authorization flow depends on Grok Bot's popup at the time of use.
Grok Bot
Associated by case tags. Verify costs, permissions and actual results in the case.
Input: CI build failure job and summary; Processing: POST to Grok Bot Webhook Routine; Output: structured conclusion in Phenomenon / Possible Cause / Suggested Check format
Prerequisites: a working Grok Bot account; an environment capable of sending HTTP POST (curl, Java, CI scripts). Cost and permissions: no extra fees mentioned; Webhook secret must be kept secure. Boundaries: HTTP 200 only means the task was accepted and started, not completed; rate limit is unpublished; deduplication must be arranged in the instruction itself.
Grok Bot
Associated by case tags. Verify costs, permissions and actual results in the case.
Input: writing requests, GitHub repos, product ideas → Processing: role-based bot review and collaboration → Output: safety-checked drafts, research briefs, launch plans
Requires a Grok Bot account; no additional API costs mentioned. Author recommends starting with one repeated task and adding bots gradually.
Grok Bot
Associated by case tags. Verify costs, permissions and actual results in the case.
Send one prompt → Grok Bot generates a "memory room" image based on your X activity → see how well it knows you
No setup needed. Open a Grok Bot conversation, send the specified prompt, and wait for it to generate a room image with description. Results depend on the breadth of your prior interactions with the bot.
Grok Bot
Associated by case tags. Verify costs, permissions and actual results in the case.
Export usage CSV → audit routines → add change checks → one job per chat with file-based state
Requires a Grok Bot account (Premium or higher), permission to export Usage CSV from grok.com/dashboard, and permission to create/edit routines. No extra fees, but involves quota-management operations.
Grok Bot
Associated by case tags. Verify costs, permissions and actual results in the case.
Review and enable Grok Bot's email, Vault, Pages/slide output, plus Auto-review and Routines/Skill limit changes
Check three updated areas in the Grok Bot interface: identity and credentials (email, Vault, payments), deliverables (Pages, Slide deck), and automation strategy (Auto-review, Routines/Skill limits). No prompt is needed—follow the in-app guidance. When entering login or payment details, confirm the platform's security measures first.
Grok Bot
Associated by case tags. Verify costs, permissions and actual results in the case.
Notes from Stanford CS146S: amend-in-flight tasks, DM priority, one-shot skills, meeting delegation, and work-log queries
Requires Grok Bot access; some features (meeting attendance, Slack/email integration) depend on team or enterprise-tier configuration. Source does not specify exact pricing or version requirements.
Grok Bot
Associated by case tags. Verify costs, permissions and actual results in the case.
Input: your actual workflow and recurring tasks → Process: use Grok Bot to generate a named-role bot squad configuration → Output: role map, shared directory conventions, pipeline rules, and self-check checklist
Requires access to Grok Bot or a similar Personal Agent. No extra cost is stated. You must maintain the directory structure and bot role descriptions yourself; hard boundaries must only be tightened, never relaxed. The original text does not specify how directories are implemented (file system, cloud drive, or bot memory); adapt to your own environment.
Grok Bot
Associated by case tags. Verify costs, permissions and actual results in the case.
