No-Code Agentist

GROK BOT HOW TO USE Updated: 2026-09-20 WHAT NEW TODAY - Folder 950 posts (2 new vs Sep 19) - Testers (samarthgowda215, Sep 19): After setup — single-Bot bottleneck when you have more than one task; waiting for finish before next job - Testers (kocer_eth, Sep 19): Six boundaries before adding Scout/Copywriter/CFO specialists — make every action legible before irreversible 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) - Testers (unicodef1wn, Sep 10): plans don’t stack — linking SuperGrok to a Cursor plan adds zero usage; upgrade within Cursor or turn on on-demand if you need more - 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 - SpaceXAI notes (blankspeaker, Sep 9): Version 0.47.0 — auto lock team review; auto review team rules - Official Elon (Sep 17): Grok Bot now has a voice - Grok Bot team (poteto, Sep 17): talk to grok bot — voice is live - Testers (mattyp, Sep 17): you can now talk to bot - Grok Bot team (lingxi, Sep 17): voice baked toward huddle / voice-call feel with your AI teammate - SpaceXAI notes (blankspeaker, Sep 17): Version 0.56.1 — ability to connect and see that the connection is still in progress - Official (jediahkatz, Sep 17): ~10% more effective usage — less subagent overuse, less bot-to-bot chatter, smarter low-effort batch routing; group chats are token-heavy - SpaceXAI notes (blankspeaker, Sep 16): Version 0.55.0 — pull logins from 1Password on your Mac (auto-refresh when a saved password changes) - SpaceXAI notes (blankspeaker, Sep 15): Version 0.53.0 — bugfixes - SpaceXAI notes (blankspeaker, Sep 15): Version 0.52.0 — ability to pin an agent in your sidebar - SpaceXAI notes (blankspeaker, Sep 9): Version 0.44.0 — marketplace of bots; multi-person Bot; voice overheard/speech tags - SpaceXAI notes (blankspeaker, Sep 10): Marketplace redesign + chat right pane + Voice calls — Voice now live (Sep 17); marketplace/pane may still lag - Testers (techdevnotes, Sep 9): Desktop Network Debugger - Testers (mattyp, Sep 4): iPad app available (official docs may still lag) - Testers (XFreeze, Sep 12): Grok Bot now directly inside Grok on iOS, Android, and the web — open/switch/manage from the Grok sidebar; no separate Grok Bot app required - Testers (tetsuoai, Sep 12 bookmark): Grok Bot now native in Grok for SuperGrok Heavy — sidebar on web, iOS, and Android - Testers (nima_owji, Sep 11): Grok Bot available in the Grok Web App - Testers (GrokBotRadar quoting techdevnotes): SuperGrok Heavy users seeing Bots in Grok web UI (limited/gradual; no official announcement) - Testers (XFreeze, Sep 12): SpaceXAI Grok Bot Guides library (101, Engineering, Support, Templates, multi-Bot teams, mobile, Design, GTM, PM) - SpaceXAI notes (blankspeaker, Sep 13): Soon interact with Grok Bots in XChat on Android and iOS X apps - Testers (XFreeze, Sep 17): Grok Bot embedding deeper into XChat — chat with Bot from XChat; link Grok account to view your Bots inside XChat (shipping soon) 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 (samarthgowda215, Sep 19): one Bot waiting to finish before the next task is a bottleneck — run parallel specialist Bots instead of serializing on one [] 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) [] Testers (B_doong2daddy, Sep 15): prefer boring specialist Bots (Inbox/Research/Ops/Code Review/Scheduling) over one super-Bot; Bot built MCP on local NAS and connected a Roborock [] SpaceXAI notes (blankspeaker, Sep 15): pin an agent in your sidebar (v0.52.0; may or may not be finished/active) [] 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 BYOK, multiplayer, and hang-error messages as missing (iPad now available per mattyp); Voice calls are now live (Sep 17) — talk to your Bot; speed/language picks may still expand [] Official Elon / Grok Bot team (Sep 17): Grok Bot now has a voice — talk to bot [] Testers (SPAC89, Sep 17): Voice mode — ~15 min EN+ES under 1% weekly limit [] Testers (XFreeze, Sep 17): Grok Voice #1 on task-completion success rate vs other voice models; same model powers Grok Bot voice [] Testers (kloss_xyz, Sep 17): 8 voice uses — morning briefing, exception-only updates, decision escalation, completion reports, agent standups, live review, EOD debrief, approval gates; teach when NOT to talk [] Official (bot, Sep 18): Grok Bot can now send you voice notes [] SpaceXAI notes (blankspeaker, Sep 18): v0.57.0 — steer away from group chats; see in-progress tasks + text [] Testers (ab_workss, Sep 18): Phone widget — keep several Bots in sight or focus on one [] 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) [] SpaceXAI notes (blankspeaker): v0.44.0 worked on browse a marketplace of bots; use a Bot with more than one person; overheard/speech tags on voice [] SpaceXAI notes (blankspeaker, Sep 10): redesigned Marketplace coming — plugins and bots on the front page, For You, Featured, categories, search, and installed (not live yet) [] Testers (XFreeze, Sep 10): SpaceXAI releasing actual sales-team Bots as installable templates (prebuilt context, connectors, routines) [] 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) [] Testers (XFreeze, Sep 11): Grok Bot for Engineering guide — lingxi fleet (5 engineer bots, 200+ cloud agents, Jenny ops Bot); official [] Testers (tetsuoai): third-party template Apple Dev by Evan — ListMachines/machineId Mac, Xcode/simulators/Swift from phone HOW TO WRITE A TASK [] Outcome: what should be finished [] Testers (unicodef1wn): Grok Bot meters agent steps and tokens, not messages — vague tasks wander and burn the week; scope with Task / Work in / Context / Done means / first N items then stop [] 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 [] Testers (SPAC89, Sep 14): use normal Grok 4.6 chat to improve your Grok Bots — Heavy mode launches multiple agents; Expert mode good for auditing each Bot [] Testers (Michael_Fenech_, Sep 14): before trusting a Bot with more responsibility, score accuracy, how much it finishes without coming back, and related quality bars — not only “did it finish?” [] Testers (MarioNawfal, Sep 14): Grok Bot can pull numbers/decisions/takeaways from a long meeting or talk into a short scannable brief [] Testers (mattyp, Sep 11): Bot responses now support diagram rendering and LaTeX [] Testers (GrokBotRadar, Sep 17): Research/compare/decide in Grok; open apps / change / send / finish in Grok Bot — Grok thinks, Grok Bot acts [] Testers (ericosiu, Sep 17): call new marketing leads in under 60s — qualify, advance, log to HubSpot [] Testers (Michael_Fenech_, Sep 18): want Grok Bot on Apple CarPlay so routine updates become a spoken catch-up on the drive AGENT COMPUTER AND LOGINS [] Open Agent Computer from the conversation to watch the desktop [] Testers (techdevnotes, Sep 9): Grok Bot Desktop now has Network Debugger [] Testers (techdevnotes, Sep 13): Grok Bot now allows you to send Bot Computer web traffic through your device [] Official Elon (Sep 14): Grok Bot now lets you route through your local machine (Bot Computer egress via your IP / local machine) [] Testers (XFreeze, Sep 14): Grok Bot Computer also gets updates — update whenever a new one is available; updating interrupts any Bot currently working [] SpaceXAI notes (blankspeaker, Sep 10): chat right pane coming — Media, Computer (watch the bot’s screen), and Routines (not live yet) [] 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 [] Official (bot, Sep 8): fill out forms and logins for your Bot without ever leaving the chat, with support for any password manager [] SpaceXAI notes (blankspeaker, Sep 16): v0.55.0 — Grok can pull logins from 1Password on your Mac, including auto-refresh when a saved password changes [] SpaceXAI notes (blankspeaker, Sep 17): v0.56.1 — ability to connect and see that the connection is still in progress (may or may not be finished/active) [] Testers (XFreeze): when a site needs your account, Bot pauses; you auth with 1Password / Apple Passwords / any manager; Bot continues — no pasting credentials into chat [] Testers (XFreeze, Sep 16): Disk Saver — when Bot Computer storage runs low, audits space and suggests safe clears (caches/temp/duplicates); nothing deleted without your approval [] Testers (LaceyPresley / muskonomy): in-chat logins/forms also cover checkouts and booking flights [] Grok Bot team (poteto, Sep 9): account switching is finally here [] Official (bot, Sep 9): Share a file directly with Grok Bot on mobile [] 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 [] Coinbase (coinbase, Sep 9): Coinbase for Agents on Grok — connect Coinbase at https://t.co/aL6KKYjGXH; tell Grok to trade, analyze, automate; no MCP setup [] Testers (XFreeze, Sep 10): sales/GTM connectors — Salesforce, HubSpot, Gong, Clay, Granola + other GTM tools so Bots can pull account context, research prospects, prepare follow-ups [] Official (bot, Sep 11): Grok Bot can now search and act across Microsoft Teams for you [] 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 [] Testers (paranoidream, Sep 14): Bot served a bots’ hall as A-Frame/WebXR over local HTTPS; opened in Quest Browser on the same Wi‑Fi (no-code VR room) 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 [] Testers (unicodef1wn): never trigger on every new message (docs warn broad listeners eat usage); pick one channel and one keyword; audit forgotten dailies [] Testers (unicodef1wn): add to every routine — if the source is unavailable, report the failure instead of using old data; test run before you schedule [] 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 [] Testers (kocer_eth, Sep 19): put six boundaries in place before adding Scout/Copywriter/CFO specialists — make every action legible before it becomes irreversible [] Use a group chat when the handoff itself should be visible [] SpaceXAI notes (blankspeaker): v0.44.0 worked on using a Grok Bot with more than one person [] 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 (liam_fallen, Sep 13): weekly Chief of Staff 1:1s with each Bot — what did you do / went wrong / need / should change; fixes what it can and brings the rest to you [] 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 [] Official (bot, Sep 9): ask your Bot to draft messages inline for you to approve before sending FIRST BOTS WORTH CREATING [] Inbox manager for email and Slack triage EVENTS - Official bot (Sep 15): LIVE Grok Bot Galaxy Day 1 — mattyp / poteto / roshan_s build a company from scratch in 3 days; Eng/PM/Founders sessions OFFICIAL LINKS - Overview:

