No-Code Agentist

GROK BOT HOW TO USE Sources: official https://t.co/2EN1BbJ794 + https://t.co/0OVb26msAp + your Grok Bot bookmark folder (851 posts) Updated: 2026-09-09 WHAT NEW TODAY - Folder 851 posts (8 new vs Sep 8) - Official (bot): fill out forms and logins for your Bot without leaving chat; any password manager supported - Testers (XFreeze): login bottleneck fix — Bot pauses for your auth (1Password / Apple Passwords / any manager), then continues the job (flights, shopping, work tools) - Testers (LaceyPresley / muskonomy): amplify in-chat logins, forms, checkouts, even booking flights - Testers (mattyp): 300+ attendees at the Grok Bot coffee pop-up; more events on the way - Grok Bot team (poteto): building Grok Bot with the team; points at Lenny Rachitsky interview with product lead Roman Ugarte - Testers (muskonomy): Lenny Rachitsky exclusive with Grok Bot product lead Roman Ugarte (how it started / where it is going; dropped Sep 8) - Testers (MarioNawfal): amplify cloud 24/7 — each Bot runs on its own computer even after you close yours 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 [] Official (bot, Sep 8): fill out forms and logins for your Bot without ever leaving the chat, with support for any password manager [] 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 (LaceyPresley / muskonomy): in-chat logins/forms also cover checkouts and booking flights [] 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:

10 insane ChatGPT 6 Astra prompts you need to try: 1. Turn a SaaS into an agent in Hermes / Grok Bot. “Analyze [SaaS product / URL] and identify the outcome customers pay for. Map its workflow, inputs, outputs, and manual decisions. Check available APIs, MCP servers, native integrations, authentication requirements, and permissions. Use browser automation where supported if no suitable API exists. Build an agent in [Hermes / Grok Bot] that completes one valuable, recurring workflow. Explain what it replaces and what still depends on the SaaS. Create its instructions, triggers, memory, approval rules, and error handling. Prevent duplicate actions and keep credentials secure. Deliver the configuration, supporting code, and setup steps. Test with sample data and report what works, what’s blocked, and what needs human input.” 2. Find money I forgot to collect. “Compare my proposals, completed work, invoices, and payment exports for [period]. Find work that was delivered but never invoiced, partial payments, overdue balances, and billing mismatches. For each finding, show the source records, amount, and why it needs attention. Separate confirmed discrepancies from items that need clarification. Create a tracker ranked by amount and urgency, then draft the relevant invoice or follow-up message for my review. Don’t invent charges or contact anyone.” 3. Take over my CapCut video edit. “Open [project] in CapCut using available browser or desktop controls. Turn this footage into a [30–60 second] video for [platform], using [reference] as the editing direction. Pick the strongest opening, cut dead air, tighten the pacing, and add accurate captions. Balance the audio, fix awkward cuts and errors, then export in [format]. Keep the project editable and flag anything you couldn’t complete.” 4. Build a 3D world I can walk through. “Use Blender and Godot through available integrations to build an explorable 3D scene based on [concept / reference images]. Start with one detailed area using [provided assets]. Add lighting, textures, collisions, and first-person controls. Include three objects I can interact with and environmental details that tell a story. Run the scene, test movement and interactions, fix broken collisions and missing assets, and deliver the editable project with launch instructions. Check the required tools first and flag anything unavailable.” 5. Turn a Salesforce opportunity into a working sales demo. “Read the discovery notes, call summaries, and requirements attached to [Salesforce opportunity]. Identify the client’s main problem and build a working demo showing how [our product / service] would solve it. Use realistic fictional data tailored to their industry and workflow. Focus on the scenario most relevant to the buying decision, and clearly label simulated integrations. Test the demo, fix broken interactions, and deliver a shareable version with a short walkthrough I can use on the next sales call.” 6. Turn my spreadsheet into a live operations dashboard. “Analyze [spreadsheet] and map its formulas, metrics, and data sources. Build a working dashboard connected to the available APIs or databases, with automatic refresh and a visible last-updated timestamp. Highlight overdue work, capacity issues, and metrics outside agreed targets. Let me filter by team, client, and period, then inspect the records behind each issue. Validate the calculations against the spreadsheet, flag stale or missing data, and deliver the dashboard with setup instructions. Clearly label any data sources that still require manual uploads.” 7. Turn a research paper into a working simulation. “Read [paper / PDF] and identify a core model or experiment that can be reproduced computationally. Extract its equations, assumptions, parameters, and required data. Flag missing details instead of inventing them. Implement it and build an interactive simulation where I can change key parameters and explore the results. Compare the output with the paper’s reported results, explain discrepancies, and distinguish reproduced findings from approximations. Deliver the working code, charts, and instructions to rerun it.” 8. Turn my API into a tool agents can use. “Read [API documentation / OpenAPI spec] and build an MCP server that lets agents perform [key tasks]. Define clear tool names, descriptions, inputs, and outputs. Implement authentication, input validation, pagination, rate-limit handling, and useful error messages. Keep credentials secure and distinguish read-only tools from actions that change data. Test the main tools against a sandbox or clearly labeled mocks. Deliver the working server, setup instructions, and an example showing an agent completing a real workflow.” 9. Turn my command-line tool into an agent skill. “Inspect [CLI tool / repository] and package its most useful workflows into a reusable agent skill. Read the documentation, identify required dependencies, and define when the skill should run. Create instructions and supporting scripts for [key tasks], with input validation, useful errors, and a preview mode for destructive actions. Keep credentials out of prompts and logs. Test a successful run and a failure case. Deliver the installable skill, setup steps, and example prompts.” 10. Turn my website into a site agents can use. “Inspect [website / repository] and identify the main tasks visitors complete. Add structured tools using WebMCP where supported, so compatible agents can search, compare, fill forms, and prepare actions through explicit inputs and outputs. Reuse the site’s existing validation and permissions. Require confirmation before purchases or submissions. Test with a compatible agent client and deliver the code, setup instructions, and a demo of one complete workflow.”

