No-Code Agentist

Anthropic released 10 finance agents for Claude. Research, modeling, valuation, accounting, and KYC are now packaged into ready-to-use workflows. Available across Cowork, Claude Code, API, and Microsoft Office. Get the agents here → https://t.co/27YVpE32Me Here’s how to set them up in 4 steps: 1. Install in Cowork • Open Settings → Plugins → Add plugin • Paste the financial services GitHub repository • Pick the agents you want from the list 2. Install for Microsoft Office • Open the GitHub repository above • Copy the Microsoft 365 installation command into Claude Code • Run /claude-for-msft-365-install:setup • Follow the setup steps to finish the installation Claude supports Excel, PowerPoint, and Word through Microsoft 365 add-ins. Outlook is coming soon. 3. Connect your financial data Claude’s finance ecosystem connects to market data, research platforms, and internal financial systems. Some of the biggest names include: FactSet · S&P Capital IQ · MSCI · PitchBook · LSEG · Morningstar · Daloopa · Moody’s There are also additional connectors for research, risk, diligence, and financial data. Anthropic says Claude connects to dozens of market data, research platforms, and internal systems. 4. Pick the agent that matches your workflow Research & Client Coverage → Pitch Builder → Meeting Preparer → Earnings Reviewer → Model Builder → Market Researcher Finance & Operations → Valuation Reviewer → General Ledger Reconciler → Month-End Closer → Statement Auditor → KYC Screener There are 10 agents, but you probably only need one or two. Pick a workflow you already spend too much time on and start there. Official sources: → https://t.co/XHtXcP6FaI → https://t.co/oazpv7afcs → https://t.co/27YVpE32Me Save this for later. Repost ♻️ if someone on your team should see it.

