state-mcp: launch level switch to prohibit external backends; document env var effects

未关闭
#2,358 3 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
45/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
typescript

调研方向

Start at the squad state-mcp CLI entry point and trace how the three backend environment variables enable experimental tools; inspect the doctor command and its documentation. Add the launch switch, make doctor report configured variables and warn when the switch is set, then verify the bridge refuses external backends despite inherited variables and the docs describe each variable’s effect.

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

描述

squad squad:architect wave:2-soon

From enterprise integrator feedback (Teams, Oct 28): operators want local only operation to be explicit and fail closed.

Ask:

  1. A launch level switch (CLI flag and or .mcp.json arg, e.g. --no-external-backend) that makes squad state-mcp refuse to enable experimental backend tools even if SQUAD_EXPERIMENTAL_BACKEND / SQUAD_BACKEND_URL / SQUAD_BACKEND_TOKEN are inherited from the environment.
  2. Documentation of exactly how those env vars affect the bridge, and what doctor reports when a backend is configured.
  3. doctor warns when backend env vars are present but the switch is set.

Target: 2.0.0-preview.3. Related: backend wire contract review (preview.1 to dev) found no changes; this is a hardening add.

主要语言
TypeScript
星标
3.4k
派生
516
平均合并
1 天 15 小时
30 天内合并 PR
116

环境准备

从这里开始

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

github/squad 的其他 Issue

查看 github/squad 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

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