I gave Tencent’s @TencentHunyuan Hy4 preview one prompt and it built a full racing game. A complete, playable top-down racer: car physics, drifting, AI opponents that stay on track, lap timers, a minimap, skid marks, and engine sounds generated on the fly. One prompt. No follow-ups. It scoped the project, implemented it end to end, and fixed its own bugs before handing the code back. People are debating Hy4 preview’s benchmark scores, but Tencent seems to have optimized for something more practical: actually completing the assignment. Multi-step planning. Tool use that doesn’t collapse after a few steps. Long-horizon execution that keeps coherence and doesn’t return a half-broken project. And yesterday they shipped an upgraded Hy4 preview that materially cuts down on back-and-forth and token usage faster “thinking,” fewer turns, and a noticeably smoother experience. The physics is where most models fail: steering that tightens at speed, momentum that feels consistent, and drift that isn’t just cosmetic. Weaker models rotate the car instantly and call it “done.” AI opponents reliably following waypoints around a closed circuit is another quiet failure mode I’ve seen even from “frontier” systems. @TencentAI_News Hy4 preview did it on the first attempt. If I were you: Grab WorkBuddy, select Hy4 preview, and paste in a real build task—not a toy. Something with moving parts that usually breaks agent workflows. Then run the exact same prompt against whatever you use now. Same environment. Only swap the model. See which one ships a working game and which one ships an apology. A lot of labs charging frontier prices are about to have an uncomfortable week. Try @WorkBuddy_AI here: https://t.co/cTHO3DD9FU

