Grok Bot Workshop: Attention Lists, Agent Teams & Cloud Agents with Roshan and Kevin
打开互动全文版(中英对照 + 朗读 + 问答)→SpaceX AI 产品团队的 Roshan 与 Kevin 演示 Grok Bot 的注意力列表、智能体团队与云端智能体如何服务产品工作流。
Roshan and Kevin from the SpaceX AI product team demonstrate Grok Bot's attention lists, agent teams, and cloud agents for product workflows.
大家好。我们马上就开始。在等的这段时间,如果你从没用过 Grok Bot,就在聊天区发个 0;用过就发个 1。这能帮我们大致了解大家的使用情况。好,看到很多 1 和 0 进来了。Noah,你在统计这些吗?
Hey everyone. We'll get started here in a second. While we wait, feel free to drop in the chat a zero if you've never used Grok Bot before, or a one. It would help us orient how much people have used it. Okay, seeing a lot of ones and zeros coming in. Noah, are you tallying all these up?
我正在心算。
I'm doing the mental math right now.
官方统计是五个。哇。
You have the official count of five. Wow.
我估计大概是一半一半。我们该搭个机器人来计数。太好了。我喜欢这种有创意的编号。
I'd say it's about a 50/50 split. We should set up a bot to do the count. That's great. I like the creative numbering.
好,欢迎大家。如果你用过 Grok Bot,就在聊天区发个 1;没用过就发 0。好,很多专家刚加入。
All right, welcome everybody. Drop a one in the chat if you've used Grok Bot before, zero if you haven't. Okay, a lot of experts just joined.
我喜欢这个投票,因为它看起来像一串二进制流,就像有个机器人在聊天区打字。很酷。非常好。那我们开始吧。大家好,我是 Kevin Neparco,来自 SpaceX 的 AI 产品团队。非常兴奋能和我的同事一起为大家展示面向产品工作的 Grok Bot。
Well, I like this poll because it looks like a binary stream, like a robot just typing in the chat. It's cool. Very good. Let's kick things off. Hello everybody. I'm Kevin Neparco over from the SpaceX AI product team. Very excited to be presenting Grok Bot for product with my colleague.
大家好,我是 Roshan,也在 SpaceX 的产品团队。我花了很多时间使用 Grok Bot,也在幕后参与它的开发。很兴奋能给大家展示一点我们每天是怎么用它的。
Yeah. Hey, I'm Roshan, also on the product team at SpaceX. Have been spending a bunch of time using Grok Bot and working on it behind the scenes. So excited to show you guys a little bit about how we use this every day.
太棒了。今天还有 Noah 加入,他会主持今天的讨论。Noah,你要不要介绍一下自己?
Awesome. And we are joined by Noah who will be moderating today's discussion. Noah, do you want to introduce yourself?
好的,很高兴见到大家。我叫 Noah,在 AI 部署团队。整个演示过程中,大家随时可以在聊天区提问。我会回答这些问题,也会把一些话题抛给你们。
Uh yeah, great to meet everybody. My name is Noah. I'm on our AI deployment team here. Throughout the presentation, feel free to drop questions in the chat. I'll be answering them as well as probably surfacing some topics up to you guys.
太好了。我想从一个很大的变化说起,这个变化我们大概都清楚,那就是不仅产品管理这门手艺在变,所有人构建软件的方式也在变。我特别喜欢 DHH 最近在 Lex Fridman 播客上的那句话,这位“开发者的开发者”我觉得很好地抓住了这个时刻,那就是“软件即产品管理”。产品该做什么?为谁而做?怎么做?该长什么样?优先级是什么?这些问题是现在每个人在构建产品和软件时都有能力去琢磨的。每个人都可以像产品经理一样思考。所以非常兴奋能聊聊 Grok Bot,以及我们在 SpaceX AI 产品团队里是怎么用它的。那么接下来,我想先分享一下我们为什么要做 Grok Bot 的背景。
Amazing. I wanted to start with a big change which I think we are probably all well aware of, which is not only is product management, the craft of product management, changing, but so too is the way in which everybody is building software. And so I really like this DHH quote off the Lex Fridman podcast recently, the developer's developer, I think really capturing sort of this moment, which is software is product management. What should the product do? Who should it do it for? How should it do it? How should it look? And what are the priorities? These are all questions that now everybody is capable of wrestling with as we start to build products and software. Everybody can be thinking like a product manager. And so very excited to talk about Grok Bot and the ways that we've been using it on the SpaceX AI product team. And so with that, wanted to share a little backdrop of why we built Grok Bot.
是的。我觉得先讲一些总体背景、讲讲 Grok Bot 为什么存在会很有帮助。我们在筹备这次分享时就在想这些,浮现出了几个主题,很多灵感来自我们内部的使用,也来自我们过去自己做产品时从很多客户那里听到的反馈。我觉得有几个主题浮现出来。第一个是,人们越来越想和智能体一起工作,而这些智能体在聊天框里并不太自在。其实聊天框非常棒,我一直在用聊天框,很喜欢用它和 LLM 做各种交互、跑各种 AI 工作流,但要让智能体真正把活干完,聊天框就有点局限、有点束缚了。所以我们真的很想思考,什么才是和智能体交互的正确界面、正确方式。而且如果你把它放到产品管理工作的语境里,这就更明显了,对吧?产品经理往往专注于结果,经常要跨多个层面工作,要和公司里各种不同职能协调,有点像总经理,要思考设计,要大量思考分析,还要和工程团队合作。后面演示里你们会看到一点我们是怎么设置的。但产品管理这项工作,似乎确实超出了聊天框那种原生的一问一答格式。另一个逐渐浮现的主题是,智能体真的需要自己的环境来干活。我们早期在云端智能体上就看到了很多这一点:让智能体能够验证自己的工作、验证输出结果,会带来好得多的结果。所以想法就是,那自然的延伸是什么?我认为就是给智能体自己的环境去干活。我们越开始实验、越玩这个,就越发现这可能是一件非常强大的事。最后我想提的一点是,同时照看多个智能体线程真的很难。我们内部有很多人自己搭了某种协调智能体,再去调用其他智能体,但这从来没有在产品层面被真正做成一等公民。我们认为 Grok Bot 在这方面做得不错,但核心想法是,当你在多任务处理时,从这个话题的会议一切换到那个话题的会议二,总得有办法把正常工作日的这一团乱麻理清楚。我们越来越开始想,如果我们能和智能体更像同事一样协作,而不是更像软件一样操作,会怎样?这基本上就是 Grok Bot 很多设计的设计纲要。
Yeah. Yeah. So I thought it'd be helpful to just kick off with some general context and kind of why Grok Bot exists. And we're thinking about this when putting this together, and a few themes sort of came up, and a lot of this was inspired by our internal usage as well as what we heard from a bunch of customers over the history of building our products ourselves. And I think a few themes emerged. One of those first ones is that it sort of increasingly felt that you wanted to work with agents and those agents weren't quite at home in a chat box. I think the chat box is actually really great. I use chat boxes all the time. Really enjoy them for all kinds of interactivity with LLMs and AI workflows, but for something about agents getting work done, it felt a little bit limiting and constraining. And so really wanting to think about what the right interface is and the right way to interact with an agent would be. And I also think if you kind of contextualize that to product management work, this becomes even more salient, right? Like PMs are often trying to focus on outcomes. You're often working across multiple parts of the stack. So you're coordinating with various different functions at a company. You're like kind of a general manager. You're kind of thinking about design. You're thinking about analytics a lot. You're working with engineering. And you'll see a little bit about that and how we've set it up in the demo later on. But really that PM work in particular seems to go beyond this Q&A format that is really native for the chat box. The other thing that was a really sort of emerging theme is that agents really need their own environments to get work done. We actually saw a lot of this with cloud agents early on, where giving agents the ability to verify their work and verify their output results in dramatically better outcomes. And so the idea was, well, what's the natural extension of that? And I think it's giving agents their own environments to do the work in. And I think the more we started experimenting and playing with that, the more we saw that that could be a really powerful thing too. The last thing I wanted to mention here is that it gets really hard to babysit multiple agent threads. We had a lot of folks internally who had built their own sort of coordinator agent that was then calling out to other agents, but that wasn't ever really done in a really first-class way across products. And we think Grok Bot does a pretty good job at this, but really this idea of, as you're thinking about multitasking, you're switching between meeting one over here on this topic to meeting two over here on that topic, having some way to just keep track of all the mess that goes on in a normal workday. And I think we increasingly just started to think of ourselves as, well, what if we could work with our agents more like colleagues versus working with them more like software? And that was kind of the design brief for a lot of what Grok Bot is.
那么沿着这个主题再讲一会儿,关于“智能体即同事”,我想点出四件事。为什么这个区分这么重要?因为它是 Grok Bot 设计、运作方式以及我们对路线图思考的很多灵感来源。我们认为,同事更专注于把各种工具串起来、产出结果。显然,连接器、MCP 和集成一直是整个行业智能体叙事中非常有力且重要的一部分。我觉得这里令人兴奋的是,让你能把这些工具串起来把活干完。所以我认为这是整个叙事中非常重要的一部分。我认为长时运行的上下文和记忆在这里非常重要。例行程序在这里也很重要。所以在产品里把这些做成一等公民,真的很棒。同事会记得你做的事,你和他们共事,他们记得你做了什么。所以让这成为解决方案的一部分非常重要。
So to carry on that theme for a little bit, four things I wanted to call out here around agents as colleagues. And why this distinction is so important, I think, is because it's a lot of the inspiration behind the design of Grok Bot and how it works and how we're thinking about the road map too. So we think that colleagues really focus more on tying tools together to produce outcomes. Obviously connectors and MCPs and integrations have been a really strong and important part of the agent story across the industry. I think what's exciting here is making it so that you can tie those tools together to get work done. And so I think that's just a really important part of the story. I think long-running context and memory is really important here. Routines are really important here. And so thinking of first-class ways to do those in the product is really great. Colleagues remember what you do, like you work with them, they remember what you do. And so having that be a part of the solution is really important.
我认为同事是独立的,所以要确保智能体也能独立——回到这个想法:智能体有自己的电脑、自己的设备去做事,有自己的软件去协作。最后我觉得把消息传递的感觉做对,也是非常重要的一部分。我在 Slack 上给 Kevin 发私信时是连珠炮式的,有时还会甩几个梗图和表情。我觉得那种体验本身就很有趣,让你感觉像是在和一位同事共事。所以希望这些主题对你们这些一开始在聊天里刷了所有关键词、用过 Grok Bot 的人来说是说得通的。希望你们已经看到了一些。但我想这就引出了:Grok Bot 到底是什么?我想在说了那么多之后把它简化成两件事。如果你们在谈论 Grok Bot、或者跟朋友同事聊起它时,有两件事:第一,它是一个有电脑的智能体。我觉得我们对其中“电脑”这部分非常兴奋。它给了智能体自己的机器、自己的运行环境,就像我刚才说的。它真的就像在给一位有自己电脑的同事发消息。第二,你的机器人团队真的是 AI 队友。它们是你可以交付真实工作的 AI 队友。它们端到端完成任务,卡住时会回来找你,运作起来就像同事一样。我很兴奋地看到 X 和其他地方有很多人在说,Grok Bot 似乎更像是一个“做事”的智能体。非常期待这继续成为我们所构建的东西。
I think colleagues are independent, and so making sure agents can be independent — calling back this idea of agents having their own computers, their own devices to do things on, their own software to go work with. And then finally I just think getting the messaging to feel right is a really important part of this. When I DM Kevin on Slack I'm rapid-fire messaging and sometimes throwing in some memes and emojis. I think there's something about that experience just being really fun that makes it feel like you're working with a colleague. So hopefully these themes make sense for those of you who had all the ones in the chat at the beginning from having used Grok Bot. Hopefully you've seen some of this. But I guess that brings us to: well, what is Grok Bot? And I want to simplify this after all of those words into two things. If there are sort of two things that you're using when you're talking about Grok Bot, or when you're talking about it with your friends and colleagues: the first is that it's an agent with a computer. And I think we're really excited about the computer part of this. It sort of gives the agent its own machine, its own environment to operate in, just like I was talking about. And it really just feels like texting a colleague who has its own computer. And the second is that your team of bots really are AI teammates. They're AI teammates that you can give real work to. They finish jobs end to end. They come back when they're stuck, and they function just like colleagues. And I've been pretty excited to see a lot of folks on X and other places talking about how Grok Bot seems to be more of a doing agent. So really excited for that to continue to be what we build.
是的,我觉得我们想融入 Grok Bot 的一点,就是去思考和你最好的同事、最好的搭档或队友共事是什么感觉。那是什么样的?他们通常非常主动,有行动偏好,能根据你的指引采取真实行动,他们在工作中学习。所以我们试着把很多这样的原则直接融入产品。
Yeah, I think one of the things that we wanted to incorporate into Grok Bot is thinking about working with your best colleague or your best coworker or teammate. What is that like? Well, they're generally very proactive. They have a bias to action. They're able to take real action based off of your guidance. They learn on the job. And so we try to incorporate a lot of those principles directly into the product.
是的。我觉得还有一些有趣的方式,比如你可以训练它们做某些事,像教一位和你共事的人那样去教它们。
Yeah. And I think there are some fun ways too, like you can train them to do certain things and kind of teach them as if you would teach someone you're working with.
完全同意。非常酷。
Absolutely. Very cool.
你要不要带我们过一遍这个团队是什么样的?
Do you want to walk us through what the team looks like?
好的,没问题。在这次演示中,我们会过几个非常令人兴奋的、产品经理专属的用例,但这其实可以推广到任何类型的产品构建者。所以在我们讲的过程中,请想想你自己的流程、你可以自动化的东西、你可以构建的不同机器人,我们可以在聊天和最后的问答环节聊这些。我发现 Grok Bot 非常有用的一点,是帮我保持专注。所以我有一个“注意力清单”的概念,它不一定是进入这一周或这一天的严格优先级,而更像是我的注意力在哪里。我喜欢把 Grok Bot 想象成坐在我肩膀上,能够审阅进入我收件箱的所有邮件,看看我在回复什么,看看我实际参与的 Slack 讨论串,也许还有我需要知道但漏掉的 Slack 讨论串,然后整理出这份注意力清单,再以不同方式使用它。我们可以聊它如何作为过滤器让你保持专注,如何把它和你的优先级清单做对比,从而理解你的优先级可能在哪里偏离了你时间实际花的地方,有很多非常有趣的方式可以开始用这份注意力清单来真正引导你的工作。另一个是,在新产品开发的基础攻坚上,能够非常快速地研究一堆不同的上下文。正如 Roshan 提到的,作为产品经理,上下文可能存在于 Notion、Slack、Gmail 以及许多其他界面——你的支持工具、你的 CRM,对吧?所以能够有一个智能体、一位可以共事的同事,帮你收集、综合这些信息,并把它转化为新的产品方向——非常令人兴奋,我们会深入讲这个用例。当然,我们还需要能够发布,需要能够把新产品推向市场。所以我们会聊一些我们构建的工作流和智能体,帮助我们加速发布。我们要过一遍我们构建的团队。这是 Roshan 和我以及 SpaceX AI 的产品团队发现对产品管理非常有用的东西的组合。那么,来认识一下团队。首先是 Kora。Kora 是我们的幕僚长。你可以把 Kora 想成做所有幕僚长该做的事:弄清楚对我们和团队来说最重要的是什么,能够减少干扰、挡掉一些事情,也许自动回复一些进来的问题,帮助我们在个人和团队层面保持专注和有条理。接下来是 Emily。Emily 是一位工程经理。Emily 被训练和教导不要真的去写代码——就像一位好的工程经理那样——而是去管理一个工程师团队。这些工程师既能从我们历史上在 SpaceX AI 推送的现有代码和 PR 中学习,也能学习一些最佳实践,把 SpaceX AI 一些最优秀工程师的技能编码进去,从而能像工程师一样工作。我们还有 Ashley。Ashley 可能是我一天中的首选,能够对我们的数据提问。Ashley 可以访问我们的数据湖和数据仓库,以及一堆不同的用户洞察和用户研究库。所以你可以问非常宽泛、笼统的问题,Ashley 会为你构建正确的图表、正确的幻灯片或正确的洞察来回答你的问题。作为产品经理,一天中会冒出很多问题,能够有一个人你直接发消息就能很快得到答案,这极其有帮助。Pete——PM Pete——是我们的小产品助手,会帮忙写很多 RFC 和产品需求文档。他也能跑那些研究,在这些不同智能体之间协调,真正帮我们构建一个高效运作的产品。还有我们的设计师 Pixel。聊聊 Pixel 吧。
Yeah, absolutely. So for the course of this demo we're going to run through a few of the really exciting PM-specific use cases, but this really generalizes for any type of product builder. And so as we go through, be thinking about your own workflows, things that you could potentially automate, different bots that you could potentially build, and we can talk about those in the chat and Q&A at the end. One of the things that I found Grok Bot to be very helpful with is keeping me focused. So I have this concept of the attention list, which is not necessarily what are my strict priorities going into the week or the day, but more like where is my attention. And so I like to think about Grok Bot as sort of sitting on top of my shoulder, being able to review all of the emails coming into my inbox, see what I'm responding to, see the different Slack threads that I'm actually engaging with, maybe the Slack threads that I need to know about but am missing, and curate this attention list that can then be used in different ways. And we can talk about how that can be a filter to keep you focused, how that can be diffed against your priority list so that you can understand where your priorities may diverge from where your time is actually going, and there are a lot of really interesting ways in which you can start to use this attention list to really guide your work. The other is, for the blocking and tackling of new product development, being able to very quickly research a bunch of different contexts. As Roshan mentioned, being a product manager, there can be context which lives in Notion, in Slack, in Gmail, and many other surfaces — your support tools, your CRM, right? And so being able to have an agent, a colleague that you can work with who can help you collect that, synthesize that, and formulate that into new product directions — very exciting, and we'll go deep into that use case. And then of course we also need to be able to ship. We need to be able to deliver new products to market. And so we'll talk about some of the workflows and agents that we have built to help us accelerate shipping. So we're going to go through the team that we have built. This is a combination of things that Roshan and I and the product team over at SpaceX AI have found to be very useful for product management. So let's meet the team. First we have Kora. Kora is our chief of staff. You can think of Kora doing all of the chief of staff things: figuring out what is most important both for us and the team, being able to reduce the distractions and block some of the things, maybe auto-respond to some of the questions that are coming in, and helping keep us focused and organized both personally and as a team. The next is Emily. Emily is an engineering manager. Emily has been coached and taught not to actually write code — like a good engineering manager — but instead to manage a team of engineers. And so these engineers are able to both learn from existing code and PRs that we have historically pushed across SpaceX AI, and learn some of the best practices, encode some of the skills from some of the best engineers across SpaceX AI, to be able to work just like an engineer. We also have Ashley. Ashley's probably my go-to throughout the day, being able to ask questions of our data. So Ashley has access to our data lake and our data warehouse and a bunch of different user insight and user research repositories. And so you can ask very broad and general questions and Ashley is going to be able to build you that right chart or that right slide or that right insight to be able to answer your question. And as a PM throughout the day, many questions will come up, and being able to have somebody that you can just DM and get an answer back really quickly has been exceedingly helpful. Pete — PM Pete — is our little product assistant, and so will help with a lot of our RFC and product requirement doc writing. He can also run that research, coordinate across these different agents, and really help us build a high-functioning product. Or we have our designer, Pixel. Talk about Pixel.
是的,其实我最近花了很多时间和 Pixel 一起工作。
Yeah, I've been spending a lot of time working with Pixel actually.
是的,我认为设计是那种用 LMS 和 AI 工具很难做好的事情之一。但我其实是受到 Lenny 最近一篇 newsletter 文章的启发创建了 Pixel。那里有一位非常出色的设计师发布了一个设计系统,我把它拿来,把一些上下文放进了 Grok Bot,你还可以用其他设计最佳实践来补充。我觉得这是做设计比较有趣的方式之一。Pixel 当然可以访问 Figma,所以它能进入 Figma 帮助做设计和幻灯片,也能访问我们的设计系统,这样当我们想做一些符合 Grok Bot 品牌或 SpaceX AI 品牌其他部分的东西时,就有一个非常强的起点,以及 Pixel 随时间建立起来的一套很强的技能,懂得如何有创意、灵活,成为一个出色的 AI 设计师。
Yeah, I think design is one of those things that's really hard to get right with LMS and with AI tools. But I actually created Pixel inspired by a recent newsletter post from Lenny. There was a really great designer who posted a design system there, and I took that and put some of the context into Grok Bot, and you can supplement that with other design best practices. I think it's been one of the more fun ways to do design. Pixel has access to Figma, of course, so it can get into Figma and help make designs and slides, and also has access to our design system so that when we want to make something that matches the Grok Bot brand or matches other parts of the SpaceX AI brand, there's a really strong starting point and a really strong set of skills that Pixel's built over time to understand how to be creative and flexible and just be a great AI designer.
非常好。是的,正如 Roshan 提到的,产品经理通常身兼多职,所以能有一个同事、一个智能体可以求助来完成很多这类工作,是非常有帮助的。而且对于产品领导层的人、正在组建产品组织的人来说,团队里有一个招聘专员也非常有帮助。那就是 Rey。Rey 可以帮助我们找到优秀的人才,并引导候选人完成我们的产品面试流程。你可能会问自己一个问题:为什么要有多个智能体?能不能只有一个智能体?我想我们把它提炼成了几条有用的原则,说明为什么多个智能体或多个同事确实最合理。第一,如果你把它映射到当今的组织和公司的构建方式,通常会有专精于某个领域的专家。这对于可参照性也非常有帮助,对吧?知道有数据问题时该找谁,有设计问题时该找谁,并且知道他们是这些领域的专家。你还有范围记忆,对吧?每个智能体都在工作中学习。你在指导他们,给他们反馈。所以他们能学到不同的东西。然后你还可以并行运行许多这样的智能体,我们可以谈谈我们如何与智能体私信以及这种新的工作流程。感觉更像是在 Slack 或 Teams 里和同事聊天。
Very good. And yes, as Roshan mentioned, PMs often wear many hats, and so being able to have a colleague, an agent that you can turn to for a lot of this work is very helpful. And also for people in product leadership, people who may be building a product organization, it's also very helpful to have a recruiter on the team. And so that is Rey. Rey can help us find amazing talent and help steward candidates through our product interview process. One of the questions you may be asking yourself is why are there many agents? Could this just be one agent? And I think we've distilled this down into a few helpful principles of why multiple agents or multiple colleagues really makes the most sense. One is just if you map it to today's organizations and the ways in which a company is built, you generally have specialists who are really good in a particular area. It's also very helpful for referenceability, right? So knowing who to turn to when you have a data question versus a design question, and knowing that those are specialists in those areas. You also have scope memory, right? So each agent is learning on the job. You're coaching them. You're giving them feedback. And so they're able to learn different things. And then you can also run many of these agents in parallel, and we can talk about how we DM with our agents and this new workflow. It feels a lot more like just chatting with a colleague as you may in Slack or Teams.
是的,可参照性对我来说非常重要,因为我觉得我只是需要某种方式让我的大脑跟上每个人在做什么。我知道我们谈了很多关于同事的类比,但我觉得这一点对我真的很有帮助。我试过只有一个智能体,我的大脑处理不了。你懂我的意思吧?所以是的,我觉得这很重要。
Yeah, the referenceability one is huge for me because it feels like I just need some way for my brain to stay on top of what everyone's working on. And so I know we talked a lot about that colleague analogy, but I think that one really helps for me. I've tried having just one agent and my brain can't handle it. You know what I mean? So yeah, I think that's huge.
酷。好的。我们想展示一些令人兴奋的演示。所以我们想展示这个团队如何协作构建一个示例功能。我们把镜头移到 Grok Bot 这边。先给大家定位一下,如果你是在我们收集时在聊天里打了 0 的人,意思是你之前没用过 Grok Bot,那么这就是 Grok Bot。我们真的希望你能试试。我听说在最后可能会有一些有趣的积分送给大家。所以如果你想轻松尝试,就请留到最后。但本质上,Grok Bot 就是要简单。它很简单,左边有一堆机器人。你可以把最常聊的机器人置顶,希望你在这里看到我们刚提到的一些名字。你会看到我们的幕僚长 Kora。你会看到分析师 Ashley,产品经理 Pete 和 Emily。你会看到下面的工程师团队。你还可以对这些机器人进行分组和组织,给它们标签,自定义它们的头像。所以这真的是一个让你个性化、让它成为你自己的机会。我在这里还想指出的是,这些机器人的很多能力来自它们可以连接的工具。我们谈到过,特别是对产品人员来说,这些工具是我们工作中非常重要的一部分,对吧?比如我每天要在 10 个 SAS 应用之间切换。所以想展示这个市场也是非常重要的一部分。显然你可以有插件。我们分了类别。从智能体编排工具到收件箱工具,这里有 MCP。还有很多研究专用工具,如果你用 Koda 或 OneDrive 的文档,设计工具等等。所以我鼓励大家第一次设置时,就浏览一遍,把你用的所有工具都链接上,让它们都连接起来。一旦你设置一次,每个智能体都会受益。我觉得这真的很有帮助。那么,好的。我们想展示什么?我想,也许我们应该从构建一个功能开始,看看效果如何?
Cool. All right. Well, we want to get to maybe some exciting demos. And so we thought we would show you this team in action to build an example feature. So we'll pan over to Grok Bot here. And just to orient you, if you were one of the folks who put a zero in the chat when we were gathering, meaning you have not used Grok Bot before, well, this is Grok Bot. We really hope you try it out. We might have some fun credits coming your way, I hear, towards the end of this. So stick around if you want to make it really easy to try it out. But essentially, Grok Bot is meant to really just be simple. It's meant to be simple where you have a bunch of bots on the left here. You can pin those bots for the ones that you're talking with most and hopefully you're seeing some names here that we just talked through. So you see our chief of staff Kora. You see Ashley, our analyst, PM Pete and Emily. You see our team of engineers down here. You can also group and organize these bots, give them labels, customize them, their avatar. So really just a chance for you to personalize and make this yours. The other thing I wanted to call out while we're here is a lot of the power that these bots get come from the tools that they can connect to. And so we talked about particularly for product folks how those tools are just such an important part of our job, right? Like I'm living across 10 SAS apps each day. And so wanted to show that this marketplace is a really important part of this too. And so obviously you can have plugins. We have categories where we've broken these down. Everything from agent orchestration tools to inbox tools, MCPs that are in here. There's a bunch of research specific tools, documents if you're using Koda or OneDrive, design tools, etc. And so really one of the things that I encourage folks when they're getting set up for the first time is to just go through this and link all the tools that you're using and get them all connected. And once you do that set up once, every agent benefits. And I think that's really helpful. So, all right. So what do we want to show? I guess maybe, should we start with building a feature and see how that goes?
好的,我们开始吧。我们先和幕僚长聊聊,感受一下如何与 Kora 聊天。我们看看我的收件箱里有什么。
Yeah, let's do it. So, let's start with just chatting with our chief of staff and get a feel for how you can chat with Kora here. So, let's just see what's in my inbox.
是的,经典的产品经理工作。帮我梳理我的一天。为了这个直播,这里将是一个演示环境。所以我们让 Grok Bot 里的同事稍微幻觉一下,创建一些虚构数据,但这些将模拟我们真实的工作流程和我们……
Yeah, classic PM, classic product person work. Help me triage my day. And for the purposes of this live stream, this will be a demo environment here. And so we are asking our colleagues here in Grok Bot to hallucinate a little bit and create some fictitious data, but these are going to be simulating our real workflows and the ways in which we...
这是你们每天实际使用的团队,对吧?
This is your actual team that you're using every day, right?
没错。
That's right.
好的,我们可以看到收件箱动态。有一些来自 Parker 关于语音的问题,还有几个关于市场的问题。然后我们看看,我今天早上一直在关注什么?这就是我们可以开始整理注意力列表的地方。所以,这会遍历 Slack 和 Gmail,以及我今天早上在 Notion 里做的所有更新,弄清楚我的注意力在哪里,我一直在花时间做的首要事情是什么。所以,看起来我一直在花时间在本地到云端的交接上。
Okay, so we can see our inbox pulse. We have some questions coming in from Parker on voice, a few questions on the marketplace. And then let's see, what have I been focused on this morning? And this is where we can start to curate our attention lists here. And so, this is going to go through Slack and Gmail and all of the different updates that I've made in Notion this morning and figure out where is my attention, what are the top things that I have been spending time on. So, yeah, looks like I've been spending time on local to cloud handoff.
市场信任、合作伙伴发布工具包,还有一堆我今早已经完成的其他事情,真是不可思议。
Marketplace trust, a partner launch kit, and a bunch of other things that I've already done this morning, which is incredible.
高效的早晨。现在才 9 点、10 点吧?如果你还没看过,Kevin 在 X 上有一篇很棒的帖子,详细介绍了这个注意力列表如何运作。我觉得非常棒。它不是待办事项列表,而是让机器人影子般地跟随你。我认为你能从中获得很多有趣的洞察,然后可以引导这些智能体帮助你解决你正在处理的最重要的事情。所以这就是注意力列表的实际应用。
Productive morning. And it's what, 9, 10 am? If you haven't read it, Kevin has a really great post on X detailing how this attention list works. I think it's really fantastic. Rather than a to-do list, it's to have the bot shadow you. And I think you get a lot of really interesting insights from that, and then can steer these agents towards helping you get unblocked in the things you're working on most. So that's the attention list in action right there.
是的,非常酷。我们看到 Kora 对我们要求的事情一直是被动响应,但很容易让 Kora 变得主动。所以我们可以说每小时整理我的收件箱,清除任何我不需要关注的内容。那么底层会发生的是,Kora 实际上会设置一个我们称之为例程的东西。
Yeah, very cool. And so what we've seen is Kora has been reactive to the things that we have asked, but it is very easy to turn Kora proactive. And so we can say every hour triage my inbox and clear out anything I don't need to pay attention to. And so what's going to happen under the hood here is Kora is actually going to set up what we call a routine.
你想谈谈例程吗?
You want to talk about routines?
是的。例程是一种自动化智能体任务的方式。你可以把它们想象成定时任务或重复任务,但它们是原生智能体式的,与 Grok 机器人一起。所以你可以要求智能体创建这些。有时如果智能体看到你反复做这些任务,它会建议或自动创建一个例程。你可以从界面查看和管理例程,并能够点击进入。所以也许我们也可以展示一下。是的,就是这样。如果你点击,我想是那里的右箭头。哦不,那会隐藏它们。好吧,你有例程。所以你可以查看例程。它们是自动化任务。这些例程的伟大之处在于,它们还保持与你连接的所有工具的连通性。所以我们会展示一个例子。哦,来了。是的,我们稍后会展示一个例子。但对于我们的分析用例,我喜欢的一件事是让我的分析机器人保持我们发布的新功能的每小时数据或每小时跟踪。这样你可以在需要时按需获得指标仪表板,而不必去网上的某个仪表板。所以就是这样。
Yeah. So routines are ways that you can automate agent tasks. I think you can sort of think of them as just scheduled tasks or repeated tasks, but they're natively agentic with Grok Bots. And so yeah, you can ask agents to create these. Sometimes if an agent sees you do these tasks over and over again, it'll suggest or automatically create a routine. You can view and manage the routines from the UI and be able to click into them. And so maybe we could show that too. Yeah, there you go. If you click I think it's the right arrow there. Oh no, that hides them. Okay. Well, you got routines. And so yeah, you can look at routines. They're automated tasks. And what's great about those routines, they also maintain connectivity to all the tools that you connect. So we'll show an example. Oh, there we go. Yeah, we'll show an example of this a little bit later on. But for our analytics use cases, one of the things that I love is asking my analytics bot to keep hourly data or hourly tracking for new features that we launch. That way you can get a metrics dashboard whenever you need on demand instead of having to go to a dashboard somewhere on the web. So there you go.
非常酷。
Very cool.
那么,在 Kora 设置这个的同时,我想我们将与我们的 Grok Bot 同事一起现场构建一个功能。那么,首先,我问了人们在 Reddit 和 X 上一直要求的一些顶级功能是什么?所以我认为我们有一个相当不错的研究列表。一位产品经理出去在社交媒体上做了一堆研究。还看了我们内部的 Slack 讨论、我们的反馈渠道。我们还有一个惊人的用户研究数据库,包含我们的用户研究团队正在对用户和客户进行的所有访谈。所以有很多反馈进入我们的产品团队。
And so while Kora sets that up, we are going to I think build a feature together live with our Grok Bot colleagues. And so to kick things off, I had asked what are some of the top features that people have been asking for on Reddit and X? And so I think we have a pretty good list of research. A PM went out did a bunch of research across social. Also looked at our internal Slack discussions, our feedback channels. We also have an amazing user research database of all of the interviews that our user research team is out doing with users and customers. And so there is a lot of feedback coming into our product team.
是的。而综合这些信息我认为本身就是一项工作。有时我在用户研究阶段发现机器人最有用的地方是能够从所有数据中生成洞察,但也只是关注和把握新动态。所以通常当新的用户研究访谈进来时,或者每天早上有最新的 Slack 更新时,我不得不进去重新提示、重新提示、重新提示。但有了我们刚刚展示的那些例程,或者像这样的快速提示,你可以一次性获得所有信息。所以,我觉得这很棒。这里有什么酷想法吗?你看到了吗?
Yeah. And synthesizing that I think is just its own job. Sometimes one of the things that I found most useful about bot on that UXR phase is being able to generate insights from all the data, but also just like keep an eye and a pulse on what's new. And so normally I'd have to go in and reprompt or reprompt or reprompt when a new user research interview comes in or every morning with latest Slack updates. But with those routines we just showed or with a quick prompt like this, you can kind of get it all at once. So, I think it's awesome. Any cool ideas in here? You see?
我很喜欢双向语音,但既然大家都在这里,也许你可以提出你对 Grok Bot 的顶级功能请求,任何使用过产品的人都可以。把它们放到聊天中。我们会将它们添加到我们的用户研究数据库。
I'm loving two-way voice, but while we have you all here, maybe you can throw in your top Grok Bot feature request for anybody who has been using the product. Drop them into chat. We will add them to our user research database.
将 Grok Bot 连接到特斯拉账户切换器。切换模型的能力。同步草稿消息。好的。
Connect Grok Bot to Tesla account switcher. Ability to switch models. Sync of draft messages. Okay.
好的。语音置顶和笔记线程。好的。双向语音。我看到很多对双向语音的投票。
Okay. Voice pin to top and note thread. Okay. Two-way voice. I'm seeing a lot of votes for two-way voice.
让我们试试。
Let's try it.
好的。那么,我们为什么不先做一些研究。让我们不要直接投入构建,尽管那会非常令人兴奋。所以为什么不看看语音到语音的基准测试,找出谁是语音到语音的顶级模型提供商。所以我们想要弄清楚我们想要如何实际实现那个模型。让我们去弄清楚谁在这里是顶级的。在我们做这个的同时,也许我们可以和 Ashley 一起问一些数据问题。
Okay. So, why don't we do a little bit of research up front. Let's not just dive into building although that would be very exciting. So why don't we ask look at the speech-to-speech benchmarks and find out who are the top model providers for speech to speech. So we want to be able to figure out which model how we want to actually implement that. Let's go figure out who is top here. And while we do that, maybe we could work with Ashley and ask a few data questions.
是的,听起来不错。那么,我想让我们切换到这里。所以,是的,我认为我们可能想要考虑的是,在思考一个新功能时我们可能想要作为输入的东西,也许我们可以从理解产品的市场规模和机会开始。所以我们可以开始问:帮我理解语音产品的市场规模和机会。我对 TAM 感兴趣。是的,我们就从那个开始。我非常喜欢拥有一个专门构建的分析师或数据聚焦机器人的一点是,随着时间的推移,它会非常了解你喜欢的数据方式。我们实际上有一些自定义技能,帮助我们以非常好的方式格式化数据,并使其符合我们的品牌。所以,当我们去为会议制作某张幻灯片或能够与同事分享数据时,它看起来和感觉起来就像大家习惯的那样。我也认为每个组织和每个团队处理数据的方式都不同,对吧?你有不同的 KPI、不同的指标,也许你以不同的方式年化收入。所以,拥有一个可以成为所有这些的首选机器人,我认为非常棒,并允许你建立一些这样的模式。所以,看起来 Ashley 正在努力工作。
Yeah, sounds good. So, I guess let's switch over here. So, yeah, I think the things that we might want to be thinking of the things that we might want as input when thinking about a new feature and maybe some things we could start with is understanding the market size of the product and kind of the opportunity. So we could start by asking help me understand the market size and opportunity for voice products. I'm interested in TAM. Yeah, let's just start with that. And one of the things that I really love about having a purpose-built analyst or data focused bot is that over time it just gets really smart about how you like your data. We actually have some custom skills here that help us format data in a really nice way, and make it kind of match our brand. So, when we're going into, you know, putting one particular slides for a meeting or kind of be able to share data with your colleagues, it kind of looks and feels like what everyone's used to. I also think every organization and every team does data differently, right? You have different KPIs, different metrics, different maybe you're annualizing your revenue in a different way. And so, having a bot that can sort of be that go-to for all that, I think, is really great and allows you to kind of establish some of those patterns. So, it looks like Ashley is grinding away here.
是的。是的。是的。为我们运行一些查询。我喜欢 Grok Bot 的另一件事是它可以多任务。这些智能体可以多任务。所以,你可以并行问多个问题。那么,当 Ashley 去为我们做这项研究时,我们也可以问其他事情,比如我们的产品中已经有一堆语音功能。所以向我们展示有多少百分比用户在我们的产品中使用任何语音模式。在我们输入那个的时候,Ashley 回来了一些洞察。
Yeah. Yeah. Yeah. Running some queries for us. The other thing that I love about Grok Bot is it can multitask. These agents can multitask. And so, you can ask multiple questions in parallel. And so while Ashley goes off and does this research for us, we can also ask additional things like we have a bunch of voice capabilities already across our products. So show us what percent of users use any voice mode across our products. And while we were typing that, Ashley came back with some insights.
是的,看起来我们面前可能有一个 480 亿美元的市场。听起来相当不错。是的,125 亿美元的可服务市场,看起来 Ashley 在这里,因为随着时间的推移,我们已经教会了 Ashley 如何制作我们喜欢的图表,已经为我们整理了一些图表。
Yeah, looks like we have maybe a 48 billion market ahead of us. That sounds pretty nice. And yeah, 12.5 billion SAM and it looks like Ashley here because over time we've taught Ashley how to make charts that we like has put together some charts for us.
这里有一些关于市场规模的分析,看起来语音 API 和基础设施与 Devi 和编码智能体非常接近。所以这对我们来说是个好机会。显然,我认为那里有一些非常好的东西。是的,看起来我们也有一些关键数据。所以,看起来是一个值得的机会。
So some analysis here on the market size, and it looks like we're seeing voice API and infra is pretty close to Devi and coding agents. So nice opportunity for us. And obviously, yeah, I think there's some really good stuff there. Yeah, it looks like we have some key data too. So all right, seems like a worthwhile opportunity.
非常酷。一个非常有用的专业提示是总是要求智能体提供引用。这样你就可以检查,也许你想对智能体使用的底层数据集提供一些额外的编辑或后续问题。所以哦看那个。好的。所以我们得到了语音 TAM。好的。这是语音 TAM 的可视化。然后我们得到了我们不同产品中语音周活跃用户的百分比。
Very cool. And one very useful pro tip is to always ask the agent to bring its citations. And so that way you can inspect and maybe there's some additional editing or follow-up questions that you want to provide on the underlying data set that agent had used. And so oh look at that. Okay. So we got voice TAM. Okay. So this is a visualization for that voice TAM here. And then we get the percentage of voice weekly active users across our different products.
我认为这种数据有时很难自己获取,当你只是一个独立的产品经理或独立的产品人员时。你经常要联系数据团队。你要确保能以正确的方式查询正确的数据库。所以我一直使用这类东西。这是一个非常好的方式来说,好的,酷。看起来我们可能在产品表面的语音功能中看到了语音产品的良好渗透。也许对我们来说,加倍投入一个功能是有意义的。
And this is the kind of data that I think can be really hard to obtain sometimes by yourself when you're just a solo PM or a solo product person. You're often reaching out to a data team. You're making sure you can query the right databases in the right ways. And so I use this kind of stuff all the time. And it's a really great way to say, okay, cool. It looks like we maybe see good penetration of voice products across our voice features across our product surface. Maybe makes sense for us to double down there with a feature.
是的,非常好。我们还要指出,目前 SpaceX AAI 内部的 Grok Bot 建立在一个很好的基础上。这个例子中体现的一件事是,你真的需要一个干净的数据集和一个好的数据湖来连接 Grok Bot。所以我们的数据工程团队做了很多艰苦的工作,他们使用 Grok Bot 来构建许多这些数据集,并整理大量好的数据,在此基础上 Ashley 可以查询并提供可信的见解。所以表面之下有很多事情在发生,以确保你有正确的基础,让智能体为你的产品团队取得最大成功。
Yeah, very good. We'll also call out that Grok Bot right now internally in SpaceX AAI is sitting on a great foundation. And so one of the things which comes through in this example is you really need a good clean data set and a good data lake to connect Grok Bot to. And so there's been a lot of hard work on our data engineering team who are using Grok Bot to build a lot of these data sets and curate a lot of this good data on top of which Ashley can query and provide trusted insight. So there's a lot happening underneath the surface to make sure that you have the right foundations for agents to be most successful for your product team.
完全正确,比如拥有规范的数据表,确保有一些技能可供智能体使用,让它们知道如何避免常见的查询错误,以及所有那些你可以明显编码到这些智能体中的东西。但看起来 PM Pete 带回了一些数据。
Totally, like having canonical data tables, making sure that there are some skills made available to the agents to know how to avoid common querying mistakes and all that stuff that you can sort of obviously encode into these agents. But it looks like PM Pete's come back with some data.
是的,让我们回去。我们刚才在问谁在语音到语音的排行榜上名列前茅。看起来 Grok Voice ThinkFast 2.0 在 Frontier 原生音频中排名第一。所以也许我们应该使用那个模型。听起来不错。好的。
Yeah, let's pop back. We were asking who's top of the leaderboard for speech to speech. It looks like Grok Voice ThinkFast 2.0 is top of the Frontier native audio. So maybe we should use that model. Sounds good. Okay.
我认为 Frontier 模型很棒。所以,是的,我们应该使用它们。
I think Frontier models are great. So, yeah, we should use them.
PM Pete 还配备了技能和我们的产品需求文档模板。所以,我们每周有产品评审,我们可以带来任何开放话题或任何我们作为产品团队想讨论的新想法。那么,我们应该和 PM Pete 一起写一个吗?
PM Pete is also equipped with a skill and a template for our product requirement docs. And so, we have a weekly product review that we can bring any open topic or any new idea that we want to discuss as a product team. So, should we work with PM Pete to write one of these?
是的,让我们做吧。我们应该请 PM Pete 帮助我们。
Yeah, let's do it. We should ask PM Pete to help us.
让我们为 Grok Bot 的语音模式写一个 PRD,我想他已经连接到 Notion 了,对吧?所以这会被放入我们的 Notion。
Let's write a PRD for voice mode in Grok Bot, and I think he's already connected to Notion, right? So this will get put into our Notion.
没错。
That's right.
好的,太棒了,太棒了。是的,所以这里的 PM Pete 有如何写出优秀 PRD 的上下文。所以 PM Pete 知道,一个伟大的 PRD 不仅仅是一堆文档上的需求;它是来自用户研究的见解,我们刚刚一起看过。它可能是来自行业和景观的见解,也许 Ashley 刚刚帮助我们整理出来的。显然还要考虑原型,我们越来越多地发现自己在流程早期就大量制作产品原型,以了解某样东西在产品中可能的外观和感觉。所以我们会看看 Pete 想出什么。与此同时,我们还有什么应该展示的吗?
Okay, awesome, awesome. Yeah, so PM Pete here has context on how to write really great PRDs. And so PM Pete knows that a great PRD is not just a bunch of requirements on a doc; it's insight from user research, which we just looked at together. It's maybe insight from the industry and landscape that maybe Ashley just helped us put together. And obviously thinking about prototypes, and increasingly we find ourselves prototyping product a lot early in the process for how something could look and feel in the product. So we'll see what Pete comes up with. Is there something else we should show in the meantime here?
为什么不让 Pixel 开始做一些设计呢?那会有帮助吗?
Why don't we have Pixel start cooking on some design? Would that be helpful?
好主意。是的,实际上我可能就让 Pete 去做。所以,Grok Bot 的一个很酷的地方是,你能也让 Pixel 来帮忙设计吗?所以是的,你可以直接给这些人发消息。他们会在后台继续工作,可以处理多任务,但你也可以标记其他机器人。我觉得这真的很有趣。所以,这里的 Pete,哦,好了,将让 Pixel 参与语音模式设计,并且仍在起草 PRD。所以,Pixel,正如我们之前谈到的,是我们的设计师,接受了设计系统和伟大设计如何运作、如何思考迭代设计和设计思维的训练。显然,很多知识来自一群了不起的人类设计师,帮助它变得真正出色。但在我们的案例中,我们真的可以在一些流程上取得先机。你会看到 Pete 正在做,你可以稍微窥探他们的对话。所以,看起来有一些共享的上下文,一些种子字符串,一个视觉简报,一些产品评审,以及一个看起来是空的模拟部分,希望会被填充。所以,好的,我们可以关闭这里的只读聊天。看起来 Pixel 已经听取了简报。
That's a great idea. Yeah, actually I might just ask Pete to do that. So, one of the cool things about Grok Bot, can you also loop in Pixel to help with design? So yeah, you can just message these folks. They'll keep working in the background and can handle the multitasking, but you can also tag other bots. And I find this to be really fun. And so, Pete here, oh, there we go, is going to loop in Pixel on voice mode design, and is still drafting the PRD. So, Pixel, as we talked about earlier, is our designer who's been trained on design systems and how great design works, how to think about iterative design, and design thinking. Obviously, a lot of that knowledge has come from an amazing set of human designers to help make it really great. But in our case, we can really get a head start on some of this process. And you'll see here's Pete's doing and you can spy on their conversation a bit. So, looks like there's some context that's shared, some seed strings, a visual brief, some product review, and a mock section that looks like it's empty that will hopefully get filled out. So, all right, we can close our readonly chat here. Looks like Pixel's briefed.
太棒了。是的,我认为任何花大量时间思考如何最好地提示智能体的人,学到的一件事是智能体实际上非常擅长提示其他智能体并与其他智能体合作。所以,我们刚刚把这两个放入一个群聊,PM Pete 能够实际上与 Pixel 直接分享所有这些上下文和 PM Pete 学到的一些东西,而不需要我们复制粘贴或移动上下文。智能体可以在幕后分享这些。
Amazing. Yeah, I think anybody who spent a lot of time thinking about how best to prompt agents, one of the things you learn is agents are actually very good at prompting other agents and working with other agents. And so, we have just put these two into a group chat and PM Pete is able to actually share all of this context and some of the things that PM Pete has learned directly with Pixel without us having to copy and paste or move context around. Agents can just share that behind the scenes.
我认为这里的一个很酷的事情也是他们在分享,但每个智能体仍然有自己的记忆、自己的上下文、自己的例程。所以,你知道,如果我们真的随着时间的推移与 Pixel 合作,教它特定的行为,比如说,总是使用暗模式,Pixel 会记住这一点,即使在这种情况下是 Pete 给 Pixel 发消息。所以,我认为这也减轻了很多心理负担。你可以一次性强制执行你的偏好,然后让这些偏好在未来所有工作中得到反映。我认为这真的让初始设置变得值得。
I think one of the cool things here, too, is they're sharing, but also each agent still has its own memories, its own context, its own routines. And so, you know, if we've really worked with Pixel over time to teach its specific behaviors, let's say, you know, always use dark mode, Pixel's going to remember that even if Pete is the one messaging Pixel in this case. And so, I think that also just takes a lot of the mental load off. You can kind of enforce your preferences once and then have those preferences be reflected on all the future work you do. And it sort of really makes that initial setup worth it, I think.
是的。嗯。
Yeah. Mhm.
有没有你喜歡在你的分析师中设置的特定例程?
And are there specific routines that you like to set up across your analyst?
是的。所以,我非常喜欢的一个,而且在我们烹饪那个文档的同时,我真的很喜欢对新功能进行定期的产品监控。所以,你知道,当我们在 Grok Bot 中推出新功能时,能够看到它们的进展对产品团队非常有帮助,这样我们既可以关注使用情况,也可以知道我们应该在哪里加倍投资。
Yeah. So, one of the ones that I really like, and while we're cooking on that doc, is I really love having regular product monitoring for new features. And so, you know, as we're launching new features into Grok Bot, being able to see how they're going is really helpful to the product team so we can both just keep an eye on usage but also just know where we should double down our investment.
我经常做的一件事,我们可以请 Ashley 在这里帮忙,就是我们最近在 Grok Bot 中推出了对 XMCP 的支持。实际上我们是在周六做的。你能给我发一个每小时一次的安装情况脉搏吗?首先,给我过去几天的使用情况。
And so, one thing that I'll do very often that we can ask Ashley to help out with here is, we recently launched support for the XMCP in Grok Bot. We did that on Saturday, actually. Can you send me an hourly pulse of how installs look? And to start, give me the last few days of usage.
所以这就是我在这里设置一个例行程序。对于新产品发布,我经常这样做。所以每天早上我醒来,也许对于每小时的,我会每小时看到它们,但也会做一个早晨简报,看看我所有的产品表现如何,比如哪里看到更多使用量,如果我看到指标下降。这真正棒的地方在于,我也可以在聊天中立即检查和分析了发生了什么。
And so this is me setting up a routine here. I'll do this very often for new product launches. And so every morning I'll wake up and have maybe well for the hourly ones I'll see them every hour, but also do like a morning brief and kind of see how are all my products doing where like where where am I seeing more usage if I see a metrics dip. What's really great about this is I can also just instantly sort of in the chat be able to inspect and analyze what what happened.
像这样的分析用例真正棒的地方在于,它连接到数据湖,正如 Kevin 提到的,底层是数据仓库。我们还可以查看产品套件其他部分的产品指标,试图解释发生了什么。所以,是的,看起来我们创建了一个例行程序。那就是我们的每小时脉搏。看起来有一些安装发生。还有我们的,是的,我们的每小时。
What's really great about analytics use cases like this is because it's tied to the data lakeink as Kevin mentioned the data warehouse under the hood. We can also look at product metrics from other parts of our product suite to try and explain what's going on. And so, yeah, it looks like we have a routine that's created. That's our hourly pulse. Looks like some installs happening. And there's our Yeah, there's our every hour.
非常酷。
Very cool.
非常酷。是的。所以,是的,我认为这是一个非常好的方式,让分析成为你日常中更被动的一部分。在类似这样的东西之前,我会发现自己总是打开仪表板,刷新它,把它固定住,放在某个墙上,而现在我只是用我的机器人。所以非常酷。
Very cool. Yeah. So, yeah, and this is this can be just a really great way, I think, to get analytics to be more of a passive part of your day-to-day. I before something like this, I'd find myself just like opening a dashboard all the time, refreshing it, keeping it pinned, having it on a wall somewhere, and now I just use my bots. So very cool.
当我们设置那个例行程序时,PMP Pete 带着我们的产品评审文档回来了。所以我们有了 Grok Bot 语音模式的草稿。让我们看看这个。
And while we were setting up that routine, PMP Pete has returned with our product review doc. And so we have a draft of our Grok Bot voice mode. Let's take a look at this.
所以这里是机会。你甚至可以从 Ashley 那里引入那些 TAM 见解。这里有一些从社交媒体和请求中提取的客户痛点。没有访问聊天的权限。
So here is the opportunity. You could even pull in those TAM insights from Ashley. Here are some of the customer pain points pulled from social media and the requests. Didn't have access to the chat.
是的,没关系。
Yeah, that's all right.
这里,但没关系。这里是提议的解决方案。所以在 Grok Bot 上的实时 Grok 模式语音模式,非常酷。
Here, but that's okay. And here is the proposed solution here. So live Grok mode voice mode on Grok Bot, which is very cool.
我喜欢这个。是的。
I like this. Yeah.
嗯,好的,看起来还有一个占位符,让 Pixel 插入一些模型,但它知道 Pixel 需要做这件事,这真的很不错。所以,我们总是可以请 RPM 确保完成。嗯,我也真的很喜欢这个。所以,有点像这里有一个文档,这里有一个 TL;DR。所以我可以稍微完善一下 TL;DR。哦,哇。好了。我们的模型来了。我刚才说,我刚才说那个。是的。
Um okay, looks like there is still a placeholder for Pixel to pop in some mocks, but it it knows that Pixel needs to do it, which is really nice. So, we could always ask RPM to make sure that that gets completed. Um, and I really like this, too. So, sort of like here's a doc and here's a TLDDR. So, I can refine the TLDDR a little bit. Oh, wow. There we go. There are our mocks. Just I was just saying I was just saying that. Yeah.
所以,Pixel 刚刚把模型交回给 PMP Pete。让我们看看他们做得怎么样。
So, Pixel has just handed the mocks back to PMP Pete. Let's see how they did.
太棒了。看看这个故事板。
Amazing. Look at this story board.
哦,是的。我喜欢这个。底部的小机器人。
Oh, yeah. I like this. The little little bot in the bottom.
好的。哇。选择了 huddle 导演。非常有趣。
Okay. Whoa. Went with the huddle director. Very interesting.
是的。是的,我的意思是,我在 Slack 中经常这样做,对吧?我们互相 huddle。所以
Yeah. Yeah, I mean I do that a lot in Slack, right? We we we huddle each other. So
听着小小的来回。
listening little back and forth.
好的,看看这里的小菜单。
Okay, look little menu here.
菜单很清晰。我认为
Menu crisp. I think
哦,甚至去了移动端。甚至去了移动端。
Oh, even went to mobile. Even went to mobile.
从操作按钮开始。好的。是的,我的意思是,这是一个非常好的起点,对吧?可能需要一点润色和一致性,但绝对足以制作一个伟大的原型。我们应该尝试构建它吗?
Started from action button. Okay. Yeah, I mean this was like a really good starting point, right? Probably could use a little bit of polish and consistency, but definitely enough to make a great prototype. Should we try to build it?
当然,让我们做吧。
Sure, let's do it.
呃,所以 Emily 是我们的工程经理,对吧?没错。好的。然后我们怎么想?我们应该让 Pete 请 Emily 构建它,还是直接找 Emily。
Uh, so Emily's our engineering manager, right? That's right. All right. And then what do we think? We should ask Pete to ask Emily to build it or just go straight to Emily.
让他们一起工作吧。
Let's just have them work together.
好的。所以,在 Grok Bot 中你可以做的一件事就是创建一个群聊。所以,我们会添加 PM Pete,还有我们的,Emily 在那里。嗯,我们就做我们的 PM 和 EM 组合,对吧?呃,然后说:“嘿,伙计们,嘿,各位。嗯,Pete 刚刚为语音模式整理了一个 PRD。你们能同步一下,让 Emily 开始构建这个吗?所以,是的,现在你可以看到我们在一个群聊中,有 Pete、Emily 和我们自己。这些群聊真正酷的地方在于,它们感觉就像同时和一群同事交谈。所以我们从这两个智能体那里获取联系人。显然之前我们看到智能体可以互相标记和提示。嗯,但我会经常使用这样的东西,只是为了能够在一个地方看到两个智能体的上下文,并更加亲力亲为,对吧?所以,有时我会,你知道,让我的幕僚长去,你知道,和其他几个智能体谈谈来完成一些事情。对于我认为像这样的构建案例,亲力亲为并让智能体互相交谈真的很好。所以,酷。非常酷。我们会让他们在这里一起工作。
Okay. So, one thing that you can do in Grok Bot is you can actually just create a group chat. So, we'll add PM Pete and where is our There's Emily. Um, we'll just do our PM and EM band up, right? Uh, and say, "Hey guys, hey folks. Um, Pete just put together a purity for voice mode. Can y'all sync up and Emily start building this? And so yeah, this is now you can see that we're in a we're in a group chat with Pete, Emily, and ourselves here. And uh what's really cool about these group chats is that they feel just like talking to a bunch of colleagues at once. And so we're getting the contacts from both of these agents. Obviously earlier we saw agents can sort of tag each other and and prompt each other. Um, but we'll I'll often use something like this as a way to just be able to see the context for both agents in one place and be a little more hands-on, right? So, sometimes I'll, you know, ask my chief of staff to uh, you know, talk to a few other agents to get something done. For, I think, build cases like this, it's really nice to be hands-on and get the get the agents to be talking to each other. So, cool. Very cool. And we will let them work together down here.
呃,Emily 下一步要做的是实际分配这项工作。所以,我们会把产品需求文档或 RFC 翻译成离散的技术任务,然后她将把这些任务交给她团队的工程师,每个人都会得到一个工单。让我们看看。哦,是的,看起来他们在聊天。检查他们。Pete 在确认事实来源。然后 Pete,他整理了我们的需求,有了 V1。任何好的产品都从 V1、MVP、原型开始。所以看起来 Pete 已经搞定了。他们正在考虑。是的。你的东西超出范围,我喜欢这个。总是很高兴看到这个。酷。他们应该正在烹饪。非常好。
And uh what Emily is going to do as a next step uh is actually distribute this work. So uh we'll take the uh product requirements doc or RFC translate that into uh discrete technical tasks which then she will hand off to her team of engineers who will each get a ticket. Let's see. Oh yeah, looks like they're chatting. Checking on them. There's Pete confirming the source of truth. And then Pete, who's put together our requirements, has the V1. Any good product starts with a V1, an MVP, a prototype. And so looks like Pete's got that figured out. And they're thinking about it. Yeah. Your stuff that's out of scope, which I love. Always always great to see that. Cool. And they should be cooking. Very good.
Grok Bot 的惊人之处之一是它能够实际启动云智能体来执行编码任务。所以,你可以把 Grok Bot 看作能够接入特定的编码工具和一组针对编码任务真正优化的智能体云环境。这样你就可以有这种很棒的交接和这些云智能体的管理者继续推进。
And one of the amazing things uh of Grok Bot is it is able to actually spin off cloud agents to do coding tasks. And so uh you can think of Grok Bot as being able to hook into a specific coding harness uh and a set of agent cloud agent environments which is really optimized for coding tasks. And so you can have this great handoff and these managers of cloud agents going forward.
是的,我认为这可以追溯到我们之前讨论的内部看到的情况,即我们许多真正优秀的工程师发现自己一天中管理着多个甚至几十或几百个智能体线程,嗯,并且创造了自己版本的管理器、协调器或管理者智能体。呃,所以启发 Grok Bot 这个特定功能的想法之一就是让那种感觉真正原生。
Yeah, I think this goes back to what we were talking about earlier with what we saw internally, which is a lot of our really great engineers found themselves managing multiple sort of even dozens or hundreds of agent threads over the course of a day and um sort of were creating their own versions of orchestrator or coordinator or sort of manager agents. Uh and so one of the ideas that inspired this particular feature in Grok Bot was making that feel really native.
现在有很多争论和讨论,关于人们如今到底有多少是在看代码、多少是在看输出和结果。我觉得这其实可能是一种非常有意思的写代码方式,未来如此,甚至现在也是。基本上就是聚焦结果,让智能体彼此协调,然后赋予智能体能力,让它们能开出这些以编程为核心的环境,在里面完成大量工作。所以,看起来它们正在推进。
There's a bunch of debate and discourse around how much people are looking at code these days versus looking at outputs and outcomes. I think this actually feels like it could be a really interesting way to write code in the future, and even now. Basically, focusing on outcomes, asking agents to coordinate with each other, and then giving agents the ability to go and spin off these coding-focused environments where they can get a lot of things done. So yeah, looks like they're cracking on.
好,非常好。看起来 Emily 实际上给我派了一个任务,要我去解除某位工程师的阻塞。看起来我这边需要做一个审批。
Okay, very good. So it looks like Emily has actually given me a task to unblock one of the engineers. Looks like there is an approval that is required on my side.
我觉得这是一个很好的例子,说明这类交接——智能体确实在尽量替你主动做事,但它们有时会遇到访问权限问题,或者需要你帮忙登录你用的某个工具。我们希望给智能体配备和我们完全相同的工具集,这样它们才能最高效。所以我们经常收到这边团队的问题,让我去登录,或者问能不能访问某个特定工具,好让它们的工作更高效。
And I think this is a good example where these types of handoffs—agents are really trying to be as active as possible on your behalf, but they can sometimes run into access issues or need your help to log into a tool that you use. And we want to equip our agents with the exact same tool set that we have access to so they can be most productive. And so we'll often get questions from the team here asking me to log in or whether they can have access to a particular tool that would make their work even more productive.
是啊,我觉得正如我们之前聊到的,确保一切连通真的很有帮助。显然在写软件的过程中,取决于你在写什么功能,你可能需要用不同方式去验证它们。所以看起来我们的工程师正在埋头推进。
Yeah, I think it's really helpful, as we talked about earlier, to make sure everything's connected. Obviously over the course of writing software, depending on a feature you're writing, you might need to be able to validate those in different ways. And so looks like our engineers are cracking away here.
还有一点我之前没怎么提到,就是这一切都能在手机上完成,对吧?我们看到了 Grok Bot 在手机语音上的那个原型,但我经常在路上就这么做。如果我有一个功能的想法,以前我会打开笔记应用,然后等回到工位再把它敲进提示词,再写一份文档。但现在我在路上就能启动整个引擎。我可以对着 Grok Bot 用语音转文字的流程说话,也许很快就能用语音流程。但真正能在任何地方、任何设备上访问它,我觉得是一个巨大的突破。有时候灵感在会议结束时突然冒出来,你就想马上启动一个想法或一个原型,而一旦系统搭好了,你真的能非常非常快地从零到原型。所以非常酷。
One thing I'll also mention that we didn't talk about much earlier is you can do all of this on mobile, right? So we saw that mockup of Grok Bot on mobile voice, but I'll often do this on the go. If I have an idea for a feature, I used to pull up a notes app and then wait till I got back at my desk and then type that into a prompt and then write a doc. But I can kick off this entire engine when I'm just on the go. I can talk into Grok Bot with the speech-to-text flow and maybe soon a voice flow. But really being able to access this anywhere and on any device, I think has been a really huge unlock. Sometimes inspiration strikes at the end of a meeting and you just want to be able to kick off an idea or kick off a prototype, and once you have the system set up, you can really go from zero to prototype really, really quickly. So very cool.
所以看起来 Eileen 和 Emily——
So it looks like Eileen and Emily—
Eileen 是谁?
Who's Eileen?
Eileen 是我们的一位工程师。
Eileen's one of our engineers.
——还有 Larry,都在协调这项工作。看起来他们正在研究实现 pool hint 的最佳方式。所以这正是一个很好的例子,体现了真正的自主性,以及 Grok Bot 们如何协调工作、在这些更大的功能上协同合作。
—and Larry are all coordinating on this work. And so looks like they are looking into the best way of implementing pool hint. And so this is just a great example here of really the autonomy and ways in which Grok Bots can coordinate their work, work together on some of these larger features.
是啊。如果你想搭建类似的东西,我想你能看到,一堆不同的人或智能体被拉进了聊天。这是因为 Emily 和这些工程师的设置方式,让它们知道自己可以互相打标签。所以随着时间推移,Emily 在这个 EM 角色上不断成长,她学会了可以把某些事情派给子智能体或其他智能体,可以拉人进来帮忙分派工作,然后再审阅那些工作。也就是形成了一种“任务—审阅者”的范式。然后还能独立测试功能。所以在这个案例里,我们并没有让 Emily 去给这些其他机器人打标签,但那种——
Yeah. And if you want to set up something like this, I think you're seeing that a bunch of different people or agents are being pulled into the chat. And that's because the way that Emily is set up and these engineers are set up is that they know they can tag each other. And so over time, as Emily has grown in her role as the EM here, she's learned that she can task out certain things to sub-agents or other agents, that she can loop in folks to help delegate work and then be able to review that work. So sort of creating a task-and-reviewer paradigm. And then also be able to test features independently as well. So in this case, we didn't have to tell Emily to go and tag these other bots, but that sort of—