Hermes Agent, the Build Track. Part 1 of 4. Ten builds of copy-paste prompts, every one checked against the official Hermes docs. This part: day one, SOUL.md, and the two memory files. The whole masterclass is free on GitHub: https://t.co/fJgpc03O7y https://t.co/nttGBhudYq

The Hermes Desktop Masterclass, part 1 of 2. The app the docs describe but never set up for you: install, the window, the settings that matter, capabilities, gateways to your other machines. Prompts to paste, checks to run. Free: https://t.co/fJgpc04lX6 https://t.co/7kK89jFYUI

GROK BOT GALAXY Updated 2026-09-20 Sources: Day 1–3 livestream sessions + Grok Bot Galaxy bookmark folder (103 posts, user-X MCP) NEW TODAY - Folder 103 posts (+1 vs 102). - Testers (DAIEvolutionHub / Lauren Tan): skip 1-agent mode; run CoS + PM + 20+ workers with loop & graph. 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). GROK BOT GALAXY Updated 2026-09-20 · Folder: Grok Bot Galaxy (id 2099917541162324015) Sources: Day 1–3 livestream sessions + Grok Bot Galaxy bookmark folder (103 posts, user-X MCP) Count: 103 posts · +1 new scrape_via: MCP (LOCK_SKIPPED_MCP_ONLY) WHAT NEW (+1 folder · no new session notes) - [T] DAIEvolutionHub (Lauren Tan / SpaceXAI): most people run 1 agent without loop & graph; stack = Chief of Staff + PM + 20+ workers (fully autonomous fleet). Watch the 1h workshop, then build the fleet. URL: DAY 1–3 KEEP - Multi-bot fleets; message like teammates; memory + routines; Shareable Templates; Away mode; audit routines - Eng maturity Autocomplete→…→Autonomous; PM Attention List · Research · Shipping; Founders CoS crew - Day 2: SDR / Sales / Support; Day 3: Mkt Ops / Post-Sales / Marketing / Wrap 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. 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). - Do not treat audience chat as product claims (buffering complaints, note-taking suggestions, Cursor/subscription questions, brand-partnership asks were chat — not slides/demos). 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. 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). 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. 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. 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). 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). 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. 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.

