与「SLACK」相关的搜索结果

At @SpaceXSI, Lauren Tan (@poteto) and Roman Ugarte (@romanugarte_) are on the core team that took Grok Bot from first line of code to launch in seven weeks. It lets you spin up AI teammates with their own identities and logins, and they just keep working in the background. Their marketing team gave a bot its own ad budget. Lauren built an entire feature with her bot in one Slack thread without ever opening Cursor. They joined us on the @LightconePod to talk about what it’s actually like working next to bots every day, and how the hard part is shifting from doing the work to figuring out what to do and why. 03:36 — Giving Bots Real Jobs 06:49 — One Bot or a Team of Specialists 10:39 — Sharing Bots Across the Company 14:46 — Identity and Permissions for AI Coworkers 18:37 — Bot-to-Bot Collaboration and Trust 22:35 — The Workflow Behind 4,000 PRs a Month 26:00 — Teaching Agents to Write Code You Trust 29:01 — Building a Personal Software Factory 33:44 — The Future of AI Coworkers 36:47 — Rethinking the AI-Native Company 40:13 — Teaching Agents to Check Their Own Work 43:56 — How Much Code Review Is Enough? 47:33 — Codebase Guardrails That Save Tokens 52:20 — When Product Judgment Becomes the Bottleneck 56:29 — From Finance to AI Engineering

if you want to automerge thousands of pull requests , this is how she does it (via @poteto). 809 in june. 10,926 in october. merged prs a month that touch the grok bot team's code. i went through her posts and put the setup in one place. every pr still gets an agentic risk review plus bugbot. low- and medium-risk ones automerge. only higher-risk ones get a person. day to day, in her words, it's just grok bot and cursor projects. she used to have more cursor automations and replaced them with slack bots that have routines. she works on many streams in parallel with pstack: perf, bug fixes, agent-friendly refactors, her own skills, features, ui polish, the harness, release and observability. not from sitting in a review inbox. she's said the speed gains come from parallelizing. a single chat can take longer because of verification. she handholds it less, so she can run several large projects at once. the real setup is in the codebase and the checks around it. she treats the codebase as memory. every agent mistake needs to turn into a constraint. her team built their own framework for grok bot so some anti-patterns become hard to write at all. agents have to verify their own work. they run the app, and can sometimes model it in tla+. they produce screenshots or video that are easier to check than the whole pr. formal verification skills and ordinary run-and-debug skills work together. she calls this an inverse pyramid. push as much as you can into determinism (fuzzing, property tests, formal and runtime verification, stricter languages) instead of spinning up more agent swarms. in her oct 6 post, she tells sandcastle, a grok team bot, to cut. it runs a buildkite dry run, dms every pr author (they can object), kicks the build, and watches it. then it starts a fuzz swarm: usually 10+ agents on grok 4.7 xhigh, some directed, some chaos monkey, using their verification skills and feature map. when something is high priority, she tells sandcastle to @ mention poteto, her engineer bot, which then spins up a cursor project to triage and fix. her team ships a new stable version of the client at least once a day. that's a lot of machinery under "just grok bot and cursor projects."

一直在用 Grok Bot，都没注意到它已经 v1.0 了，而且是 10 天前，这有点灯下黑了 😄 看看作为 v1.0 的 Grok Bot 和 v0.x 时有啥不同？ 1. 多人协作：可以把 Bot 分享给团队，带到 Slack、Microsoft Teams 和视频通话里；同一套 Team Bot 可由团队共用，也可只分享给特定的人或群组。Bot 能在多人对话中跟上讨论，并在工作中积累对团队知识和偏好的理解。 2. 主动接手：可以识别待办并提出由它来做，跟进未完成事项，预估团队下一步需要什么，并在需要判断时把相关的人拉进来。 3. 能力提升：浏览网页更稳定，写文档和做演示更快、更可靠，并减少完成任务所需资源。 其他改进还包括：登录和浏览网站时更少中断；可以制作能共同编辑、也可持续更新的交互式页面；与 Gmail、Google Calendar、GitHub 等工具的连接有所加强；已授权的动作少打断，敏感操作仍会询问。共享空间也有明确约束：遵守各人权限，并检查信息是否适合发到公开频道。 个人可以创建自己的 Bot，也可以分享给团队。Team Bot 面向 Team 和 Enterprise 套餐；会议功能面向 Team、Enterprise 和 Ultra，企业套餐需由管理员打开。官方文档补充，Bot 可加入 Google Meet、Zoom 或 Microsoft Teams，在会议中回答，结束后发送摘要和待办。

Introducing Grok Bot 1.0. AI teammates that work alongside your whole team. Share Bots, collaborate with them in Slack and Teams, invite them to meetings, and watch them learn and become more helpful.

