抄作业 / 做成了什么 / Grok Bot
Grokbot and GitHub (Connected but Authorization header badly formatted)
标题与摘要为原文，未翻译。
- 做了什么
- Staff: GitHub connector shows Connected but fails with “Authorization header is badly formatted”—tracked bug; workaround is press-and-hold the account → Remove, then reconnect and sign in again.
- 资料完整度
- 作者与原链接有
- 做了什么有
- 来源原文摘录有
- 截图 / 媒体有
- 步骤 / 章节来源未提供
- 提示词 / 配置原文来源未提供
- 结果 / 数字来源未提供
- 风险提示有
- 相关条目有
— 表示来源没有给出，本站不补写。
- 来源原文摘录
Where does the bug appear (feature/product)? Something else — Grok Bot / Grok iOS app GitHub connector Describe the Bug The GitHub connector in the Grok iOS app fails to load even though my GitHub account is shown as Connected. The following error appears: Error — Failed to load connector “Couldn’t start sign-in: Streamable HTTP error: Error POSTing to endpoint: bad request: Authorization header is badly formatted” The account section still shows my default GitHub account as Connected. Pressing Retry does not resolve the problem. Steps to Reproduce • Open the Grok app on iPhone. • Open the
展开全文
GitHub connector. • Attempt to load/use the connected GitHub account. • The connector fails to initialize. • The error reports that the Authorization header is badly formatted. • Press Retry. • The same error persists. Expected Behavior …RongleCat/awesome-grok-bot (GitHub) · 打开原文 ↗ 摘自论坛首帖，照录原文，未翻译。
- 效果截图
截图来自原帖 - 提示词
来源没有给出可直接复制的提示词原文。
- 怎么复制
- 读原文：forum.cursor.com ↗
- 把原文里的步骤/提示词整理成一条消息交给 Bot
- 先手动跑一次，再决定频率
- 风险与限制
- 作者的结果不保证能复现，以原帖为准
- 用量预估
- 用金属计算器估一下