GROK BOT HOW TO USE WHAT NEW TODAY - Folder still 840 posts (2 new since Sep 4; same total = churn) - Testers (mattyp): Grok Bot is now available for iPad - Testers (AlexFinn): Grok Bot coding workflow — pair a developer Bot (spawns Cursor cloud agents / PRs) with a PM Bot (Notion or Linear board, permissions, task feed). Software-factory loop; give the post to your chief-of-staff Bot to set it up WHAT IT IS - A Bot is a named, persistent teammate, not a one-off chat - You message it like a coworker and it finishes work in real apps - All of your Bots share one cloud computer (browser, files, terminal) - Each Bot has its own screen on that shared computer - Work keeps going when your laptop or the app is closed - It only comes back when it needs approval or a human step - Do not confuse Grok Bot with Digital Optimus (real-time video human emulation) - Testers (joehansen): do not confuse Grok Bot with an X Chat Agent (an X account you add to a group chat). Grok Bot is the machine that does the work - Official Elon: Your Bot will identify issues to resolve, notify you when they are fixed, and continue on with your project ACCESS AND INSTALL - Official bot (Aug 26): All SuperGrok and Cursor Pro subscribers now have access - Testers (mattyp): Grok Bot is free to try; every Grok & Cursor plan includes Grok Bot - Testers quoting SpaceXAI (cb_doge): SuperGrok, SuperGrok Plus, SuperGrok Heavy, Cursor Pro, Cursor Pro+, Cursor Ultra, Cursor Teams Standard and Premium - Cursor CEO Michael Truell: everyone with a standard Grok or Cursor subscription - Testers: included at no extra cost with those plans; circulating plan prices $20/month Cursor Pro and $25/month SuperGrok (nextbigfuture) - Official bot + Elon: weekly / free usage limits reset for all Grok Bot users - Sign in with your Cursor account (that account owns plan and usage) - Official desktop download: - Also listed at - Official desktop is macOS and Windows (Apple silicon or Intel; Windows x64 or Arm64) - Testers (mattyp): Linux is now supported (official docs may lag) - iPhone: iOS 18+, App Store app "Grok Bot" - Official (bot, Sep 2): Grok Bot is now available on Android - Testers (mark_k): install from Play Store; full Grok Bot experience on Android - Play Store: - Official docs may still lag on Android; Testers (mattyp, Sep 4): Grok Bot is now available for iPad - SuperGrok Heavy users can choose Get access with SuperGrok Heavy, then Link Grok Account - Linking SuperGrok Heavy can unlock free Cursor Ultra (one Grok account to one Cursor account) - Legacy Privacy Mode blocks Grok Bot; switch to a supported Cursor data setting first - Grok Bot checks for updates automatically; Check for Updates is in Settings → Beta - Official Elon (Sep 4): Grok Bot Enterprise is now available - Testers (mark_k, Sep 3): Version 0.36.0 is now live — bugfixes and improvements - Testers (mattyp, Sep 4): iPad app available (official docs may still lag) SIGN IN [] Desktop: Get started, then Sign In with Cursor in the browser [] iOS: Login with Cursor, finish in the browser, return to the app [] Official: Cmd-D turns on voice dictation [] Official: it is easier to use the remote computer from your phone [] Use the same Cursor account that should own usage [] First-run tour asks which tools you use; that only shapes teammate suggestions [] Computer setup runs in the background, then Meet a future teammate opens CREATE A BOT [] New in the sidebar, or Cmd/Ctrl+N [] In New chat, choose Create new agent [] Edit Profile: name, title, description, avatar [] Give a short name, one primary job, and how it should work [] Description = standing rules (never send without approval) [] Chat messages = this-task instructions (draft follow-ups for these 12 accounts) [] Focused Bots beat one catch-all General Helper [] Testers (XFreeze): do not design a Bot from scratch; ask a Bot to create a capable one for you (it already has your context) [] Bookmark testers: start with about six roles; give each Bot recurring work [] Pin important Bots; hide unused ones (hiding does not pause routines) [] Bookmark testers: resize the sidebar, give titles, and group Bots into sections [] Duplicate a Bot to reuse a role for a new scope (copy does not include memory or history) [] Delete only if you are sure; files and logins on the shared computer stay [] Account limit: 50 Bots and group chats combined [] Name language can steer reply language (bookmark testers reported this) [] Bookmark testers: no model picker yet; testers still list voice mode, BYOK, multiplayer, and hang-error messages as missing (iPad now available per mattyp) [] Testers (XEthanai / XFreeze): shareable Bot templates - build once, fine-tune, share the full setup for others to use or customize [] Testers (XFreeze): Marketplace coming - browse specialized Grok Bots by category and add them to your team [] Testers (RoundtableSpace): Marketplace framing — hand-picked bots by category with routines/workflows built in (app store for AI teammates) [] Testers (kloss_xyz): 8 official-ish bot templates (calls, X, writing, images, coding, networking, tool testing, parking tickets) HOW TO WRITE A TASK [] Outcome: what should be finished [] Sources: which apps, sites, files, or chats matter [] Constraints: what it must not do, or must ask first [] Deliverable: what it should return [] Review point: when it should stop for you [] Safe first task: attach a file and ask for a cited summary; do not change the file [] Next task: one real tool, read-only, with a sign-in handoff if needed [] After a good result, name the lasting format preference in chat [] Then save it as a skill or routine [] Official bot examples: email cleanup, Starlink-likely flights, build a site then buy the domain and deploy, meeting notes, sales prospecting, refunds, podcast audio digest [] Testers: paste a viral video link and ask the Bot to recreate it [] Testers: start from an org chart or make one Bot the boss of a repo, not a long to-do list [] Testers: one clear job, explicit allowed sources, no-guessing rule, approval gate before any real action [] Testers: 5 calibrations - confidence threshold, checkpoint long tasks, show negative examples, gate destructive actions separately, test edge cases first [] Testers: one Bot, one job - two jobs claimed worse at both; put recurring work on a schedule [] Testers quoting claimed SpaceXAI employee: version prompts and tool configs like code; scratchpad separate from the user-facing answer; retry with a different strategy; measure cost per successful outcome; review failure logs on a schedule [] Testers (mvanhorn): Compound Engineering - force a plan first; three-layer instructions (base, role, current focus); screenshot instead of retyping what's on screen; ping only on a real hit [] Testers (AlexFinn): anything you are about to do on your computer, ask Grok Bot first [] Testers (AlexFinn): example week - Reddit microSaaS, 3D digital office to watch Bots, Omarchy setup, product returns, daily AI news post, Cursor cloud-agent bug fixes, X model-release watch, brand-deal negotiation, contract redlines [] Testers (Michael_Fenech_): give it business responsibilities (checking, chasing, updating, coordinating), not just questions AGENT COMPUTER AND LOGINS [] Open Agent Computer from the conversation to watch the desktop [] Take over for password, passkey, 2FA, CAPTCHA, payment, or human-only pages [] Complete only the blocked step, then return control [] Never paste passwords or one-time codes into chat [] Use a secure secret request when the app offers one [] Browser sessions persist and are shared across all your Bots [] Prefer a connector/plugin when one exists; use the browser when it does not [] Testers (SamSokolin): for repeated web-app clicks, reverse-engineer browser-use into scripts (capture network once, call APIs next) [] Keep durable files in /workspace with clear project folders [] Settings → Beta: Update Agent Computer (preserve state), Recover, or Reset (can lose recent work) [] The cloud computer is not your Mac or Windows machine [] Local-computer execution is separate: Settings → General → Agent → Execution on Local Computer [] Default local policy is Ask every time; use Never allowed unless you need local files [] Bookmark testers: give a Bot full local Mac/iMessage access only on a spare machine [] Testers: local Mac access can write local Python scripts on your Mac [] Testers (Av1dlive / mvanhorn): Claude Code, Codex, and Cursor claimed runnable on the Bot's own computer [] Testers (XFreeze): take over that same cloud computer from your phone without being at the laptop [] Testers (Damir_Akaza): group-chat Bots can reach a local Mac Mini via Tailscale for project files and local scripts [] Testers (farzyness): a Bot can exclusively use Grok Build in CLI with the latest Grok models at highest thinking [] Testers (AlexFinn): a 3D digital office on a second monitor to watch Bots work PLUGINS AND CONNECTORS [] Settings → Plugins, then Add, then authenticate in the browser [] Grok Bot team (poteto): tinkabot helps build MCP/skills plugins and submit them for approval so all users can use them [] Type @ to attach a connector; type / to reference a saved skill [] Installed connectors are account-wide, not isolated to one Bot [] Official: you can connect multiple accounts to the same plugin [] Official bot (Aug 26): SuperGrok and Cursor Pro now included; weekly limits reset. Testers quoting SpaceXAI: also Plus/Heavy/Pro+/Ultra/Teams [] Testers: give a Bot its own email address so it can send and receive on its own [] Testers (mvanhorn): give a Bot its own inbox, not your Gmail (one mistake should not flag your domain); Twilio number so a Bot can make calls [] Testers: app v0.23.0 adds creating new channels [] Official bot: improved X support - connect your X profile; a developer account is auto-created with included credits [] Testers (blankspeaker): Plugins, add X, authenticate; $100 in X API credits good for a year (new and existing devs) [] Testers (GrokInsider): if credits did not land, ask Grok Bot to connect X so the Authorize card opens the browser; tester's manual plugin add failed [] Follow the Connect card when a Bot asks for a plugin [] Bookmark testers: X connector may still need a paid X API key in some setups (official path now auto-creates a developer account with credits) [] Bookmark testers: image generation works; testers now also claim video editing (music sync). Video generation still unconfirmed. Testers (XFreeze): dedicated video-editor Bot for footage → clips/cuts/sound/titles [] Bookmark testers: Grok Bot can now read your X bookmarks [] Testers (testerlabor): you can link your X Premium+ subscription to Grok Bot [] Testers: Higgsfield x Grok Bot; 100 free credits for new users [] Testers: send a YouTube link with start/end timestamps and get an HD clip in chat (Google login claimed) [] Testers: give a Bot Grok Build + Cursor CLI so weekly limits can be spread across Cursor and Grok [] Grok Bot team (poteto) + testers (XFreeze): Microsoft connectors live - Outlook, Outlook Calendar, OneDrive (search/send email, drafts, schedules, meetings, browse/upload files) [] Testers (XFreeze): Bot can natively generate images with Grok Imagine Image 2.0 inside the workflow (no separate Imagine tab) SKILLS AND ROUTINES [] Skill = reusable how-to (steps, rules, output, approval boundary) [] Routine = when to run that work (schedule or event) [] Do the task once, make it reliable, save a skill, then automate [] Teach a task: open computer view, choose Teach a task, demo up to 10 minutes, review the draft skill [] Teaching records the screen, not microphone audio; do not expose secrets while teaching [] If Teach a task is missing, ask the Bot to write a skill from the completed work [] Create a routine on the Bot that should own the job [] Confirm owner, schedule, time zone, input, result, approval, and missing-data behavior [] Event triggers (Slack, GitHub) are separate from plugins and need their own connection [] Keep event matchers narrow; avoid every new message [] Test run does real work; use safe inputs [] Testers quoting docs: Test can send real emails to real clients; Stop is a brake, not a rewind [] View conversation details → Routines to pause, edit, inspect, or delete [] A Bot can own 50 routines; last 20 run records are kept [] Deleting a routine has no undo [] Testers quoting docs: delete a Bot and every routine on it dies; no undo [] Long absence can pause unattended routines until you confirm [] Bookmark testers: Teach a task from + in the browser, record yourself, then let the Bot replay it [] Testers: skills taught to one bot claimed available across the account team on the same computer [] Official Elon: how to share your Grok Bot design with others [] Testers: a reusable-skills source claimed (BrianRoemmele) [] Testers quoting Grok Bot team (0xMorlex): keep recurring routines off the main agent's context [] Testers (mvanhorn): Teach by recording and respect the 10-minute cap MULTI BOT TEAMS [] Start with one Bot that owns an end-to-end outcome [] Add a specialist only when the role is stable [] Use a group chat when the handoff itself should be visible [] Bots can message each other and pass ownership [] Do not treat separate Bots as a security boundary (they share the computer) [] Keep sending, buying, deleting, publishing, and production changes behind approval [] Bookmark testers: a Bot may create other Bots before it can delete them [] Bookmark testers: tell a hub Bot to loop a specialist every few minutes and watch it [] Testers: put Bots in one group chat, appoint a Chief of Staff, and stop being the router [] Testers (farzyness): one master agent owns specialists + chat rooms and pings you one action item at a time [] Testers: isolate each Bot's job and add a supervisor; a crew without that can perform worse [] Testers: night-shift crews (chief, scout, forge, critic, ship, ledger) share one computer; human gate for merge, production, spend, send, delete [] Testers: one group chat per job/post, not per Bot; you only message the Chief of Staff [] Testers: show the workflow once on screen rather than writing a long spec [] Testers: add a RED TEAM Bot whose job is to disprove the thesis; no single source closes a claim [] Testers quoting Grok Bot team (0xMorlex): specialist roles (designer/engineer/PM); organize projects without a new Bot for everything; a Chief of Agents that creates and manages the rest [] Testers (mvanhorn): Bot Advisor whose only job is building and tightening other Bots; files are the memory bus between Bots [] Testers (Damir_Akaza): 4 Bots in one group chat split a Meta ads campaign (creatives, fact-check, deploy) with autonomous handoff [] Testers (cminshall): overnight group of five Bots one-shotted an admin UI from PRD/FRD/prototype PNGs IOS [] Same Bots, chats, routines, plugins, and cloud computer as desktop [] Testers (mattyp): Grok Bot supports 21+ localized languages on mobile [] Send text, dictate, attach photos/files, mention Bots, reply in threads [] Take over the computer for login/2FA from the phone [] You can pause or resume a routine on iOS [] Editing schedule, run history, test, delete, and teach-by-demo still need desktop [] Enable notifications for results, questions, and approvals [] Testers: phone notification shows the proposed action; approve or deny [] Testers (XFreeze): you can operate and take over the Bot's computer from your phone as long as it has internet [] Grok Bot team (poteto, earlier): had pointed at Play pre-registration; superseded by Official bot Sep 2 Android launch APPROVALS AND SAFETY [] Put the stop line in the request: draft, do not send; ask after showing current vs proposed [] Desktop: Allow once, Deny, or Always allow a matching rule [] iPhone: Approve once or Deny [] Auto Review: Settings → General → Auto-review [] Require Approval beats Always Allow when both match [] Write narrow rules, not allow everything in the browser [] Do not approve an action you cannot identify [] Connect only the tools the workflow needs [] Start read-only; keep spend, send, publish, delete, and production behind approval [] Sign out and revoke connectors when access should end [] Deleting a Bot does not wipe shared files or browser sessions [] Bookmark testers: delay standing inbox/CRM access until you trust the beta [] Bookmark testers: one person burned a 7-day quota in about 8 hours [] Testers (daveginvesting): burned a week of tokens in about 2 hours on first try [] Bookmark testers: SuperGrok may offer one-off usage resets in settings; use before they expire [] Testers: gate destructive actions (delete, overwrite, irreversible send) as their own confirmation, not lumped with routine tool use [] Testers quoting docs: Test run does real work; Stop does not unsend [] Testers quoting Elon (cb_doge): connecting a Bot to a bank account; Elon said any loss from a bot mistake would be covered. Still keep spend behind approval [] Official bot Link shopping: keep purchases behind approval even though the Bot can complete them on your behalf [] Official Elon: Grok Bot buys a Tesla [] Testers (mvanhorn): unsupervised crews claimed to multiply their own errors ~17x; draft-then-approve anything that sends; most Bots that don't own an outcome fail [] Testers (antpalkin): end every agent's job with a hard never-without-asking list; give one Bot veto/kill power whose no beats the rest of the desk FIRST BOTS WORTH CREATING [] Inbox manager for email and Slack triage [] Calendar and reservation Bot [] Research and daily brief Bot [] Coding Bot that can launch Cursor cloud agents [] Testers (AlexFinn): pair a developer Bot (Cursor cloud agents + PRs) with a PM Bot on Notion/Linear that feeds tasks and grants permission — software-factory loop [] Chief-of-staff hub that routes work to specialists [] Personal errands Bot (tickets, food, travel, forms) [] Content Bot that drafts in your voice for approval [] Chief-of-staff that researches you, organizes the other Bots, and can turn the digest into a morning podcast [] Testers (mvanhorn): Bot Advisor; own-inbox Bot; a call Bot with its own number [] Testers (techdevnotes): default Bots circulating - Night Shift (overnight digest), Inbox Triage, Chief of Staff, Negotiator, Prototyper, Researcher, Shopper, Apartment Scout, Lookout, Competitor Watcher [] Testers (techdevnotes): also tool-specific sales/ops/dev roles (CRM scribe, pipeline scout, ticket triager, QA, dashboard watcher) [] Official bot + Link: Shopper Bot can now complete online purchases once link is connected (keep approval on) [] Testers / SpaceXAI (kiaraplds): flights, tickets, groceries - delegate errands safely to your Bot [] Testers (minchoi): one-person-company setups - money, appointments, running ops from the phone [] Testers (niccruzpatane): Accounting Bot (invoices, spending, bills); Personal Bot (flights, rides, Airbnb, Google Calendar, Amazon orders/returns); Home Bot (lights, robots, speakers, thermostats) [] Testers (GrokBotDev): Jess (email/calendar/Notion/Slack recap), Marketing Bot, Prospecting Sheet Builder, Reaper (kill unused subs/meetings), Human Copywriter [] Testers (Michael_Fenech_): start in recruitment, e-comm, real estate, accounting, legal, SaaS, agencies, trades, founder ops EVENTS - Testers (cb_doge): Grok Bot Galaxy three-day event Sep 15–17 at The Howard, 661 Howard St, San Francisco (in person or livestream, 8:45am–6:00pm): create/customize Bots, teach style/goals, workflows by role, meet the team OFFICIAL LINKS - Overview: - Get started: - Create Bots: - Skills and routines: - Computer and apps: - Approvals and privacy: - iOS: - Cursor getting started: - SuperGrok Heavy link: - Launch post: - Download:

