In-app coordinator/Ralph never reads .squad/ralph-instructions.md; only `squad watch --execute` does
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 2/5
- 预计耗时
- 1-3 小时
- 新手友好度
- 78/100
- Issue 类型
- 缺陷
- 描述清晰度
- 描述清楚
- 活跃度
- 活跃
- 技术栈
- github, typescript
调研方向
阅读 .github/agents/squad.agent.md 和 .squad/templates/ralph-reference.md,然后将其中的指示与 squad watch --execute 所描述的行为进行比较。更新 Ralph 分派指示,使其在 .squad/ralph-instructions.md 存在时加载该文件,并修正参考文件中的自引用。当应用内的分派路径遵循用户自有的指示,且引用链指向预期文件时,即为完成。
由索引模型根据 Issue 内容生成。
描述
Problem
.squad/ralph-instructions.md is the user-owned file for Ralph's repo rules. Its own header says squad init creates it and squad upgrade never overwrites it. But only squad watch --execute tells the spawned session to read it.
The in-app path never mentions the file. "Ralph, go" and coordinator-driven issue dispatch run from .github/agents/squad.agent.md (coordinator v1.0.1) and its on-demand .squad/templates/ralph-reference.md, and neither references .squad/ralph-instructions.md. So any rule a user writes there is skipped whenever the coordinator, rather than watch --execute, dispatches issue work.
Observed with squad-cli 1.0.1 on Windows:
- The repo's
ralph-instructions.mddefines a multi-host claim protocol: assign the issue, comment "Claimed by ", and run an election over the issue timeline. - An in-app coordinator session dispatched about 10 issue sessions without claiming any of them.
- Two issues were worked twice by the same coordinator across context windows, which a claim check would have prevented.
- Other rules in that file are skipped too, including host concurrency limits and the round-report format.
.squad/templates/ralph-reference.md line 11 also points to itself ("Read .squad/templates/ralph-reference.md…"), so the reference chain ends there.
Expected
Every Ralph/coordinator work-dispatch path loads .squad/ralph-instructions.md when it exists, with the same precedence watch --execute gives it. That way the user-owned rules apply no matter how work is dispatched.
Suggested fix
- In
squad.agent.md, in the Ralph section and before any issue dispatch: "If{TEAM_ROOT}/.squad/ralph-instructions.mdexists, read it and follow it before selecting or dispatching issue work." - Fix the self-reference in
templates/ralph-reference.md. - Optionally, have the coordinator load it once per session alongside
team.md/routing.md.
Workaround
Add a pointer in .github/copilot-instructions.md, which squad upgrade does not manage.
Related: #1314 (documenting the escape hatch).
- 主要语言
- TypeScript
- 星标
- 3.4k
- 派生
- 516
- 平均合并
- 1 天 15 小时
- 30 天内合并 PR
- 116
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
github/squad 的其他 Issue
-
bug
难度 2/5 1-3 小时 新手友好度 84/100
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 77/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
相似的 Issue
-
bot:ai-assisted component:platform-js status:untriaged
难度 1/5 1 小时以内 新手友好度 74/100
midnightntwrk/platform-js#38 ·
-
难度 2/5 1-3 小时 新手友好度 68/100
ranxianglei/billion-context#7068 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
mybigday/whisper.rn#348 ·
-
enhancement severity:low
难度 2/5 1-3 小时 新手友好度 82/100
Battle-Cattle/BCUK-Bot-4#1075 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 67/100
ilan-pinto/roaring-lions#1552 ·
维护者通常 1 天内回复