GROK BOT GALAXY Updated 2026-09-19 NEW TODAY - Verification/CI guardrails (tester spectnfa): feature map for agents · evals as skill unit tests · cloud agents reproduce bugs · ban useEffect/comments at CI · compiler as next guardrail after code review - Eng fleet loops (tester 0xShoopy): Slack 24/7 unblock · X bug→reproduce→fix→PR · nightly 3 AM cleanup · red-CI auto-fix (page after 10 min) · P0 check every 5 min · playbook bot broadcasts new rules - Post-Sales overnight (tester 0xGenAi / Blake): morning status board · call prep 15–20 min before · Slack/email/history/product updates · screenshots when done · laptop closed - Marketing demo (joshkim / SpaceXAI): audit product · landing page · paid campaigns · automate end-to-end - CoS stop wall first (tester kocer_eth): one entry · evidence gate · ownership line · human stop wall · action log · STOP ALL kill switch - Shared-login warning (tester maestrooth): all bots share every login on the cloud computer; screens ≠ trust boundaries - Workshop timestamps (0xwhrrari / arle0x): first bot → real work → no-PM product → founder stack; 4-layer stack → templates → phone mode - Fleet scale cite (DAIEvolutionHub): CoS + PM + 15+ workers / 10–20 cloud agents in a loop PRIOR 0918 FOLDER HIGHLIGHTS (was WHAT NEW 2026-09-18 · 89/+20 · Day 3 sessions folded) Day 3 official + slate (folder) - [O] bot: Day 3 live — building a company with Grok Bot; sessions for marketing and customer success. - [O] poteto: free Ultra window (new accounts) + “we are launching our game today!” - [O] mattyp: one-month free promo window live; later thank-you to first-stream friends. PRIOR 0916 HIGHLIGHTS (kept; full prior merge below) - [T] DevinSoto Day 1 notes pack: named price tiers; agents-as-colleagues; Away mode; D7; audit browser routines; Day 2 = Sales. - [T] ChrisSimpson / Shub: group-chat bots bill climbs — tag separately, set model per task, forget over-ref context, take bots out of group chat. - [T] tetsuoai / poteto: codebase as agent memory. 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/Y6LvquLoJX; 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. 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). - Do not treat audience chat as product claims (buffering complaints, note-taking suggestions, Cursor/subscription questions, brand-partnership asks were chat — not slides/demos). 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. 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). 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. 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. 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). 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). 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. 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.