GROK BOT HOW TO USE WHAT NEW TODAY - Folder 843 posts (3 new vs Sep 5) - Testers (GrokBotDev): Official Marketplace launched (about 69 bots on the official list; community catalog 420+ discoverable/searchable from a Bot) - Testers (JasonL_Capital): 8 options-trading Bots (scan puts, price LEAPS, run the wheel) with copy-paste prompts — trading strategist pack - Testers (AsFoundX): SpaceXAI Grok Bot Galaxy — Sep 15–17 at The Howard, SF + worldwide livestream; persistent AI agents / teammate with its own computer WHAT IT IS - A Bot is a named, persistent teammate, not a one-off chat - You message it like a coworker and it finishes work in real apps - All of your Bots share one cloud computer (browser, files, terminal) - Each Bot has its own screen on that shared computer - Work keeps going when your laptop or the app is closed - It only comes back when it needs approval or a human step - Do not confuse Grok Bot with Digital Optimus (real-time video human emulation) - Testers (joehansen): do not confuse Grok Bot with an X Chat Agent (an X account you add to a group chat). Grok Bot is the machine that does the work - Official Elon: Your Bot will identify issues to resolve, notify you when they are fixed, and continue on with your project ACCESS AND INSTALL - Official bot (Aug 26): All SuperGrok and Cursor Pro subscribers now have access - Testers (mattyp): Grok Bot is free to try; every Grok & Cursor plan includes Grok Bot - Testers quoting SpaceXAI (cb_doge): SuperGrok, SuperGrok Plus, SuperGrok Heavy, Cursor Pro, Cursor Pro+, Cursor Ultra, Cursor Teams Standard and Premium - Cursor CEO Michael Truell: everyone with a standard Grok or Cursor subscription - Testers: included at no extra cost with those plans; circulating plan prices $20/month Cursor Pro and $25/month SuperGrok (nextbigfuture) - Official bot + Elon: weekly / free usage limits reset for all Grok Bot users - Sign in with your Cursor account (that account owns plan and usage) - Official desktop download: - Also listed at - Official desktop is macOS and Windows (Apple silicon or Intel; Windows x64 or Arm64) - Testers (mattyp): Linux is now supported (official docs may lag) - iPhone: iOS 18+, App Store app "Grok Bot" - Official (bot, Sep 2): Grok Bot is now available on Android - Testers (mark_k): install from Play Store; full Grok Bot experience on Android - Play Store: - Official docs may still lag on Android; Testers (mattyp, Sep 4): Grok Bot is now available for iPad - SuperGrok Heavy users can choose Get access with SuperGrok Heavy, then Link Grok Account - Linking SuperGrok Heavy can unlock free Cursor Ultra (one Grok account to one Cursor account) - Legacy Privacy Mode blocks Grok Bot; switch to a supported Cursor data setting first - Grok Bot checks for updates automatically; Check for Updates is in Settings → Beta - Official Elon (Sep 4): Grok Bot Enterprise is now available - Testers (mark_k, Sep 3): Version 0.36.0 is now live — bugfixes and improvements - Testers (mattyp, Sep 4): iPad app available (official docs may still lag) SIGN IN [] Desktop: Get started, then Sign In with Cursor in the browser [] iOS: Login with Cursor, finish in the browser, return to the app [] Official: Cmd-D turns on voice dictation [] Official: it is easier to use the remote computer from your phone [] Use the same Cursor account that should own usage [] First-run tour asks which tools you use; that only shapes teammate suggestions [] Computer setup runs in the background, then Meet a future teammate opens CREATE A BOT [] New in the sidebar, or Cmd/Ctrl+N [] In New chat, choose Create new agent [] Edit Profile: name, title, description, avatar [] Give a short name, one primary job, and how it should work [] Description = standing rules (never send without approval) [] Chat messages = this-task instructions (draft follow-ups for these 12 accounts) [] Focused Bots beat one catch-all General Helper [] Testers (XFreeze): do not design a Bot from scratch; ask a Bot to create a capable one for you (it already has your context) [] Bookmark testers: start with about six roles; give each Bot recurring work [] Pin important Bots; hide unused ones (hiding does not pause routines) [] Bookmark testers: resize the sidebar, give titles, and group Bots into sections [] Duplicate a Bot to reuse a role for a new scope (copy does not include memory or history) [] Delete only if you are sure; files and logins on the shared computer stay [] Account limit: 50 Bots and group chats combined [] Name language can steer reply language (bookmark testers reported this) [] Bookmark testers: no model picker yet; testers still list voice mode, BYOK, multiplayer, and hang-error messages as missing (iPad now available per mattyp) [] Testers (XEthanai / XFreeze): shareable Bot templates - build once, fine-tune, share the full setup for others to use or customize [] Testers (GrokBotDev): Official Marketplace launched (about 69 bots listed; community has catalogued 420+ searchable from a Bot) [] Testers (XFreeze): Marketplace framing earlier — browse specialized Grok Bots by category and add them to your team [] Testers (RoundtableSpace): Marketplace framing — hand-picked bots by category with routines/workflows built in (app store for AI teammates) [] Testers (kloss_xyz): 8 official-ish bot templates (calls, X, writing, images, coding, networking, tool testing, parking tickets) HOW TO WRITE A TASK [] Outcome: what should be finished [] Sources: which apps, sites, files, or chats matter [] Constraints: what it must not do, or must ask first [] Deliverable: what it should return [] Review point: when it should stop for you [] Safe first task: attach a file and ask for a cited summary; do not change the file [] Next task: one real tool, read-only, with a sign-in handoff if needed [] After a good result, name the lasting format preference in chat [] Then save it as a skill or routine [] Official bot examples: email cleanup, Starlink-likely flights, build a site then buy the domain and deploy, meeting notes, sales prospecting, refunds, podcast audio digest [] Testers: paste a viral video link and ask the Bot to recreate it [] Testers: start from an org chart or make one Bot the boss of a repo, not a long to-do list [] Testers: one clear job, explicit allowed sources, no-guessing rule, approval gate before any real action [] Testers: 5 calibrations - confidence threshold, checkpoint long tasks, show negative examples, gate destructive actions separately, test edge cases first [] Testers: one Bot, one job - two jobs claimed worse at both; put recurring work on a schedule [] Testers quoting claimed SpaceXAI employee: version prompts and tool configs like code; scratchpad separate from the user-facing answer; retry with a different strategy; measure cost per successful outcome; review failure logs on a schedule [] Testers (mvanhorn): Compound Engineering - force a plan first; three-layer instructions (base, role, current focus); screenshot instead of retyping what's on screen; ping only on a real hit [] Testers (AlexFinn): anything you are about to do on your computer, ask Grok Bot first [] Testers (AlexFinn): example week - Reddit microSaaS, 3D digital office to watch Bots, Omarchy setup, product returns, daily AI news post, Cursor cloud-agent bug fixes, X model-release watch, brand-deal negotiation, contract redlines [] Testers (Michael_Fenech_): give it business responsibilities (checking, chasing, updating, coordinating), not just questions AGENT COMPUTER AND LOGINS [] Open Agent Computer from the conversation to watch the desktop [] Take over for password, passkey, 2FA, CAPTCHA, payment, or human-only pages [] Complete only the blocked step, then return control [] Never paste passwords or one-time codes into chat [] Use a secure secret request when the app offers one [] Browser sessions persist and are shared across all your Bots [] Prefer a connector/plugin when one exists; use the browser when it does not [] Testers (SamSokolin): for repeated web-app clicks, reverse-engineer browser-use into scripts (capture network once, call APIs next) [] Keep durable files in /workspace with clear project folders [] Settings → Beta: Update Agent Computer (preserve state), Recover, or Reset (can lose recent work) [] The cloud computer is not your Mac or Windows machine [] Local-computer execution is separate: Settings → General → Agent → Execution on Local Computer [] Default local policy is Ask every time; use Never allowed unless you need local files [] Bookmark testers: give a Bot full local Mac/iMessage access only on a spare machine [] Testers: local Mac access can write local Python scripts on your Mac [] Testers (Av1dlive / mvanhorn): Claude Code, Codex, and Cursor claimed runnable on the Bot's own computer [] Testers (XFreeze): take over that same cloud computer from your phone without being at the laptop [] Testers (Damir_Akaza): group-chat Bots can reach a local Mac Mini via Tailscale for project files and local scripts [] Testers (farzyness): a Bot can exclusively use Grok Build in CLI with the latest Grok models at highest thinking [] Testers (AlexFinn): a 3D digital office on a second monitor to watch Bots work PLUGINS AND CONNECTORS [] Settings → Plugins, then Add, then authenticate in the browser [] Grok Bot team (poteto): tinkabot helps build MCP/skills plugins and submit them for approval so all users can use them [] Type @ to attach a connector; type / to reference a saved skill [] Installed connectors are account-wide, not isolated to one Bot [] Official: you can connect multiple accounts to the same plugin [] Official bot (Aug 26): SuperGrok and Cursor Pro now included; weekly limits reset. Testers quoting SpaceXAI: also Plus/Heavy/Pro+/Ultra/Teams [] Testers: give a Bot its own email address so it can send and receive on its own [] Testers (mvanhorn): give a Bot its own inbox, not your Gmail (one mistake should not flag your domain); Twilio number so a Bot can make calls [] Testers: app v0.23.0 adds creating new channels [] Official bot: improved X support - connect your X profile; a developer account is auto-created with included credits [] Testers (blankspeaker): Plugins, add X, authenticate; $100 in X API credits good for a year (new and existing devs) [] Testers (GrokInsider): if credits did not land, ask Grok Bot to connect X so the Authorize card opens the browser; tester's manual plugin add failed [] Follow the Connect card when a Bot asks for a plugin [] Bookmark testers: X connector may still need a paid X API key in some setups (official path now auto-creates a developer account with credits) [] Bookmark testers: image generation works; testers now also claim video editing (music sync). Video generation still unconfirmed. Testers (XFreeze): dedicated video-editor Bot for footage → clips/cuts/sound/titles [] Bookmark testers: Grok Bot can now read your X bookmarks [] Testers (testerlabor): you can link your X Premium+ subscription to Grok Bot [] Testers: Higgsfield x Grok Bot; 100 free credits for new users [] Testers: send a YouTube link with start/end timestamps and get an HD clip in chat (Google login claimed) [] Testers: give a Bot Grok Build + Cursor CLI so weekly limits can be spread across Cursor and Grok [] Grok Bot team (poteto) + testers (XFreeze): Microsoft connectors live - Outlook, Outlook Calendar, OneDrive (search/send email, drafts, schedules, meetings, browse/upload files) [] Testers (XFreeze): Bot can natively generate images with Grok Imagine Image 2.0 inside the workflow (no separate Imagine tab) SKILLS AND ROUTINES [] Skill = reusable how-to (steps, rules, output, approval boundary) [] Routine = when to run that work (schedule or event) [] Do the task once, make it reliable, save a skill, then automate [] Teach a task: open computer view, choose Teach a task, demo up to 10 minutes, review the draft skill [] Teaching records the screen, not microphone audio; do not expose secrets while teaching [] If Teach a task is missing, ask the Bot to write a skill from the completed work [] Create a routine on the Bot that should own the job [] Confirm owner, schedule, time zone, input, result, approval, and missing-data behavior [] Event triggers (Slack, GitHub) are separate from plugins and need their own connection [] Keep event matchers narrow; avoid every new message [] Test run does real work; use safe inputs [] Testers quoting docs: Test can send real emails to real clients; Stop is a brake, not a rewind [] View conversation details → Routines to pause, edit, inspect, or delete [] A Bot can own 50 routines; last 20 run records are kept [] Deleting a routine has no undo [] Testers quoting docs: delete a Bot and every routine on it dies; no undo [] Long absence can pause unattended routines until you confirm [] Bookmark testers: Teach a task from + in the browser, record yourself, then let the Bot replay it [] Testers: skills taught to one bot claimed available across the account team on the same computer [] Official Elon: how to share your Grok Bot design with others [] Testers: a reusable-skills source claimed (BrianRoemmele) [] Testers quoting Grok Bot team (0xMorlex): keep recurring routines off the main agent's context [] Testers (mvanhorn): Teach by recording and respect the 10-minute cap MULTI BOT TEAMS [] Start with one Bot that owns an end-to-end outcome [] Add a specialist only when the role is stable [] Use a group chat when the handoff itself should be visible [] Bots can message each other and pass ownership [] Do not treat separate Bots as a security boundary (they share the computer) [] Keep sending, buying, deleting, publishing, and production changes behind approval [] Bookmark testers: a Bot may create other Bots before it can delete them [] Bookmark testers: tell a hub Bot to loop a specialist every few minutes and watch it [] Testers: put Bots in one group chat, appoint a Chief of Staff, and stop being the router [] Testers (farzyness): one master agent owns specialists + chat rooms and pings you one action item at a time [] Testers: isolate each Bot's job and add a supervisor; a crew without that can perform worse [] Testers: night-shift crews (chief, scout, forge, critic, ship, ledger) share one computer; human gate for merge, production, spend, send, delete [] Testers: one group chat per job/post, not per Bot; you only message the Chief of Staff [] Testers: show the workflow once on screen rather than writing a long spec [] Testers: add a RED TEAM Bot whose job is to disprove the thesis; no single source closes a claim [] Testers quoting Grok Bot team (0xMorlex): specialist roles (designer/engineer/PM); organize projects without a new Bot for everything; a Chief of Agents that creates and manages the rest [] Testers (mvanhorn): Bot Advisor whose only job is building and tightening other Bots; files are the memory bus between Bots [] Testers (Damir_Akaza): 4 Bots in one group chat split a Meta ads campaign (creatives, fact-check, deploy) with autonomous handoff [] Testers (cminshall): overnight group of five Bots one-shotted an admin UI from PRD/FRD/prototype PNGs IOS [] Same Bots, chats, routines, plugins, and cloud computer as desktop [] Testers (mattyp): Grok Bot supports 21+ localized languages on mobile [] Send text, dictate, attach photos/files, mention Bots, reply in threads [] Take over the computer for login/2FA from the phone [] You can pause or resume a routine on iOS [] Editing schedule, run history, test, delete, and teach-by-demo still need desktop [] Enable notifications for results, questions, and approvals [] Testers: phone notification shows the proposed action; approve or deny [] Testers (XFreeze): you can operate and take over the Bot's computer from your phone as long as it has internet [] Grok Bot team (poteto, earlier): had pointed at Play pre-registration; superseded by Official bot Sep 2 Android launch APPROVALS AND SAFETY [] Put the stop line in the request: draft, do not send; ask after showing current vs proposed [] Desktop: Allow once, Deny, or Always allow a matching rule [] iPhone: Approve once or Deny [] Auto Review: Settings → General → Auto-review [] Require Approval beats Always Allow when both match [] Write narrow rules, not allow everything in the browser [] Do not approve an action you cannot identify [] Connect only the tools the workflow needs [] Start read-only; keep spend, send, publish, delete, and production behind approval [] Sign out and revoke connectors when access should end [] Deleting a Bot does not wipe shared files or browser sessions [] Bookmark testers: delay standing inbox/CRM access until you trust the beta [] Bookmark testers: one person burned a 7-day quota in about 8 hours [] Testers (daveginvesting): burned a week of tokens in about 2 hours on first try [] Bookmark testers: SuperGrok may offer one-off usage resets in settings; use before they expire [] Testers: gate destructive actions (delete, overwrite, irreversible send) as their own confirmation, not lumped with routine tool use [] Testers quoting docs: Test run does real work; Stop does not unsend [] Testers quoting Elon (cb_doge): connecting a Bot to a bank account; Elon said any loss from a bot mistake would be covered. Still keep spend behind approval [] Official bot Link shopping: keep purchases behind approval even though the Bot can complete them on your behalf [] Official Elon: Grok Bot buys a Tesla [] Testers (mvanhorn): unsupervised crews claimed to multiply their own errors ~17x; draft-then-approve anything that sends; most Bots that don't own an outcome fail [] Testers (antpalkin): end every agent's job with a hard never-without-asking list; give one Bot veto/kill power whose no beats the rest of the desk FIRST BOTS WORTH CREATING [] Inbox manager for email and Slack triage [] Calendar and reservation Bot [] Research and daily brief Bot [] Coding Bot that can launch Cursor cloud agents [] Testers (AlexFinn): pair a developer Bot (Cursor cloud agents + PRs) with a PM Bot on Notion/Linear that feeds tasks and grants permission — software-factory loop [] Chief-of-staff hub that routes work to specialists [] Personal errands Bot (tickets, food, travel, forms) [] Content Bot that drafts in your voice for approval [] Chief-of-staff that researches you, organizes the other Bots, and can turn the digest into a morning podcast [] Testers (mvanhorn): Bot Advisor; own-inbox Bot; a call Bot with its own number [] Testers (techdevnotes): default Bots circulating - Night Shift (overnight digest), Inbox Triage, Chief of Staff, Negotiator, Prototyper, Researcher, Shopper, Apartment Scout, Lookout, Competitor Watcher [] Testers (techdevnotes): also tool-specific sales/ops/dev roles (CRM scribe, pipeline scout, ticket triager, QA, dashboard watcher) [] Official bot + Link: Shopper Bot can now complete online purchases once link is connected (keep approval on) [] Testers / SpaceXAI (kiaraplds): flights, tickets, groceries - delegate errands safely to your Bot [] Testers (minchoi): one-person-company setups - money, appointments, running ops from the phone [] Testers (niccruzpatane): Accounting Bot (invoices, spending, bills); Personal Bot (flights, rides, Airbnb, Google Calendar, Amazon orders/returns); Home Bot (lights, robots, speakers, thermostats) [] Testers (GrokBotDev): Jess (email/calendar/Notion/Slack recap), Marketing Bot, Prospecting Sheet Builder, Reaper (kill unused subs/meetings), Human Copywriter [] Testers (JasonL_Capital): 8 options-trading Bots (scan puts, price LEAPS, run the wheel) with copy-paste prompts [] Testers (Michael_Fenech_): start in recruitment, e-comm, real estate, accounting, legal, SaaS, agencies, trades, founder ops EVENTS - Testers (cb_doge): Grok Bot Galaxy three-day event Sep 15–17 at The Howard, 661 Howard St, San Francisco (in person or livestream, 8:45am–6:00pm): create/customize Bots, teach style/goals, workflows by role, meet the team - Testers (AsFoundX): SpaceXAI hosting Grok Bot Galaxy Sep 15–17 at The Howard, SF + worldwide livestream (persistent agents / teammate with its own computer) OFFICIAL LINKS - Overview: - Get started: - Create Bots: - Skills and routines: - Computer and apps: - Approvals and privacy: - iOS: - Cursor getting started: - SuperGrok Heavy link: - Launch post: - Download:

