How personal AI fits into daily life: dots, Muse, Grok Bot and Instinct

Can an interview transcript become clips, show notes and social copy, with later edits carried across the set? Can school notices turn into a family calendar and a supplies list? Can recurring research and email preparation continue after one handoff? dots, Muse, Grok Bot and Instinct belong in one view because each explores assistance that keeps context, enters existing tools and carries work forward.

OpenAI dots connects Astra to a cloud computer and ongoing tasks. Meta Muse produces plans and checklists while extending toward glasses and Charm. Grok Bot gives recurring work a role and cloud workspace. Instinct uses messages and calls for everyday requests. Their interfaces make delegation feel familiar, while the work they emphasize and the outputs they leave differ.

This topic starts with official examples and outputs, then connects firsthand accounts and later projects, distinguishing software characters from device interfaces. The table maps uses and entry points; task records explain how well they work.

October 5 correction: dots here means the ongoing assistant OpenAI introduced at DevDay. The initial version used material about an unrelated iPhone app with a similar name; it has been replaced.

In OpenAI’s creator scenario, Iggy finds moments in an interview transcript, prepares show notes and social posts, then carries feedback across those materials. The official illustration turns one copywriting request into continuing creative work: tone, audience and accepted edits inform the next batch.

Astra, a cloud computer and browser, and relevant conversations, memory and preferences support this continuity. dots can research, work with files and run software. Create it on desktop, then continue in a supported mobile app. Local projects require the connected computer online with ChatGPT open. OpenAI also relays an early tester’s missed invoice being prepared and sent after approval; that is a vendor-reported case.

SLIDEFACTORY’s Mark Nguyen reports roughly five hours of early-October agency work: dots found calendar conflicts, joined Slack, summarized a PDF and, through the agency’s own tool, completed crawls of 44 and 111 pages on two sites. Email and rescheduling remained unfinished, and the first scheduled report had not arrived. The completed outputs and open tasks show what the first day established.

Creer also reports using existing Markdown, JSON and handoff files to resume two local projects and continue edits and tests separately. The DevDay topic follows how saved material becomes a starting point for the next step.

• Follow the two local projects and their handoffs →
• Read how dots setup, memory and computers work ↗

Muse’s team published an India itinerary, a school information page and a checkable packing list: material from a conversation becomes something to reopen and use. The team also describes extracting dates from school emails and preparing supplies. These official outputs and accounts connect the idea of a personal assistant to recognizable everyday work.

Charm and glasses change how a person hands off a task. At Connect, Mark Zuckerberg held a physical Muse Charm prototype, with its avatar on the screen. Meta also announced Muse for AI glasses: looking at a shelf product, a notice or a school-supplies list could provide context without describing it. The announced Charm prototype is designed around pocket-sized real-time voice interaction; launch details are still to follow.

Software, devices and makers connect here: Muse works in a personal Secure VM and browser; hardware makes the same agent easier to reach. The ESP32 firmware and Linux SDK in Muse Gadgets offer makers routes through buttons, displays and sensors. The next useful evidence is a working project showing why its particular form improves an interaction.

• Continue to Charm, Home Link and maker-built devices →
• Explore the team’s outputs and design walkthrough ↗

Grok Bot’s official marketing demo combines launch copy in Figma and Notion with a team campaign recap. Another official example starts from a weekly CRM list, adds web and Slack research, and leaves outreach drafts for review. The role lasts beyond one question, with material and outputs in existing work tools.

Give a Bot a name and responsibility, then message it from phone or desktop. It works with a persistent cloud computer, files, browser and connectors. Official documentation says cloud work can continue after the laptop closes, and Bots can divide work. A weekly job can therefore retain material, methods and corrections across runs.

James Swierczewski’s outreach account gives a concrete process: the Bot proposed a list, contact research, email drafts and a tracker, with final sending left to him. When tracker files were invisible, it moved records and drafts into chat. The account makes output visibility tangible. Grok Companions emphasizes character and voice conversation; this chapter follows the work-focused Grok Bot.

• Continue to shared material and methods in Grok Team Bots →

Instinct’s official examples are familiar: arranging an airport ride, booking a handyman or following up on a dropped thread. Its interfaces are messages and calls, with an emphasis on understanding current work and personal priorities. These product descriptions make the intended everyday situations clear.

It connects relevant context from email, messages, screen, audio, location and devices, then uses a phone and computer to pursue the task. It may initiate a message or call. Familiar communication becomes a place for delegation and follow-up. Later experience can show whether an agreement survives and whether the assistant returns at the useful moment.

The public page does not state regional eligibility, and available work depends on connected services. For bookings or contacting others, establish who gives the final confirmation. Instinct’s terms also require a separate request to delete indexed information after disconnecting a service. These conditions affect ongoing use.

A TechRadar writer asked Muse to find shorts: it requested a size, returned options and a discount, then asked for an Amazon login before purchase. In a separate savings challenge, the writer reported about $35 saved against a promoted $1,000 target. The accounts show steps from options toward action, while keeping one person’s result distinct from general performance.

dots’ project accounts and Grok Bot’s outreach job raise another question: once work resumes, does it return somewhere the person can inspect and continue? The former has completed summaries and crawls alongside unfinished email and reporting; the latter moved invisible files into chat. The concrete observations are completed steps, usable outputs and who takes over next.

Personal Agent Bench adds external teardowns and task records for Muse and Instinct. Its first-round results use different task sets and sample sizes, so they are not a head-to-head ranking; the team also discloses that it builds agent software. The material helps ask better questions about runtime, memory and outcomes, ahead of future matched-task comparisons.

Start with a familiar job whose finish line you know. Interview and social-material revisions explain dots’ creative continuity; family travel, school notices and supplies explain Muse’s everyday outputs; weekly research, drafts and recaps explain Grok Bot’s ongoing role; coordinating rides or repairs by message explains Instinct’s interface. These scenarios help frame a choice, then your own results test it.

Specify the output: a checklist, review-ready drafts or changes in the original tool. Watch whether accepted requirements survive, how new material changes the result, and how it returns when blocked. Keep a clear confirmation point for payment, bookings and external sending. Inspecting results and correcting memory should be as easy as handing off work.

This topic will continue with artifacts, longer use and matched-task comparisons: revisions across dots’ creative materials, continuity through Muse glasses and Charm, visible outputs from Grok Bot routines, and completed everyday arrangements with Instinct. Those concrete changes will develop the relationships between these four products.

• Continue to dots’ project-handoff accounts →
• Continue to Muse hardware and Home Link →
• Continue to team use of Grok Bot →