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

A coworker created as Built in still cannot hand work on

未关闭
  • 哪里不对？
#399 3 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

  • #695 来自 @Harbor404 —— 已关闭，未合并

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
活跃
技术栈
typescript
领域
backend-api-design

调研方向

阅读 #317 中延期的设计以及 #331 中描述的行为，然后检查 plugins/store.ts，尤其是 agentRunsHere 和 managedConfiguration 路径。比较无 endpoint 的 built_in 存储选项与在 callback surface 上 mint 一个 hop endpoint，并记录对于已有 managed Bot 的部署以及已经存储为 remote_ag_ui 的同事所选择的行为。

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

描述

Tracking the design question #317 deferred on purpose, so it survives the PR that half-answers it.

From that PR's description:

A coworker created as "Built in" through the wizard is stored as remote_ag_ui pointed at the
managed endpoint. Its tool callbacks work (the deployment-token path), but the handoff tool is
minted only inside this deployment's own run loop, so such a coworker can be asked but cannot
itself hand work on. […] Fixing it properly means either storing endpoint-less creates as
built_in type, or adding a server-minted hop endpoint to the callback surface — worth its own PR
either way.

What #331 covers

#331 takes the first option, because the interview it adds cannot end by asking somebody for a URL.
store.create writes a built_in coworker running on its role description where there is neither
an endpoint nor a managed Bot — which on the one-container image the README recommends is every
coworker.

That buys back exactly what the note was about, in that case: agentRunsHere is
row.type === "built_in" (plugins/store.ts), and grantable on the handoff answer comes from it,
so a coworker created that way can be handed work on.

What is still open

Where the deployment does have a managed Bot, create still prefers managedConfiguration, the
row is still remote_ag_ui, and nothing changes: the coworker can be asked and cannot hand work on.
The wizard's "Built in" option is only offered on exactly those deployments, so the case #317
described is the case still outstanding.

Two ways out, both from the original note:

  1. Store endpoint-less creates as built_in even when a managed Bot exists. Smallest diff, and
    it makes "Built in" mean one thing everywhere rather than two things depending on configuration.
    The question is what happens to coworkers already stored the other way — they keep working, but
    the roster then holds both shapes with no way to tell them apart except the endpoint string.
  2. Mint a hop endpoint on the callback surface. Leaves storage alone and makes the handoff tool
    reachable from outside the run loop. Larger, and it puts a new server-minted address into a
    surface that currently only issues tokens.

Not proposing either — this is #317's question and the choice is its author's. Filing it so it does
not disappear when #331 merges and the no-managed-Bot half stops being visible.

主要语言
TypeScript
星标
6.6k
派生
914
平均合并
22 小时 56 分钟
30 天内合并 PR
141

环境准备

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

从这里开始

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

CopilotKit/OpenBot 的其他 Issue

查看 CopilotKit/OpenBot 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

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