Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

Reply editor prefills the AI disclaimer instead of the draft answer

未关闭 适合新手
  • 哪里不对？
#145 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 3 天内回复

还没有人认领这个 Issue。

评估

难度
2/5
预计耗时
1-3 小时
新手友好度
78/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
冷清
技术栈
typescript
领域
ai, backend, frontend

调研方向

从 packages/outpost/queue/src/handlers/ai-response.ts 第158-172行附近开始，然后检查 apps/web/src/components/.../reply-editor.tsx，以确认 suggestedResponse 的使用方式。验证编辑器接收的是未格式化的 pipelineResult.response，为 suppressed case 添加覆盖，并确保在不更改已发布 response 的情况下满足验收条件。

由索引模型根据 Issue 内容生成。

描述

area: ai roadmap roadmap: now

The agent-facing reply editor prefills with the AI disclaimer instead of the draft answer.

Where

packages/outpost/queue/src/handlers/ai-response.ts:172

await prisma.ticket.update({
    where: { id: ticket.id },
    data: {
        suggestedResponse: pipelineResult.formatted.text,
    },
});

formatted.text is the published form of the reply: platform formatting, footer, and — for anything below HIGH confidence — a leading disclaimer block:

> ⚠️ This is an AI-generated response. We've escalated this to our engineering team — someone will follow up in this thread shortly.

apps/web/src/components/.../reply-editor.tsx:59 prefills the agent's reply box with that string verbatim. So a human picking up an escalation opens their editor and finds a draft that opens by declaring itself AI-generated and announcing an escalation — text that makes no sense coming from them, and that they have to delete before writing anything.

The raw draft is already persisted one call earlier as Message.content (ai-response.ts:158) and is available as pipelineResult.response. That's the right source for an editor.

Fix

-        suggestedResponse: pipelineResult.formatted.text,
+        suggestedResponse: pipelineResult.response,

Worth checking whether any other consumer depends on suggestedResponse carrying the formatted text before flipping it — as of #143's review, reply-editor.tsx is its only reader and it's human-driven, so nothing auto-posts it.

Why it's filed separately

Raised by @jerelvelarde in review of #143 and deliberately not fixed there: the line is pre-existing, isn't in that PR's diff, and #143 only makes it reachable more often.

It gets worse, though, with the always-answers work that's in progress (retrieval fan-out across all four MCP corpora + the no-answer reply). Under that change, a suppressed ungrounded draft has its formatted.text replaced with the no-answer copy:

I couldn't find an answer to this in the CopilotKit or AG-UI documentation or source code, so I don't want to guess. I've escalated this to our team — someone will follow up in this thread.

So the human's editor prefills with the apology, and the actual draft they were meant to work from lives only in Message.content, which the editor never reads. The stated justification for suppressing rather than discarding a draft — "a human can edit and send it" — stops being true.

Should land with, or before, that PR.

Acceptance

  • suggestedResponse holds the unformatted draft (pipelineResult.response), disclaimer-free
  • Reply editor prefills text an agent can send without deleting a preamble
  • A suppressed draft still reaches the editor as the draft, not as the no-answer copy
  • Test covering the suppressed case, since that's the path where the two diverge
主要语言
TypeScript
星标
8
派生
4
平均合并
3 天 19 小时
30 天内合并 PR
10

环境准备

  • 提供 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 没有贡献指南

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

CopilotKit/outpost 的其他 Issue

查看 CopilotKit/outpost 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。