modelstudioai / modelstudioai/cli
Allow opting out of auto-update and of the automatic `bl skill init` after updates
还没有人认领这个 Issue。
- 主要语言
- TypeScript
- 星标
- 333
- 派生
- 28
- 平均合并
- 1 天 9 小时
- 30 天内合并 PR
- 33
描述
bl currently self-updates silently and then unconditionally re-runs bl skill init, with no persistent way to opt out of either step.
What happens
- Any command (e.g. a scheduled
bl usage token-plan) triggersshouldAutoUpdate()when the installed version is a major behind, or more than 3 minors behind (packages/runtime/src/utils/update-checker.ts). It then runsnpm install -g bailian-cli@latestin the middle of the user's command. - On success,
syncAgentSkillsAfterUpdate()runsbl skill init, which symlinks everybailian-*skill into every detected agent directory (~/.claude/skills,~/.codex/skills,~/.config/opencode/skills,~/.pi/agent/skills,~/.agents/skills, …).bl updatedoes the same viaupdateAgentSkill()(packages/commands/src/commands/update.ts). - The only gate is
ctx.settings.quiet, which comes from the per-invocation--quietflag and is not aconfig.jsonkey (packages/core/src/config/loader.ts), so it cannot be made persistent.bl skill inititself has no flags to limit targets.
Why this is a problem
Users who manage their agent skill directories elsewhere (dotfiles, a config-as-code repo) have their removals silently reverted on the next update. In my case 10 skills I had removed came back into five agent homes because a cron-style quota probe happened to run after 1.24.0 was published (telemetry: skill init at 2026-09-11T13:48:04Z, cliVersion 1.24.0, immediately after an in-flight 1.20.0 usage token-plan).
Request
Two independent, persistent switches (config.json key and/or env var), e.g.:
BAILIAN_AUTO_UPDATE=0/"auto_update": false— never runnpm install -gimplicitly; only print the "update available" notice.BAILIAN_SKILL_SYNC=0/"skill_sync": false— never runbl skill initimplicitly after an update (both the auto path andbl update).
Optionally, bl skill init --agent <list> so the sync can be scoped even when enabled.
Environment: bl 1.24.0, npm global install, macOS 26.6, node v26.8.2.
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
调研方向
从 packages/runtime/src/utils/update-checker.ts 和 packages/core/src/config/loader.ts 开始,追踪自动更新和持久化设置,然后检查 packages/commands/src/commands/update.ts 以及 bl skill init 入口点。验证这两个开关能独立阻止隐式 npm 更新和技能同步,同时保留更新通知和显式技能初始化行为。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- nodejs, typescript
- 领域
- cli, developer-experience, tooling
- Issue 类型
- 功能
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 活跃度
- 活跃
- 描述清晰度
- 基本清楚
- 新手友好度
- 63/100