抄作业 / 做成了什么 / Grok Bot

做了什么

Feature request that Grok Bot voice-call turns and a three-part-summary land in the same chat transcript instead of a separate hang-up JSON rail.

场景

周报 / 简报

资料完整度

• ✓ 作者与原链接有
• ✓ 做了什么有
• ✓ 来源原文摘录有
• — 截图 / 媒体来源未提供
• — 步骤 / 章节来源未提供
• — 提示词 / 配置原文来源未提供
• — 结果 / 数字来源未提供
• ✓ 风险提示有
• ✓ 相关条目有

— 表示来源没有给出，本站不补写。

来源原文摘录

Feature request for product/service Chat Describe the request Problem Voice calls do not integrate with chat session turns. Spoken work stays on a separate rail (call JSON at hang-up; chat mostly gets a duration receipt). That is a big usability gap: the mode you use to talk is not the same record the bot and you rely on for context. Why Dictate is not the answer Composer Dictate (mic on the prompt field) still lands text in the chat, but it is keyboard-mode with a mic: start a draft, speak, stop, edit, send, then optionally jump into a call. Switching between Dictate and voice-call is clunky

展开全文

and not hands-off. A voice UX should prioritize staying on the call — compose, post into the chat session, hear the labeled reply — without touching the composer. Framing (intentional separation of concerns) …

摘自论坛首帖，照录原文，未翻译。

提示词

来源没有给出可直接复制的提示词原文。

怎么复制

1. 读原文：forum.cursor.com ↗
2. 把原文里的步骤/提示词整理成一条消息交给 Bot
3. 先手动跑一次，再决定频率

风险与限制

• 作者的结果不保证能复现，以原帖为准

用量预估

用金属计算器估一下