A task typed on Home can land in another project's repository
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
Start at internal/tui3/home.go:3396 (homeStart) and homeStartWithProject at :3406, then trace /task dispatch and hosted engine selection. Reproduce through codeaf chat in tmux with two projects and an existing engine, then add the unit and e2e coverage described in the issue. Done means Home tasks and plain messages resolve the same project, commits stay in B, the conversation workspace names B, and the Home/task manual and invalidates are updated.
由索引模型根据 Issue 内容生成。
描述
Seen on dev@debffabf6.
What happened
On 2026-09-24, a /task typed directly on Home while Home showed project B opened a conversation attached to project A's still-running engine. The task commit landed in A; B was untouched. The same result occurred on #1410's merge-base. A plain message typed on Home stayed in B. One run also showed could not start the task · the engine did not answer in time despite the task having started elsewhere; that notice was observed once, not independently reproduced.
Replication
Deterministic (no model). None yet: both launches need a conversation with a live engine, which today means a model.
Field (real models). OPENROUTER_API_KEY, deepseek/deepseek-v4-flash, tmux; a few minutes and a few cents.
export CODEAF_HOME=$(mktemp -d) HOME=$(mktemp -d)
A=$(mktemp -d) && git -C "$A" init -q && git -C "$A" commit -q --allow-empty -m init
B=$(mktemp -d) && git -C "$B" init -q && git -C "$B" commit -q --allow-empty -m init
cd "$A" && codeaf chat, send any message, then close the window. A's engine stays up.cd "$B" && codeaf chat. Home's seam readsproject:with B's folder.- On Home, type
/task write h0.txt containing h0and press enter.
Today the conversation opens in A (its meta.json workspace is A) and the commit task: write h0.txt containing h0 lands in A; git -C "$B" log is unchanged. Control: a plain message typed on Home in step 3 opens in B.
Where
internal/tui3/home.go:3396 at dev@debffabf6, homeStart, begins Home submissions; homeStartWithProject at :3406 delegates to target opening. Search /task dispatch through that path and the hosted engine selection.
The fix
Bind the Home draft's project to the new conversation and its engine before dispatching /task. Refuse visibly if that binding cannot be established; never let an existing engine from another project answer it.
Acceptance
- e2e: through
codeaf chatin tmux, a Home/taskissued while A's engine lives creates and commits only in B; the conversation workspace field names B. - e2e: a plain Home message still opens in B.
- Unit: the Home task command and plain-message paths resolve the same target project.
- Update the Home/task manual and
invalidates.
- 主要语言
- Go
- 星标
- 115
- 派生
- 14
- 平均合并
- 9 小时 35 分钟
- 30 天内合并 PR
- 752
环境准备
我们还没有检查这个项目的环境配置文件。先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
Agent-Field/CodeAF 的其他 Issue
-
area:chat bug sev:papercut
难度 2/5 1-3 小时 新手友好度 86/100
Agent-Field/CodeAF#1592 ·
维护者通常 1 天内回复
-
area:headless bug sev:critical
难度 2/5 1-3 小时 新手友好度 88/100
Agent-Field/CodeAF#1566 ·
维护者通常 1 天内回复
-
area:chat bug sev:critical
难度 2/5 1-3 小时 新手友好度 82/100
Agent-Field/CodeAF#1548 · 1 条评论 ·
维护者通常 1 天内回复
-
area:chat feature
难度 2/5 1-3 小时 新手友好度 88/100
Agent-Field/CodeAF#1510 ·
维护者通常 1 天内回复
-
area:tests bug
难度 2/5 1-3 小时 新手友好度 82/100
Agent-Field/CodeAF#1489 ·
维护者通常 1 天内回复
查看 Agent-Field/CodeAF 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 78/100
-
难度 1/5 1 小时以内 新手友好度 65/100
521xueweihan/HelloGitHub#3789 ·
-
难度 2/5 1-3 小时 新手友好度 88/100
维护者通常 12 天内回复
-
stage-fail
难度 2/5 1-3 小时 新手友好度 78/100
siyuan-note/bazaar#2282 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
openshift/kube-compare#307 ·
维护者通常 1 天内回复