We're still so small but I'm loving the team we've got at Superlogical. They're so talented and kind and love their craft. It's a different era of software development and our expectations and practices reflect that. I want to share a bit about how we work. First, everyone is trusted to push to main. We do machine-aided code review pre-push and human plus more machine-aided code review post-push. Limited to no PRs. Culturally, we've all agreed that if we ever hire someone who we DON'T trust to push directly to main, then they probably aren't the right fit for the team (so far, not an issue). Some common sense here: if someone is stepping outside their lane or comfort zone, we'll open PRs. For example, I'm pretty trash at macOS/iOS UI, so I'll open PRs for UI-affecting functionality and ask for eyeballs/help. But for business logic and internals, I push to main. Second, everyone can cut a release. Our release process is fully automated and when you start a release (for any platform) it triggers a Slack notification and a 15 minute countdown. The 15 minute warning is a final gate that allows people to review plus collaborate on a changelog. During that 15 minutes, anyone in the company can pause the release rollout. After 15 minutes, the train leaves the station. You can't override the 15 minutes (except to pause). It gives everyone a chance to step in. Third, we avoid synchronization through fast remediation rather than through planning. The server and clients on various platforms ship features as fast as they can. We use post-hoc human review and AI-assistance to identify feature mismatches across products ("Windows has support for X and Mac doesn't." or "Mac and Windows differ in their behaviors for Y in this way."). This avoids expensive "sync" meetings and coordination. We trust that producers of features are mindful of what they're producing and we trust that adjacent product lines will self-synchronize quickly. In practice, we see feature parity across platforms within 24 to 48 hours. All of this works on mutual trust. It ONLY works with mutual trust. Everyone at all times has to trust that they've got each others back: 1. Push to main only works if you fix your mess, or if you don't, that someone else will quickly but that you'd do the same (and generally in equal amounts). 2. Anyone can deploy only works if you trust everyone to cut at the right time, with the right changelog, and that people will respect the 15 minute timer. 3. Sync through fast remediation only works if you trust other teams will pick up and integrate your work quickly, which only works if you would too. It also only works if you are fairly producing mismatches (e.g. not constantly). We've got a great team. I know we're still small and that these practices will change in many ways as we scale. But this is already a markedly different practice than what I would've done 15 years ago. In general, we are building from day 1 on a foundation of mutual respect, excellence, and trust. And it's been awesome.

卧槽！！Grok Bot 工程师刚发布了一份11页的PDF，教你如何把周额度从 100% 降到 20%，核心就十步： 1. 用量是一道乘法：唤醒次数 × 上下文 × 步骤 × 扇出。四头各减一点，比只减一头管用。 2. 只有一个共用池。Grok 聊天、Grok Bot、Cursor 都吃同一周额度百分比。没有按 Bot 拆分，到 100% 前也没预警。 3. 唤醒先烧。每 15 分钟跑一次的例行任务，一周 672 次，哪怕啥都没变。测试运行也算。 4. 用触发器换掉死定时。Slack @、邮件、GitHub 事件、webhook。同样的活，672 次能压到十几次。 5. 每次回复都会重读整段对话。一个 Bot 挂同一活干六周，每次都会把旧上下文背着跑。换新 Bot，附一份约 300 字交接说明。 6. 精简人设和记忆。它们会跟每一步一起跑，一周能跟几千次。 7. 每个任务写清终点和停止规则。连续失败两次就停下来问。重试死循环最费。 8. 能接应用就别靠点点点。打开、截图、滚动、点击能拖到七步；连上应用往往一次调用就够。 9. 一活一主。群聊里 4 个 Grok Bot，一问最多能出 4 条计费回复。Bot 之间来回最多 2 条。 10. 周中额度到约 80% 就切低耗：暂停例行任务，只交最终结果，到 100% 前先设花费上限。 同样的活，示例是 2000 units → 400。单砍唤醒就能砍掉半周；池子没变大，Bot 更持久了。 建议收藏，赶紧喂给你的Gork bot！

Personal Agent 趋势判断： 不论是 Muse、Dot 还是 Grok Bot ... 目前都是你和它沟通，它完成一些事情， 而我们日常生活和工作中，做具体的事只是一部分，很大一部分时间都在沟通上。 不论是当面沟通、发消息、打电话、视频会议... 等等。 不能替你去和别人沟通的 Agent 体系是不完整的。 能替你进行沟通，需要以下先决条件： 1. 懂你：Agent 知道你是怎样的人，怎样的沟通表达习惯 Memory & Soul 2. 懂对方：Agent 知道沟通对象、知道沟通上下文（Context）和下一步沟通目标（Target） 3. 懂沟通、能沟通：Agent 知道沟通技巧（Skill），知道准备最合适的材料（文档、图片、PPT、动画视频...），知道使用沟通工具（Zoom、Slack...），会听、看、说，需要多模态能听懂、看懂、说话（TTS、ASR...） 目前几乎技术都满足了，只需要一个合理机制把这些组合起来。 2027 年，会替你沟通的 Agent 成为主流，不会替你沟通的 Agent 会是边缘。

1/ 像是提前看到了2—3年后的世界。 下班后，他坐在车里对着手机说了几句话，Grok Bot便开始工作： 读取Notion里的待办事项、更新完成状态、把任务移到下周、发送日历邀请、归档邮件，还根据预设SOP自动回复Slack消息。 最后甚至通过X Money完成了转账。全程只靠语音。