Grok Bot Q&A #1

Summary

Matt Palmer and Eric answered questions about Grok Bot’s integrations, automation, memory, and newer features. They emphasized that Grok Bot can connect information across services and carry out tasks that would otherwise require manual work or custom scripts.

Features and integrations discussed

• Apple services: Connectors include Home, Calendar, Reminders, alarms, and location services. The speakers did not confirm whether iMessage integration is coming.
• Vault and 1Password: Vault can securely store details such as addresses for form filling. The bot can use stored information without directly seeing the underlying values, similar to a password manager. The speakers described Vault as a lightweight Grok Bot option that can complement, rather than necessarily replace, 1Password. Broader credential-provider integrations are expected over time.
• X Money: One speaker was exploring the connector. They noted that X Money can create one-time virtual cards for purchases. Bot-to-bot payments and expense splitting were discussed as possibilities, not confirmed features.
• Pages: Bots can create reports, dashboards, visualizations, and simple interactive websites or games. Examples included weekly work summaries, fitness-analysis heat maps, social-post analytics, and a Doom-style game. Under the hood, Pages was described as similar to a React app built with a standardized set of components and a design system.
• Team bots and collaboration: Team bots can turn recurring internal tasks into shared tools. The speakers likened this to “every app could be a bot.” Broader multiplayer and group-chat support was described as still in development. They also mentioned Slack and Microsoft Teams integrations.
• Bot-to-bot and Cursor workflows: With the Cursor plugin, Grok Bot can exchange information with live Cursor project agents—for example, finding context in Slack and sending it to a project. Projects can also message bots back. The speakers described this as useful for passing bug reports and other work between people’s agents, with a human involved.
• Models: Grok Bot uses a mix of models and selects one it considers suitable for a request.
• Memory: There is user-level memory shared across bots, as well as bot-specific memory. Users can ask Grok Bot to add, change, or remove memories. Skills were described as a separate way to encode repeatable knowledge or workflows.
• Email forwarding: Bots can forward messages from their own inboxes while preserving the original formatting.
• Image-to-video: A bot can turn a supplied image or description into a video. One example used Grok Imagine to animate an image with moving bars and text.
• Usage tracking: The usage-and-billing area includes a per-bot view for identifying which bots or routines consume the most tokens.
• Computer use: Cursor’s computer-use feature was described as available to try; Grok Bot computer-use work was still underway. The speakers highlighted its potential for testing apps through the same interface a person would use.

Tips, examples, and guidance

• Try asking what the bot can do. The speakers recommended experimenting and stating your intent. They said asking directly is often how they discover useful capabilities.
• Connect the tools you use most. More integrations can help the bot find relevant context across email, Slack, Notion, and other services.
• Build trust gradually. One speaker described using Grok Bot to onboard at work by asking it questions before contacting coworkers, then relying on it more as he learned what it could do.
• Look for repeatable tasks. Review prompts and routines you use often, then consider turning them into a routine, skill, or dedicated bot.
• Example routine: Eric described a “Scout” bot that checks Slack, Notion, and projects and sends him a morning briefing of notable company updates.
• iPhone shortcut: Matt said an iPhone Action Button can be remapped to open a Grok Bot voice call instead of Siri. He referred viewers to a post on his profile for the setup steps.

Main speakers

• Matt Palmer
• Eric (surname not stated in the subtitles)