GROK BOT USE CASES NEW TODAY - Refresh after Xapi filed 5 more posts into folder 2095212840558658002: 126 unique (prev 121 → 126, +5). Official 0 / Testers 126. All 5 hydrated via get_posts_by_ids. No elonmusk / bot / grok author posts. Quoted SpaceXAI engineers, Cursor field engineer Amrita, and Claire Vo still Testers (author is the poster). “$20/mo”, “70% cheaper”, “$200/mo plan”, “no context window / memory in S3”, “$500 course” are Testers claims — not Official pricing/SKU. Hype labeled. Not a medical or trading how-to. Review 2090096266533335474 stays separate. Skipped arthur_win8 how-to 2095298449524523468 and other x-folders-posted ids: 0 hits in this batch. - Testers (TopherNOW, Sep 4) Xapi: two weeks of GrokBot lessons — setup is easy, quality automation is not; give examples → evaluate → iterate → then automate; do not launch 10–15 agents day one; start with Chief of Staff (audit/suggest); pick only bots that help the business… - Testers (AIJackRoberts, Sep 4) Xapi: six-agent company — Grok Master (brain-dump → which bots), Arnie health (calendar + weigh-ins), Chief of Staff (delegates; Topview/Apify), Strategist, Head of Fun, Finance on Mercury (fun must ask finance first). Bots message each other;… - Testers (AleiahLock, Sep 4) Xapi: Cursor workshop relay (field engineer Amrita Venkatraman) — persona-based CEO model not task prompts; CoS spins inbox/calendar/to-do; tag bots in group chat; Teach a Task (record flight booking → permanent skill); close laptop, agents keep r… - Testers (0xMovez, Sep 4) Xapi: SpaceXAI engineer (ex-Cursor) workshop relay — 20+ GrokBot agents with /loop /goal inside pstack; Chief of Staff knows other agents and manages everything; “1% use it correctly”; build a team from scratch in 1-hour workshop. Testers quote, not… - Testers (0xMorlex, Sep 5) Xapi: Claire Vo power-user session — “turned me back into an exec”; replaced OpenClaw with 7 specialized GrokBots (CoS, family daily briefing, eng manager pushing PRs, customer support, shopping research/buy); CoS → engineering → support → family →… WHAT IT IS - This note is use-case practice from the Grok Bot Use Cases folder only: how Testers actually staff a Chief of Staff, brief a bot, run a small team, wire inbox/calendar/Slack, hunt subscriptions, run a one-person desk, research, code overnight, copy templates, shop with Link, and keep a human on money. It is not Review as its own title. It is not Grok Bot How To Use. It is not a Grok Bot product dump (folder Grok Bot stays separate). - Official vs Testers: Official = elonmusk / bot / grok as AUTHOR of the post. Everyone else is Testers — including posters quoting Elon or SpaceXAI engineers/PMs, and including GlowbomOSS / RichardPatey / kirillk_web3. This dump has Official 0 / Testers 126. - Do not retitle. Do not mix Review (id 2090096266533335474) or Grok Bot How To Use into this as those titles. Do not invent features, prices, or plan SKUs. Glowbom OSS / Skills Dojo / Plugin Marketplace / web-app bots / Klaviyo bot / SpaceXAI internal installs are Testers claims, not Official SKUs. Hype (trading PnL, $100k-class claims, millionaire, “almost unfairly easy”) is labeled, not treated as fact. Not medical or trading how-tos. HOW TO USE - Sequence from dump (Testers): (1) treat the Bot as a teammate with a job, not a chat window; (2) name one Chief of Staff first — it routes, it does not do all the work; (3) write Description vs Task and set approval gates before the first send; (4) run by hand three times, then skill, then routine; (5) start with two Bots, cap the roster, reuse before spawning; (6) connect mail, calendar, and Slack and report actuals; (7) put handoffs in /workspace, not chat paste; (8) stay silent unless stuck; (9) overnight: Cursor or local Grok Build CLI for watched/heavy work, Grok Bot team for the rest; (10) copy a proven template instead of rebuilding; (11) Email+Slack+CoS can stand up in 20–30 min (Testers); (12) label money/PnL stories as Testers hype. [] Write a job, not a prompt — what it owns, which accounts, what hours, who it hands finished work to (unicodef1wn, kloss_xyz, jigschat) [] Separate Description (never changes) from Task (this run). Mixing them is why bots feel inconsistent [] Name one Chief of Staff as the only human entry point. It routes, delegates, watches handoffs, escalates — it does not do every job (adiix_official, ScottyBeamIO, SymoneBeez, kirillk_web3, jigschat) [] Set approval gates before the first task: money, publishing, deletion, signatures, irreversible external actions. You still hit send (unicodef1wn, adiix_official, s4yonnara) [] Do not automate on day one. Run it by hand, save a skill, then a routine (unicodef1wn, kloss_xyz skill filter: use 3× or cut) [] Start with two Bots only. Cap team size. Reuse a bot you already set up before adding a new one (beamnxw, kloss_xyz, jigschat week-one four) [] Connect mail, calendar, and Slack. Have Chief report what you actually spent time on, not what you planned (kloss_xyz, s4yonnara, SymoneBeez, kirillk_web3) [] Put research, drafts, evidence, decisions, and handoffs in /workspace so the next Bot continues where the last stopped (adiix_official, karankendre) [] If a tool blocks automation, do the task once while it watches; save the correction as a permanent rule (kloss_xyz) [] Tell bots to stay silent unless they are stuck or they need you to decide (kloss_xyz) [] Overnight: keep watched coding in Cursor; route token-heavy jobs to local Grok Build CLI; hand everything else to a Grok Bot team; ping when the fix lands (0xCarnagee, joehansen, TheNotARubicon, s4yonnara builders, chariya111111) [] Copy a proven template / marketplace bot instead of rebuilding the desk (RoundtableSpace, shmidtqq, Av1dlive, RichardPatey, ericosiu OSS, kloss_xyz 26) [] Treat trading PnL, “make money,” and $60k / $1k→$3.9k / $83.5k / $50k / $25k claims as Testers hype. Not a trading or medical how-to [] Easy setup ≠ easy quality — prove one job with CoS before spawning a roster (TopherNOW) - Watch Official elonmusk / bot / grok for any later restatement. Treat SpaceXAI-engineer quotes and Elon relays as Testers until those handles author the post. First hour / Chief of Staff - Testers (TopherNOW, Sep 4): day-one lessons — CoS first for audit/suggest; focus ONE workflow until useful, then pass off; do not launch 10–15 agents. - Testers (AIJackRoberts, Sep 4): CoS + five specialists that message each other; Grok Master brain-dump picks the roster before you spawn. - Testers (AleiahLock, Sep 4): Cursor workshop — CoS spins inbox/calendar/to-do; Teach a Task; persona over task; granular ask-first rules. - Testers (0xMovez, Sep 4): SpaceXAI workshop — CoS that knows every agent and manages /loop /goal teams (20+). - Testers (0xMorlex, Sep 5): Claire Vo — CoS coordinates eng/support/family/finance/shopping; human only at decisions. - Testers (kloss_xyz, Sep 3): blank-page day one — stand up CoS, import memories/context, CoS interviews you for priorities, then add specialists. Talk mostly to CoS; bots message each other on channels. - Testers (kirillk_web3, Sep 3): Plugins first, then CoS with a meeting-prep routine and inbox draft routine (no auto-send). - Testers (jigschat, Sep 3): week-one four — CoS, Inbox, Research, Reviewer; 20-minute first setup; GREEN/YELLOW/RED before anything external. [] Create one Chief of Staff as the only entry point before any specialist [] Paste a job description into Description; keep this-run instructions in Task [] Set the never-alone list (send, publish, spend, delete, sign) before the first task [] Do not start with 20+ agents. Two Bots, then add (or jigschat week-one four) [] Email + Slack + CoS can stand up in the first half hour if that is the desk (SymoneBeez) [] Point Chief at heavy jobs so it can route them to local Grok Build CLI instead of burning Bot tokens (TheNotARubicon) [] Skill filter: keep only what you used three times on real work (kloss_xyz) [] Focus ONE workflow with Chief until it is useful, then pass it to a specialist + routine (TopherNOW) How to brief a bot - Testers (TopherNOW, Sep 4): examples → evaluate → iterate until quality, then automate; separate agents when a domain needs its own memory. - Testers (AleiahLock, Sep 4): Teach a Task (record once → permanent skill); persona brief, not endless task prompts; external-email always ask first. - Testers (jigschat, Sep 3): one recurring job, one set of sources, hard stop before outside world; good vs bad task examples; checklist before a routine goes live. - Testers (kirillk_web3, Sep 3): concrete inbox/follow-up prompts — digest in chat, proposed reply in your voice, never auto-send; meeting notes as source of truth for follow-ups. [] Brief outcome, sources, constraints, deliverable, and the stop-for-review point before you send [] Save every correction as a standing rule [] Require source + evidence before action [] One bot owns the conclusion from the numbers [] A bot should never decide both what is true and whether it may act (Dmytroo_eth) [] Do not auto-send inbox drafts (kirillk_web3) [] Examples → evaluate → iterate → then automate; do not automate day-one noise (TopherNOW) Team of bots - Testers (0xMovez, Sep 4): 20+ agents with CoS manager; /loop /goal / pstack workshop from SpaceXAI (Testers relay). - Testers (AIJackRoberts, Sep 4): six named seats (Master/health/CoS/strategist/fun/finance) messaging each other. - Testers (0xMorlex, Sep 5): Claire Vo seven seats — CoS → eng → support → family → finance → shopping; not one all-in-one assistant. - Testers (TopherNOW, Sep 4): do not spawn a mess of 10–15; CoS proves one job, then hands off to a specialist + routine. - Testers (AleiahLock, Sep 4): live workshop team CoS → 3 bots → engineering → on-call; bots tag each other in group chat; agents negotiate APIs. - Testers (chariya111111, Sep 4): five ops/dev seats that remind each other of job boundaries, then coordinate a production deploy in a group. - Testers (kloss_xyz, Sep 3): CoS + 11 specialists + 2 channels; bots message each other and run routines. [] One Chief; specialists with one job each [] Shared /workspace bus — no copy-paste of context between tools [] Reuse before spawn; cap the roster; ask the human first [] Merge / deploy / send / spend stay behind a human gate [] Record yourself once to teach a repetitive task [] Five named seats with one permanent job each, same persistent cloud (RetroValix) [] Content desk can be seven seats with draft-only publishing (karankendre) [] Split a new agent only when a domain needs its own memory/context (TopherNOW) Inbox and calendar - Testers (AleiahLock, Sep 4): CoS stands up inbox, calendar, and to-do bots in the Cursor workshop. - Testers (AIJackRoberts, Sep 4): Arnie health bot reads calendar + weigh-ins before being asked. - Testers (0xMorlex, Sep 5): Claire Vo family agent turns plans + local news into a daily briefing. - Testers (kirillk_web3, Sep 3): CoS scans inbox for messages that need a reply; short digest + proposed reply; skip newsletters/noise; no auto-send. Meeting-prep routine pulls CRM/mail/Slack/notes. - Testers (kloss_xyz, Sep 3): connected email; cleaned thousands of spam; unsubscribed from 3 forgotten paid things. [] Connect mail and calendar under the Chief first [] Add Slack if that is where the desk lives (SymoneBeez) [] Triage what needs a reply; draft in your voice; you hit send [] Report actuals hourly; ping only when it truly matters [] Do not auto-send. Do not auto-post [] Webhook-on-mail is Testers practice — still a human on irreversible (rileybrown) Subscription audit - Testers (kloss_xyz, Sep 3): email clean found 3 forgotten paid subscriptions to cancel. - Testers (clairevo / s4yonnara): Penny Pincher digs through receipts for subscriptions to cancel and bills worth renegotiating. Same walkthrough: approval gate before anything irreversible. [] Read-only first: list subscriptions from receipts / mail [] Hard stop: no accept, no confirm charges, no binding cancel without you saying run it [] Human still signs in and hits the irreversible button One-person company - Testers (AIJackRoberts, Sep 4): built a 6-agent company inside Grok Bot; “$20/mo / 70% cheaper / no hosting” labeled Testers. - Testers (TopherNOW, Sep 4): pick bots that move the business; CoS-first; test before platform-switching; $200/mo plan claim labeled Testers. - Testers (0xMorlex, Sep 5): Claire Vo “back into an exec” — 7 bots, 7 jobs, one human at the approval layer. - Testers (kirillk_web3, Sep 3): one-person creative shop anecdote with CoS + Scout/Quill/Courier. “$30k/month” labeled Testers, not Official. - Testers (jigschat, Sep 3): 12 agents you’d keep; week-one four only. [] Write what the company does in one paragraph and what it must never do alone [] Chief of Staff first; two Bots; you still pick the topic and polish the draft [] Add send / marketing / sponsors only after the research→write loop is clean [] You still hit send, publish, and spend Daily brief / research - Testers (0xMorlex, Sep 5): family agent daily briefing from plans + local news (Claire Vo session). - Testers (AIJackRoberts, Sep 4): Strategist seat for analytics and competitors under CoS. - Testers (kloss_xyz, Sep 3): weekday news every 2 hours 6am–6pm + hourly model/AI release watch; intel watches 100+ accounts; new-only briefs. [] Demand sources and links on every brief; no guessing [] New-only reports; one line if nothing changed [] Analyst loop: what actually performed, then change the next draft [] Do not treat folder trading stories as a how-to Grok Build site - Testers (AleiahLock, Sep 4): persona backend bot works in any repo it has never seen (workshop). Testers claim. - Testers (chariya111111, Sep 4): five-agent site desk staged/deployed production (Gunicorn) with independent tests — human watched. Testers. [] Build the site from inside Grok Bot if that is the desk (GlowbomOSS Testers OSS, not Official) [] Route large coding jobs to local Grok Build CLI; results come back to the Bot (TheNotARubicon) [] Human still reviews merge / deploy / production Overnight coding and build / print loop - Testers (AleiahLock, Sep 4): close the laptop — every agent keeps running; eng team + on-call in workshop; two agents negotiate API contracts unattended. - Testers (0xMorlex, Sep 5): Claire Vo eng manager pushes PRs toward merge; CoS preps work before it reaches her. - Testers (chariya111111, Sep 4): group deploy with staged reload + backup + independent tests. [] Watched coding stays in Cursor; unattended work goes to a Grok Bot team [] Heavy / token-expensive jobs can go to local Grok Build CLI via Chief (TheNotARubicon) [] Ping only when the fix lands or a decision is needed [] Real file + live preview; do not eyeball a set of twenty from a screenshot [] Human still reviews merge / deploy / production Bot Templates - Testers (RichardPatey, Sep 4): free Klaviyo nine-skill bot. Testers template, not Official Marketplace SKU. - Testers (kloss_xyz, Sep 3): extracted/saved 26 public Grok Bot template setups; skill filter use-3×-or-cut. [] Browse a category / copy a proven setup instead of rebuilding the desk [] Keep the same approval gates on an imported bot: send, spend, delete, publish stay with you [] Do not treat a copied finance/trading template as a trading how-to [] Shared CoS template is Testers (Av1dlive), not Official [] Free Klaviyo / Skills Dojo / SpaceXAI-install lists are Testers, not Official SKUs Shopping with Link - Testers (0xMorlex, Sep 5): Claire Vo separate shopping agents research and buy — human still at approval. Testers; not Official Link SKU. [] Human still hits buy / confirm / pay [] Do not treat a Tester Amazon-buy demo as an Official Link SKU CFO / Bank Connect - Testers (AIJackRoberts, Sep 4): Finance bot on Mercury — Head of Fun must ask finance first. Testers connect claim; human still on irreversible money. Not Official bank SKU / not financial advice. [] Human approves every pay, refund, move, or confirm-charges action [] Do not treat folder PnL stories as a how-to. Not financial advice ACCESS - No Official elonmusk / bot / grok author post in this scrape. All 126 Testers. Watch Official if they later restate product, templates, Marketplace, web-app bots, or Link. - Defer Review → Review note (id 2090096266533335474). Defer Grok Bot product dump → Grok Bot. Defer Grok Build TUI → Grok Build. Do not retitle this Grok Bot How To Use. - Not medical. Not trading. Hype labeled. KEY LINKS - Testers day-one CoS lessons (TopherNOW): - Testers 6-agent company (AIJackRoberts): - Testers Cursor workshop relay (AleiahLock): - Testers SpaceXAI 20+ agents workshop (0xMovez): - Testers Claire Vo 7-bot exec session (0xMorlex): - Xapi MISSING (not in folder): 2095472505037148665 - Testers day-one CoS+11 bots (kloss_xyz): - Testers Plugins+CoS meeting/inbox routines (kirillk_web3): - Testers business growth video (ericosiu): - Testers 7-agent content team (karankendre): - Testers Klaviyo 9-skill bot (RichardPatey): - Testers 5-agent OrchidRoots deploy (chariya111111): - Testers week-one 4 roles (jigschat): - Testers Elon relay Chat→CoS→company (kingwilliam_): - Grok Bot Use Cases folder:

Yesterday, Tammy shared how her team replaced all their SaaS tools with their own AI-built equivalents and now run over 30 agents to support their business @numbersprotocol https://t.co/GUHcKRxDVe

I still don't understand why everyone isn't doing this yet Elon Musk left a comment under the original video: "this is either genius or a mistake." Using this exact setup, I found out my agents had been agreeing with each other for three days before I noticed Eleven Grok agents on the desk, costing $200 a month, doing a job a media analyst charges $350,000 a year for A 5 AM call. I don't participate in it How the agents are distributed: SEARCH-GH - reads GitHub, surfaces repo features before Twitter does SEARCH-XT - sits in crypto Twitter, catches tone before consensus SEARCH-DB - Dribbble, catches a visual trend before agencies do SEARCH-HN - Hacker News, keeps only what repeats SEARCH-AX - arXiv, reads preprints day-one SEARCH-PH - Product Hunt, logs launches before press coverage SEARCH-RD - Reddit, listens to niches nobody else checks SEARCH-YT - YouTube, transcribes before things go viral SEARCH-DC - Discord, monitors private servers SEARCH-SS - Substack, reads essays before they're quoted SEARCH-TT - TikTok, tracks topic velocity WATCHER - doesn't search itself, cross-references all eleven feeds and brings only the overlap that actually requires a human decision While I was away, the system scanned 166 signals, then 718, then 1,438 and caught 20 collisions between independent feeds. The result: one idea I packaged before the market did Each agent has its own virtual browser, terminal, and local cloud memory. The desk runs even when the laptop is closed Setup is easier than it seems: 1. Download Grok Bot and create your Watcher 2. Give the other ten agents task descriptions like you're briefing new hires 3. Run it once while they watch 4. Connect webhooks to your feeds and Telegram No VPS, no code, no waiting for developers his used to mean 16 hours of open tabs and fear you'd missed the moment. Mine took one evening Save this before your next idea. Save the guide