Handling Nearly 1M Calls, This Voice AI Startup Secures Another $15M Core JudgmentWhile European enterprises face severe hiring shortages and surging call volumes, Berlin-based startup telli secured a $15M Seed round (bringing total funding to $18.5M). Operating with a lean team of 6, telli processed nearly 1 million calls while maintaining over 50% MoM revenue growth. Rather than simply building another voice chatbot, telli enables enterprises to deploy custom voice agents directly into business workflows. 01 / THE BOTTLENECK OF SCALING IS ALWAYS THE PHONE LINEThe three founders previously scaled customer support operations at German solar unicorn Enpal. They realized that as companies expand, the primary operational bottleneck isn't product or sales—it's call volume outstripping hiring speed. Instead of optimizing traditional call centers, telli automates routine phone workflows by letting enterprises directly "hire" voice agents. 02 / NOT A ROBOT, BUT A PHONE AGENT FACTORYtelli’s platform, telli Studio, operates as a no-code factory for phone agents: No-Code Workflow Builder: Companies configure operational flows without coding. HVAC firms automate service scheduling, real estate agencies manage viewing confirmations, and recruiters handle first-round candidate screenings. Model-Agnostic Infrastructure: Clients can swap underlying LLM and voice models (Claude, OpenAI, ElevenLabs, Cartesia) without losing their configured business logic. 03 / THE HARD PART IS INTEGRATION, NOT CALL HANDLINGMaking AI answer calls is trivial today; integrating AI into live operations is complex. The real challenge lies in post-call data syncing, system API calls, human-in-the-loop triggers, and compliance with GDPR and the EU AI Act. Serving solar, HVAC, real estate, and recruiting, telli treats the phone call as an operational entry point rather than a simple communication tool. 04 / REDEFINING THE CALL CENTERHistorically, enterprises purchased call center software where software fielded calls and humans executed tasks. That dynamic is inverting: enterprises expect AI to directly execute bookings, screenings, confirmations, and follow-ups. Voice AI is shifting from "answering calls" to "executing business operations." ======================================== Xử Lý Gần 1 Triệu Cuộc Gọi, Startup AI Này Tiếp Tục Nhận 15 Triệu USD Đánh Giá Cốt LõiTrong bối cảnh Châu Âu đối mặt với tình trạng thiếu hụt nhân sự và lượng cuộc gọi tăng vọt, startup telli tại Berlin vừa hoàn tất vòng Seed 15 triệu USD (tổng vốn đạt 18.5 triệu USD). Khi chỉ có 6 người, telli đã xử lý gần 1 triệu cuộc gọi và duy trì tốc độ tăng trưởng doanh thu hàng tháng trên 50%. Thay vì làm một bot thoại thông thường, telli cho phép doanh nghiệp tự triển khai các Agent giọng nói vào quy trình vận hành. 01 / TĂNG TRƯỜNG NHANH NHẤT, NƠI DỄ NGHỄN NHẤT LÀ ĐIỆN THOẠICác sáng lập viên từng làm quy mô hóa CSKH tại kỳ lân năng lượng mặt trời Enpal (Đức). Họ nhận ra khi công ty phát triển, điểm nghẽn lớn nhất không phải sản phẩm hay bán hàng mà là cuộc gọi. Lượng điện thoại tăng nhanh hơn tốc độ tuyển dụng. Thay vì tiếp tục tối ưu call center, telli tự động hóa các cuộc gọi có quy trình cố định bằng cách để doanh nghiệp tự "tuyển" Voice Agent. 02 / KHÔNG BÁN ROBOT, BÁN MỘT "NHÀ MÁY" AGENT THOẠISản phẩm telli Studio đóng vai trò như một nhà máy tạo Voice Agent dạng no-code: Cấu hình không cần viết code: Doanh nghiệp chỉ cần đưa quy trình nghiệp vụ vào. Công ty nhiệt lạnh tự động đặt lịch bảo trì, công ty bất động sản xác nhận lịch xem nhà, công ty tuyển dụng hoàn thành vòng phỏng vấn đầu tiên. Linh hoạt chọn mô hình: Doanh nghiệp có thể chuyển đổi giữa các mô hình (Claude, OpenAI, ElevenLabs, Cartesia) mà không lo mất đi quy trình nghiệp vụ đã thiết lập. 03 / CÁI KHÓ THỰC SỰ LÀ TÍCH HỢP VẬN HÀNH, KHÔNG PHẢI NGHE ĐIỆN THOẠICho AI nghe một cuộc gọi hiện nay không khó. Cái khó là đưa nó vào quy trình đang chạy hàng ngày: đồng bộ dữ liệu sau cuộc gọi, gọi hệ thống nào, bước nào cần con người xác nhận, tuân thủ GDPR và EU AI Act ra sao. Phục vụ từ năng lượng, bất động sản đến tuyển dụng, telli biến cuộc gọi từ công cụ giao tiếp thành đầu vào của quy trình kinh doanh. 04 / TÁI ĐỊNH NGHĨA CALL CENTERTrước đây, doanh nghiệp mua phần mềm call center để con người xử lý công việc. Hiện tại, thứ tự này đang đảo ngược: AI trực tiếp thực hiện đặt lịch, sàng lọc, xác nhận và theo dõi. AI giọng nói đang chuyển dịch từ "nghe điện thoại" sang "làm nghiệp vụ."