Jev claims 193x faster AI workflows. The practical idea: stop using a writing model for every routing decision. Here’s an inbox example, a cost calculation and a test brief you can give your coding agent. https://t.co/FVophuFShg

𝗧𝗵𝗲 𝗔𝗜-𝗣𝗼𝘄𝗲𝗿𝗲𝗱 𝗔𝘂𝘁𝗼𝗻𝗼𝗺𝗼𝘂𝘀 𝗗𝗔𝗢 𝗔𝗴𝗲𝗻𝘁: 𝝰𝗶 Protocol Execution Managing operational tasks inside DAOs—such as executing routine transactions, updating parameter settings, and rebalancing liquidity—requires continuous voter sign-off and manual intervention. Deploying autonomous AI agents governed by smart contracts automates routine operational tasks safely within user-defined parameters. When DAOs deploy autonomous agents via Web3 wallets, protocol management becomes efficient. 𝗔𝗜𝗡𝗙𝗧 provides autonomous agent setup models for DAOs at https://t.co/aznYQECnaV. By linking governance wallets, DAO teams can configure AI agents to handle operational tasks autonomously on-chain. Automate your DAO operations today through three straightforward steps. 𝗚𝗲𝘁𝘁𝗶𝗻𝗴 𝗦𝘁𝗮𝗿𝘁𝗲𝗱 1️⃣ Connect Governance Key: Authenticate your DAO wallet address at https://t.co/aznYQECnaV. 2️⃣ Select Autonomous Agent Module: Choose AI models configured for automated transaction execution and parameter monitoring. 3️⃣ Set Execution Boundaries: Define smart contract rules and deploy your operational agent on-chain. 𝗪𝗵𝘆 𝗔𝗜𝗡𝗙𝗧 𝗠𝗮𝘁𝘁𝗲𝗿𝘀 𝗔𝗜𝗡𝗙𝗧 elevates DAO productivity by delegating repetitive operational workflows to intelligent software agents. - Automated Routine Execution: Process operational tasks at https://t.co/aznYQECnaV automatically according to DAO governance parameters. - Transparent Bounded Execution: Ensure AI agents operate strictly within code-enforced smart contract boundaries. - Wallet-Bound Authorization: Authorize and update agent permissions using your DAO cryptographic wallet. - Native Token Billing: Settle agent operational compute costs using decentralized crypto payments. This framework allows DAO members to focus on high-level strategic direction rather than manual maintenance. 𝗧𝗵𝗲 𝗕𝗶𝗴𝗴𝗲𝗿 𝗣𝗶𝗰𝘁𝘂𝗿𝗲 The future of organization lies in human-AI collaboration on open blockchain networks. Delegating routine execution to autonomous AI agents frees human energy for creative and strategic governance decisions. 𝗔𝗜𝗡𝗙𝗧 anchors this organizational evolution via https://t.co/aznYQECnaV. It constructs the essential interface connecting DAO governance with autonomous machine execution. Decentralized organization management will no longer be slowed by manual operational friction. It will be powered by open Web3 portals that bring sovereign, automated artificial intelligence to protocol management worldwide. @AINFTcom @justinsuntron #TRONEcoStar