🚨 OpenAI power users are turning ONE agent into a 24/7 team that runs entire workflows while they sleep No new tools No code Just a 3 page setup 99% of people will never see Here's the full playbook before everyone copies it 🧵 https://t.co/WcSVz5yD21

https://t.co/Hdr7hpH2p8

[e] think · [l] keep · [p] do one thing · [r] attack it without holding the pen. How I supervise a chat model on research work. https://t.co/0BKRKudLRo

Most LLM failures are not crashes. They are confident, well formatted answers that nothing in the stack objected to. Here is what guardrails actually do, and where memory changes the answer. https://t.co/6np5YiljXg

https://t.co/9FnQH7CFhv

You are a Prompt Auditor. This chat is not for answering the user's question. Your job is to inspect whatever they type for bias, ego, and leading language, then hand them a cleaner prompt they can paste into a new chat. Do this for every user message unless they explicitly say "answer it here." WHAT TO LOOK FOR - Leading phrasing: "why is X so bad/good," "don't you think," "isn't it obvious" - Hidden assumptions treated as facts - Ego and certainty: "I know," "I'm convinced," "clearly," "everyone knows," "just confirm" - Absolutes used as premises: always, never, all, none - Loaded labels used as if settled - Validation-seeking: "am I right?", "this is good, right?" - Instructions that pressure agreement instead of accuracy OUTPUT FORMAT — use these exact headings every time: ## 1. Audit - Quote the risky phrases - One line each on what they push a model to do - If the question is already fairly clean, say so. Do not invent problems. ## 2. Neutral question Rewrite the user's request as a genuine question or a neutral task. Remove certainty, flattery-seeking, and loaded premises. Keep their actual intent. Do not add a new agenda. ## 3. New-chat prompt Give one copy-ready block the user can paste as the first message of a new chat. That block must include: 1. Short anti-sycophancy rules 2. The cleaned question/task 3. Any useful output constraints (what to separate: facts vs inference vs opinion; strongest countercase first; no flattery) Keep it tight enough for free-tier models. No preamble outside the copy block. COPY BLOCK RULES - Put the new-chat prompt inside a single fenced code block - It should work on ChatGPT, Claude, Gemini, or similar - Do not answer the underlying question - Do not praise the user - Do not add moral lectures If the user sends several questions, produce one combined new-chat prompt unless they are clearly separate topics. If separate, make one copy block per topic. If they say "answer it here," first still do sections 1–3, then answer the cleaned question under ## 4. Answer.

https://t.co/7fhp8h0MY9

Instinct hit $2.5 BILLION one week after launching 🤯 Linear hit the same valuation on the same day, with $100M ARR, 40,000 customers and 177% net revenue retention behind it Instinct is a personal agent with no app. You text it or call it, and it plugs into your email and accounts, then books the doctor, calls Comcast, cancels the subscriptions and negotiates with vendors while you sleep. $350M raised. Users who buy through it average $1,300+ a month. I ran it for two weeks and wrote the full playbook: setup order, 30+ ready-to-send texts, 7 workflows, plus invites while they last 👇 https://t.co/KhCQXRpio4 Would you hand an agent your logins?

Tonight I asked my AI agent which memory system it was using. It took a file audit to answer. It had been reading two at once for days. Same agent since January, three models, two vendors. Seven months of notes: four things rotted, five rules held. https://t.co/PRA5mQ95Ko