No-Code Agentist

GROK BOT GALAXY Updated 2026-09-21 Sources: Day 1–3 livestream sessions + Grok Bot Galaxy bookmark folder (107 posts, user-X MCP) NEW TODAY - Folder now 107 posts (4 new). - Testers (0xShoopy, Day 2 DropXAI): physical demos — newspaper bot, package→split-flap, iMessage Instacart share, back-in-stock, shows tracker; WiFi printer with no drivers. - Testers (0xShoopy): X Article — “Grok Bot: how to build an AI crew that learns by watching you work.” - Testers (0xSoural): connect email/calendar/Slack/X/credit card; bots each own memory/chat/job; Slack → Grok Bot; multi-bot Q&A. - Testers (BlueDeltaHQ): 30-prompt pack (Palmer / Tan / Sadanani). FIRST DUMP — Day 1 - Livestream demo (Day 1): Grok Bot Galaxy opened as a standing how-to topic — treat like SpaceX/Starship/Tesla folders. Three-day event framing: a small team building a company/product in three days with Grok Bot. - Livestream demo (101): Grok Bot pitched as a team of extraordinarily capable AI agents, not one single assistant. Create a bot by naming it, teaching it your style, and giving it a goal; then let it take on real work. - Livestream demo (101): Bots work in parallel across apps, tools, and websites already in use; message them like teammates; they keep context in memory and improve as they go. - Livestream demo (101 closing): Bots can access every tool — even tools without MCPs (Google Form demo; slide said this can extend to research tools such as Qualtrics). Bots learn from video teachings. External-facing actions should require human approval. - Livestream demo (Eng): AI Maturity Curve — Autocomplete (Cursor Tab) → Ask & Edit (Cursor Agent) → Agentic Coding (Cursor 3) → Automations (Cursor Cloud Agent) → Autonomous Coding (Grok Bot). - Livestream demo (PM): Three PM primitives — Attention List, Research across customer context, Shipping (Grok Bot claimed as a double-digit % of internal merged PRs). - Livestream demo (Founders): Multi-agent org live — CoS (steve) orchestrating specialists; Meet the crew: Close Bot, Prod Bot, Stalk Bot, Proto Bot, YapBot. Cost tip slide: “Routines are awesome (but audit them!)”. - Refresh 2026-09-15: first folder scrape merged — 23/+23 bookmark posts (signed-in website); see PRIOR FOLDER MERGE. - Refresh 2026-09-16: 39/+16 folder posts; Day 1 notes pack / cost tips / timestamps (see PRIOR 0916 highlights below). - Refresh 2026-09-19: 102/+13 folder posts; CoS stop wall + eng CI/eval guardrails + Blake post-sales (see PRIOR 0919). Session notes: none newer than how-to (last Day 3 Wrap Sep 17 already folded). Physical + connector demos (tester) - [T] 0xShoopy (Day 2 SpaceXAI demos): GrokBot left the screen — newspaper bot (calendar/email/subscriptions overnight → physical print + comic + crossword from your life); package tracker (email scan → Amazon stops → split-flap display flips on arrival); iMessage controller (Instacart location screenshots every 2 min to a friend — multiplayer without a share feature); back-in-stock tracker (daily size+color check); shows tracker (renewals/premieres → what to watch tonight). Quote: said "print this" → bot found printer on WiFi with no settings/drivers. - URL: - [T] 0xShoopy (X Article, quoted in the Day 2 demos post): "Grok Bot: how to build an AI crew that learns by watching you work" (article post bookmarked; companion to the demos thread). - URL: PRIOR FOLDER MERGE (2026-09-15 · 23/+23) PLATFORM pop-up company (tester claim) - [T] oneillund: after ~5h of stream, spotted live company name PLATFORM; slogan “Spin up a stall. Own the night.”; concept connects chefs, venue landlords, food-industry workers, and operators to launch city food pop-ups; site https://t.co/Y6LvquKQUp; verification timestamp cited ~5:16:55 into the broadcast. Operating model + builders - [T] 0xMorlex: operating model Human → sets direction · Grok Bot → holds context + coordinates · Specialist agents → execute · Humans → review, redirect, approve. Agent-native company from day one (product/research/eng/ops routed through same system), not isolated “ask an agent to write some code.” - Builders named across folder posts: Matt Palmer, Lauren Tan, Roshan Sadanani (SpaceXAI engineers building live with Grok Bot as AI workforce). Also referenced as mattyp / poteto / roshan_s in tune-in posts. - [T] XFreeze tip: ask a Grok Bot to watch the livestream with you — real-time notes, screenshots, track what you care about (bot watching the bot). Fleet rules playbook - [T] kloss_xyz (from rewatching lingxi’s session): engineer bot onboards bots with fleet rules in one message; bots catch their own rule conflicts; turned into a stealable 22-rule fleet playbook. Workshop / session timestamps (tester recaps — useful for rewatch) - [T] 0xCarnagee (~1h workshop framing): 04:12 first bot from scratch · 28:40 engineers hand real work · 44:25 running product w/o a PM · 52:25 founder’s stack / starting to ship. WHAT IT IS - Livestream demo (101 / Founders “Introducing Grok Bot”): Create bots for different jobs; message bots like teammates; bots keep context in memory and improve; bots can be logged into your tools and use them like you do; automations/routines; share bots / shareable workflows / Shareable Templates. - Livestream demo (Why Grok Bot slide — 101 + Founders): Easy as iMessage; Always-on agents (24/7); Uses your tools like you; Finishes the work; Shareable workflows / Shareable Templates. - Livestream demo (“Finishes the work”): create bots for different jobs, give direction and let them figure it out, then set up automations and routines. - Livestream demo (Eng Why Grok Bot): No more caffeinated laptop; Beautifully available to all platforms; Control computer when needed; First-party coding agent integration. - Event framing (livestream): three-person team attempting to build a company/product in three days with Grok Bot; public X broadcast with “Grok Bot Galaxy” backdrop. - [T] Folder reinforcement: agent-native operating model (Human→Bot→specialists→humans); live build company name PLATFORM (tester claim). HOW IT WORKS / MULTI-BOT TEAMS - Livestream demo (101): Separate bots for separate jobs — left-side list with email/comms and slide bots; named work bots on demo slide included Sales Outbound, Chief of Staff, Inbox Manager, Website designer, and Debug. - Livestream demo (101 multi-bot): Shared conversation with Amrita Venkataraman plus Email Ethan, Data Dan, and Slide Sonya; Members panel with Add Member. - Email Ethan: drafts external notes/emails; outbound emails require Amrita’s approval before anything leaves. - Data Dan: numbers, surveys, charts; handed off Coffee Data (n=100, avg ~1.9 cups/day, median 2, mode 3; buckets 0→8, 1→23, 2→29, 3→32). - Slide Sonya: owned the Grok Bot 101 deck and new slides; created a chart on the last slide from Coffee Data before Ethan emailed Jason. - Multi-bot action pattern (livestream): assign each bot a narrow role, pass structured outputs between them, gate external communications on human approval, and sequence dependent work (chart first, email second). - Livestream demo (Eng Meet the team): Lingxixi — Chief of Staff; Craig — UI Engineer; Steve — Devex Engineer; Hogan — Infra Engineer; Jenny — Head of Operations. - Livestream demo (Eng / Founders live fleet): steve (chief of staff), tater (engineer), hashbrown (reviewer), mash, prototyper/grokpot, PlanetScale Bot; Founders roster also showed Founding Eng, Growth Eng, Knowledge Base Manager, Creative Director, drop (merch), foil (tickets), Sip, and more. - Livestream demo (Founders CoS handoff): “Needs your attention” — sign in to tdraw, then “I’m done, continue” / Skip; agent creates share link after human auth. - Livestream demo (PM lessons): Named agents + separate memory (broad mission, scoped memory); Agents all the way down — EM agents manage IC agents that spin Cloud Agents; hierarchy beats one mega-prompt. - Livestream tip (Eng): “restate in your own words before executing.” - Dashboard snapshots (livestream demos, not Official product SLA): Eng ~24 Bots / 353 Messages / 2 Working / 17 Active; Founders ~27 Bots / 910 Messages / 3 Working / 12 Active. - [T] kloss_xyz / lingxi: fleet onboarding via one-message rules; bots detect rule conflicts; 22-rule playbook pattern. - [T] 0xMorlex: Human sets direction → Bot coordinates → specialists execute → humans approve. COMMON USE CASES - Livestream slide “Grok Bot: Common Use Cases” organized by GTM, Engineering, Marketing, and Admins. - GTM — Account Health and Sales Outbound (livestream): pipeline built overnight; follow-ups drafted after every call; CRM kept current; outreach shipped in the user’s voice ready for review. - Sales Outbound demo (livestream): overnight pipeline/outbound — research prospects on the web, gather contact/account info from Salesforce, draft email in the user’s voice, check/update daily; routines included a morning outbound queue and an end-of-day send list; connected Gmail + Salesforce shown. - Engineering — Product Performance and Bug Reproduction (livestream): bugs reproduced overnight; repro pack dropped in the ticket; hotspots pulled before standup; outputs ready for review. - Marketing — Talent Scout and Paid Media (livestream): campaigns watched overnight; monthly budget drafted; creatives rotated when stale; spend shifts surfaced in Slack ready for review. - Admin — Chief of Staff and Expense Manager (livestream): calendars, travel, expenses, and inboxes handled end to end while the admin directs and bots run the busywork. SETUP AND ONBOARDING [] Livestream demo: first-time setup asks “What do you mainly want me for? Whatever you pick, we can refine from there.” [] Setup choices shown: Data & analysis (spreadsheets, metrics, charts); Research & digests; Workflows & routines (recurring checks, reminders, automated follow-ups); or Something else (free-text). [] Second create screen categories visible: Work & projects, Customer support, Research & …, Coding & tools, Not sure yet (exact small labels partly GAP). [] Tip: start with a broad job category and refine afterward; use free-text when presets do not fit. [] Settings/general (livestream): workspace/tool connection controls; visible toggle for automatic actions; tool/app list (exact toggle semantics GAP). [] Notifications (livestream): toggle — notify when the bot finishes or needs input. APPROVALS AND SAFETY [] Livestream demo (Google Form): bot surfaced an explicit action card with Approve and Deny before the computer/browser task — computer actions are not silently assumed. [] Action-history statuses shown: “Allowed once,” “Auto-review Paused This Action,” “Expired”; task runs on Grok Bot’s computer; live view of the bot’s computer/Google Forms made the external action inspectable. [] Tip: Review action history/status; one-time permission, paused review, and expiry are distinct states — do not treat them as completion. [] Closing 101 slide (livestream): bots get human approval when necessary; for enterprise use, external-facing actions should require approval; Email Ethan never sends an external email until its draft is approved. [] Tip/pitfall: confirm actions that create or change external artifacts. [] Founders cost slide (livestream): “Optimizing Costs” — “Routines are awesome (but audit them!)” with routine-manager UI. ENGINEERING SESSION - Livestream slide “Engineering Use Cases” / “Get Things Done when I am away”: instead of sitting in front of the computer to follow up with cloud agents, bots examine transcripts, read screenshots/proofs, and push back on your behalf. - Nightly Code Cleanup (livestream): every night at 3 a.m., bot researches the repo for quality gaps / improvements, then hands PRs when you wake. - TestFlight Seat Management (livestream): previously needed an internal tool for adding people via email; with Grok Bot, tell it the goal, have it build the MCPs, and automatically listen on Slack for requests. - Live pattern (livestream): cloud-agent-only code, human-owned merges; Steve stays quiet until a tree is named / night armed; one cleanup cloud agent per area; boards when a PR opens (owner=him); never merges; never touches others’ PRs. - Live Slack #pr-reviews (livestream): hashbrown Slack webhook (thursday-pr-notify) + SLACK_WEBHOOK_URL in GitHub Actions secrets; tater smoke pass succeeded; Lauren added thursday-pr-notify; Cursor automation may auto-trigger on matching PR-review messages. - Live routines shown: “Fleet watcher — Every 30 minutes”; “PO trip lookup — Every 5 minutes”; Flylo trip-lookup P0 agent with five-minute watch. PRODUCT / PM SESSION - Livestream slide “PM use cases: Three primitives that change how PMs work”: - 01 Attention List — filter Slack/email/meetings/Granola noise; surface focus; compare stated goals vs where time went. - 02 Research across customer context — Gong, Granola, Salesforce, Notion, support tickets, user research DB; synthesize where customers get stuck in the funnel. - 03 Shipping — Grok Bot represents a double-digit % of internal merged PRs; PMs express goals; agents decompose/allocate/review/integrate via Cloud Agents with codebase + secrets. - Live product example (livestream demo numbers, not Official public metrics): 1,453 ticket purchases Mon Sep 14; Mobile 612 (42%); Web 841 (58%); fare-select friction can delay booking when mobile is close. - Priorities visible: P0 Fare select (must ship); P1 Keep mid-funnel healthy; P2 Seat (optional). - Live PM workspace: fix sticky footer Continue + fare_selected (mobile_web / native); launch FUNNEL-P0-3 on booking-frontend; FUNNEL-P0-9 search+fare instrumentation Running with cloud agent in flight. - Product calls on screen: instrument mobile_web vs native from week 1; single-path prototype until A/B; seat stays P2. - Design lock: Pixel Direction A (Figma); Elian scaffold in A not B; acceptance to Elian (build), Einstein (QA), Nova (fare_selected on Continue). FOUNDERS SESSION - Livestream: Founders began after BRB interstitial; multi-person panel (chat referenced Eric / trykarat / Karat shirt — stage names not captioned on screen). - Agenda slide (livestream): Quick Intro; What Can Grok Bot do?; Why Grok Bot; Founder Demos; Power User Tips; Recap; Q&A. - Multi-agent org (livestream demos + audience framing): Brand/Coach/Work/Research; live roster examples Founding Eng, Growth Eng, Knowledge Base Manager, Creative Director; CoS pattern — start with Chief of Staff and have it recommend when other agents should spin up (audience pattern noted; live demo used steve as CoS). - Live build (livestream): tdraw board for Grok Bot art exhibition — Venues / Tickets / Merch wireframes; plan ticket front + HOLO, claim (tier → pay/claim), merch drop + item. - Merch agent “drop” (livestream): used Grok image for concepts; Soft Launch Bot Plush (~$28–38); Holo Stub Pin (~$14–18); poll for Drop 001 (Mission Patch Trio / Soft Launch Bot Plush / Holo Stub Pin / Remix). - Holo ticket demos (livestream, browser-verified tilt/flip): Prism Admit (rainbow foil/glint); Shader Lattice (WebGL liquid-crystal); Diffraction Pass (canvas grating, CSS emboss, foil edge). TIPS AND PITFALLS [] Livestream: one bot, one narrow job; pass structured handoffs; sequence dependents; gate outbound send/publish/spend on human approval. [] Livestream (Eng): treat bots like interns; think one level further when unblocks repeat; start with a feedback loop; restate before executing; human-owned merges. [] Livestream (PM): teach style from past Slack; silence is a feature for CoS; hierarchy of agents beats one mega-prompt. [] Livestream (Founders): audit routines for cost; CoS handoffs for sign-in; Shareable Templates / share bots once a workflow works. [] Livestream (101): review action cards — Allowed once ≠ completed; Auto-review Paused ≠ done; Expired ≠ success. [] [T] Fleet: one-message fleet rules; bots can catch rule conflicts (22-rule playbook). GAPS - Opening minutes of 101 and spoken narration across sessions: no captions/transcript; only slide/UI-corroborated claims kept. - Small on-screen text often illegible (routine times, settings toggle semantics, coffee-form question wording, some category labels, panel answers in Q&A). - Eng/PM/Founders: multiple Chrome memory-pressure tab discards and Aw Snap error 9 crashes; intervening content unobserved. - Founders: spinner stall (~2 min); formal end state not confirmed; subscription/pricing/Marketplace upgrade answers not reliably legible. - Speaker identities on 101/Founders often not captioned on-screen; chat names (e.g. Eric/trykarat) are not treated as Official stage IDs. - PLATFORM company name/slogan/site is a tester (oneillund) claim from stream UI — not an Official slide quote in Day 1 notes; treat as folder-sourced until corroborated on-slide.

Your GTM team already has a brain. It's scattered across the CRM, the call recordings, the product analytics, and the rep who's on holiday. Memory was never the hard part. Retrieval is. Five layers, in order, each with the artifact it produces. https://t.co/aEOl6rArs1

Most AI agents waste tokens on decisions that never needed text Jev turns routing, scoring, and verification into a fast decision layer I broke down the architecture most agent builders are still missing ↓ https://t.co/02POtifVJx