Tag: grok-voice

  • Voice Writes the Ticket. Cursor Does the Hands.

    Voice Writes the Ticket. Cursor Does the Hands.

    Inspired by Damon Chen (@damonchen), on connecting Grok Bot to Cursor so a ticket becomes a PR — 26 August 2026. First-party from the stack we run: Voice, a card, Cursor, Hub. Not a reprint of his connector list.

    Damon’s useful sentence is not the $200 line. It is this: a request lands, Cursor opens the repo, he wakes up to a PR. Bot is the router. Cursor is the hands.

    We run a smaller version of the same split. Voice on the walk writes the ticket — one next move, done-when, which site. Cursor on the Hub laptop touches the files. The chat window does not become the IDE. The IDE does not come on the walk.

    What each seat actually does

    • Voice — talk the work. Leave the session up. Share the screen when the object is already open. Do not hang up.
    • Card — Notion holds the seat: next move, due, who sits. Not the repo.
    • Cursor — one writer in the files. Serialize commits. Same rule as one WordPress lock.
    • Hub — live URL, git, receipts. Chat is last mile.

    Texas Twins Dad said it first in a thread we already honored: bot briefs, Cursor does the work, review the PR. We added the walk. Voice is how the brief gets written when your hands are full.

    What we will not do

    We will not ask Voice to edit ten PHP files while we cross a street. We will not ask Cursor to be the company memory. We will not let four agents open the same post ID because Voice said “just ship it.”

    Manasvi’s Cursor Ultra note is the other seed: Auto + Composer + Grok can finish the day on almost no usage if a human splits the scopes. The cost is babysitting. Opus-style swarm one-shots and then you cannot explain the diff. We take the babysit. Restoration pages and client repos are not a demo reel.

    If you cannot name which product is talking — Grok the app, Cursor the IDE, Bot the teammate, Premium+ the bill — stop and read Voice, Builder, and Bot Are Three Products. Confusion is how you buy four seats and still have no hands.

    Will Tygart — Tygart Media.
    Talk the ticket. Then sit down.

  • Leave Voice On. Share the Screen. Do Not Break the Thread.

    Leave Voice On. Share the Screen. Do Not Break the Thread.

    Inspired by Robster (@007_Robj), leaving Grok Voice on across devices while sharing docs and engineering notes — 3 September 2026. Official product facts from Grok release notes, 10 June 2026 and x.ai/grok. This is a new Tygart article from the stack we run. Not a reprint.

    The useful Voice habit is not a demo. It is leaving the session up.

    Robster’s line: keep Voice on while you move between devices, share the document in front of you, and do not restart the conversation every time the window changes. Grok’s own replies tonight said the same mechanism from the other side: start a Voice session, hit share, look at the paper together. No copy-paste loop.

    Upstream fact, not a screenshot thread: on 10 June 2026 the official notes shipped screen sharing in Grok Voice on iOS and Android. Grok sees the screen in real time so you can ask about what is in front of you without hanging up. Product page: natural back-and-forth Voice on web, iOS, and Android. If the spoken model still says share is missing, the notes say tap the button anyway. Docs beat the lag in the prompt.

    How we use it

    Walk with the buds in. Laptop stays on the Hub chat. Voice is the walk. The card in Notion is the next move. Cursor is the hands when something has to hit WordPress or git. That is the same map as Chat Is Last Mile and the receipt from walking five sites in Voice. Different job: those pages are “what shipped.” This page is “do not hang up.”

    • Start Voice. Leave it up.
    • Share the screen when the object is already open — Search Console, a draft, a moisture map, a PR.
    • Brief the next move onto a card. Do not store the company in the audio.
    • One writer on the CMS. Voice can draft. It does not pile four agents onto one post ID.

    Kayvon said the missing piece on a drive is two-way Voice on top of a digest. An MP3 you cannot answer is a podcast. A session you can interrupt is a desk. We want the desk.

    What this is not

    It is not “Grok Voice replaced the shop.” It is not a Voice Agent Builder tutorial. Builder and the 21 flagship voices live on x.ai/news. Use that page if you are casting a custom agent. This page is the human session you refuse to restart.

    Will Tygart — Tygart Media.
    We write about what we do, including the walk home.

  • Voice, Builder, and Bot Are Three Products

    Voice, Builder, and Bot Are Three Products

    Inspired by Nourhan (@beyrouti), on Grok Bot and outbound calls — 2 September 2026 — answering Alternate Jones. Official product facts from Introducing the Voice Agent Builder (1 July 2026) and 21 New Flagship Grok Voices. New Tygart article. Not a reprint and not a telephony cookbook.

    People ask Grok Bot to place the appointment call. Then they are surprised the teammate cannot dial.

    That is three products in one sentence.

    • Grok Voice in the app — the walk. You talk. Screen share. Connectors. Last mile. See leave Voice on (draft) and x.ai/grok.
    • Grok Bot — the teammate with a computer. Briefs, PRs, CRM updates. Official door: docs.x.ai/grok-bot.
    • Voice Agent Builder — the production phone agent. No-code. Telephony, tools, MCP, guardrails. Official door: x.ai/news/grok-voice-agent-builder.

    Nourhan’s point is the map: Builder is not inside Bot until someone wires them. Builder already has the number. Bot already has the computer. Consumer Voice already has your earbuds. Mash them in chat and you get a missing-feature thread.

    What the official Builder page actually ships

    Plain-language call flow. Documents, tools, guardrails. Bring a number over SIP or use a provisioned line. Speech-to-speech on Grok Voice, not a three-vendor STT / LLM / TTS sandwich. Voices live in Builder, the Voice Agent API, and TTS — including the July flagship set. Published rate on that news page: API audio at $0.05 / min, provisioned telephony +$0.01 / min. If those numbers move, the news page wins.

    That is a phone product. It is not “I walked home and published a WordPress draft.”

    How we split it

    • Walk and desk session: consumer Voice. One human. One writer on the CMS.
    • Teammate work: Bot + Cursor + Hub. Chat is last mile.
    • A number that answers or places a bounded call: Builder, on the official console, with a human on the irreversible step.

    We are not going to publish a bridge recipe. Twilio’s field CTO already said they are making the pipe easier. When xAI documents a first-party Bot → Builder dialer, that page becomes the spec. Until then, pick the product that already does the job.

    Will Tygart — Tygart Media.
    Name the product. Then sit in the right chair.

  • Voice Mode Can Use the Connectors. It Still Cannot Be the Shop.

    Voice Mode Can Use the Connectors. It Still Cannot Be the Shop.

    Inspired by official Grok (@grok), connectors in Voice Mode — 5 August 2026 — and X Freeze’s write-up of the same drop. Product facts from that post and x.ai/grok. New Tygart article. Not a reprint.

    The August drop was simple: Voice Mode can use the same connectors as chat. Mail. Calendar. The apps you already tied on. You talk. It acts. You do not look down to paste a thread into a box.

    That is the right shape for a walk. It is the wrong shape for a company brain.

    A builder comparing Claude and OpenAI this week said voice instructions never fired the task that chat fired. Grok’s move was to put the connectors inside Voice so the spoken turn and the tool call are one session. Use that. Then write the result somewhere that survives the hang-up.

    The walk rule

    • Voice + connectors: read mail, name the next meeting, flag the one thread that needs a human.
    • Card: one next move, plain language. Notion is the seat, not the drive.
    • Hub: the draft, the receipt, the live URL.
    • Hands: Cursor or one WordPress writer. See the write lock.

    Same stack as Chat Is Last Mile. Voice is a better last mile than typing while you walk. It is still last mile.

    The August Voice connector that turns a brief into a memo or a daily audio file is a digest. Useful on a drive. If you cannot answer it and change the board, it is an MP3. Keep two-way Voice for the work. Keep the memo as a readout.

    Builder and custom voices stay on the official news page: 21 flagship voices. Do not mix Agent Builder with “I left Voice on while I walked home.” Those are two products.

    Will Tygart — Tygart Media.
    Connect the walk. File the work.

  • Bespoke Subscriber Update: What We’ve Been Building with Grok Voice

    Bespoke Subscriber Update: What We’ve Been Building with Grok Voice

    Hi there —

    This one’s a personal note, not a newsletter blast. You’ve been on our list, and I wanted to tell you what we’ve actually been building lately, in plain language.

    The big idea: talking to the website

    We’ve wired up Grok Voice — a voice assistant — directly to the Tygart Media WordPress site. That means I can audit the site, clean up drafts, publish posts, attach images, set SEO metadata, and hand work off to other agents, all by talking. No dashboard clicking. No copy-paste. Just a walk and a conversation.

    As a proof of concept, we ran a full maintenance pass: health check, draft triage, taxonomy cleanup, featured images from the media library, internal linking, and a weekly automation that scans for new drafts, spam, and plugin updates every Monday morning.

    What we shipped this session

    • Published a batch of local Tacoma content — Mount Rainier, the Port, utilities, parks, workforce guides — properly categorized and tagged.
    • Optimized and published two longer personal essays: Email Is the New API and The Pile Is Substrate.
    • Cross-linked the restoration product pages so the operating system, job tracker, equipment tracker, and claims tools point at each other.
    • Built a Restoration Industry Knowledge Base in Notion — vendors, standards, KPIs, pitfalls — structured so any restoration company can duplicate it and let Grok Voice fill it in.
    • Handed off a v1.0 productized version to be finished, uploaded to the Square shop, and turned into sales content.

    What’s next (the interesting part)

    The next layer is bespoke outreach. Instead of one generic email to the whole list, we’re connecting FluentCRM so Grok Voice can read each subscriber’s history and send a genuinely personal note — what we’ve built, what fits them, what to try first. No secrets, just the useful stuff.

    You’ll be among the first to get one of those. If you want to jump ahead, the restoration ops kit and the knowledge base are the places to start.

    Thanks for being on the list. Talk soon,
    Will