Actionist Builder on @ActionModelAI This is where you create workflows and send them to the Marketplace. Top banner first: Builder Epoch #9 = 5% revenue. Publish this month and that rate stays on those workflows. What the page is for: build no-code automations, test them, then publish so other people can run them. On the main screen: - Workflows Created / Published / Pending - Total Installs, Views, Points earned - Drafts and Submissions + Create Workflow How to create one: 1. Click Create Workflow 2. Add Title and Description 3. Add Domains (required) 4. Optional: Success Criteria, Pre-Requirements, Tags 5. Build the flow in Node Editor 6. Add Variables, Rules, Ask Human if needed 7. Save as Draft or Submit Workflow How you earn: - someone runs your workflow, - actions consume $LAM, - you get the epoch rate locked at publish time. This page is empty until you create the first one. Start with Create Workflow. Full walkthrough of the Builder and the create form in the video 👇

Jev can't write a single sentence, and it's the most interesting model launch I've seen this year. I spent some time on the docs, the critics, and what people built. What it is, how it works, and where the hype outruns the facts: https://t.co/kpXxlvwWZu

Jev is a super-fast, cheap AI that only makes yes/no or score decisions—not full answers. In AI agents (bots that do multi-step tasks), a “harness” is the control code around them. The tweet says Jev’s best job isn’t picking models or checking tools. It’s spotting “drift”: when the agent starts wandering off the original goal. Like a friend saying “hey, you’re getting off-topic” without fixing it for you. Score every step, nudge it back. Runs constantly, costs almost nothing, and the person writing the prompts doesn’t have to change anything.

https://t.co/pv3XHUud5u