Tools and trust: plugins that need plugins and programs, and trusting a plugin
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 8/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- nodejs, zig
调研方向
This is a tracking issue for a design plan, so start by reading plans/TOOLS_AND_TRUST_PLAN.md in the fizzyedit/plans repository. The checklist names core.darwin_spawn, settings.zon, the app/ tools manager and the tools/ registry directory as the areas each step touches. Work happens in the numbered sub-PRs, not here, so a newcomer should pick one step only after the maintainers confirm its scope.
由索引模型根据 Issue 内容生成。
描述
The plan is plans/TOOLS_AND_TRUST_PLAN.md in fizzyedit/plans. Three mechanisms, kept apart:
- Plugin to plugin: "works with", never "requires". A plugin names the plugins it works best
with, and why, in its identity manifest. The store offers them together; a missing partner is
never a load failure. - Tools: programs fizzy manages for plugins (
zls,zig, Node, npm packages, agent
binaries,fizzy-mcp). Specs are data in the registry; plugins ask through an SDK service; every
tool is configurable in Settings > Tools (system, managed, or a path the person names), and
nothing installs without asking. - Trust. Installing a plugin for the first time asks the person to trust it, saying it runs as
native code with their permissions and that they are trusting its author. Trust, bound to the
plugin's source, lets its updates install automatically; a change of source asks again.
Each step is its own PR saying Part of #<this issue>:
- 1.
core.darwin_spawntakes extra environment variables; one spawn helper for tools - 2. Trust: the dialog, the record in
settings.zon, auto-update gated by trust, the source-change hold, plugins from outside the store - 3. The tools manager (
app/) and the SDKtoolsservice (moves the fingerprint) - 4. Settings > Tools, and the tool consent dialog
- 5.
tools/in the registry (fizzyedit/plugins), exported with the catalog - 6. First consumers: zls for the zig plugin; the chat's agent picker (Codex, then Node and npm agents);
fizzy-mcp - 7.
works_within the manifest, shown and offered by the store
🤖 Generated with Claude Code
- 主要语言
- Zig
- 星标
- 1.5k
- 派生
- 40
- 平均合并
- 5 小时 32 分钟
- 30 天内合并 PR
- 537
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
fizzyedit/fizzy 的其他 Issue
-
维护者通常 1 天内回复
-
难度 5/5 一周以上 新手友好度 25/100
维护者通常 1 天内回复
-
难度 3/5 1-2 天 新手友好度 52/100
维护者通常 1 天内回复
-
难度 3/5 1-2 天 新手友好度 49/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 58/100
维护者通常 1 天内回复
相似的 Issue
-
0.2.1-rc.3 compatibility: 21 peer ranges enumerate exact versions, so rc.3 is rejected可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭
难度 2/5 1-3 小时 新手友好度 76/100
NanmiCoder/dsh-agent-teams#277 ·
维护者通常 1 天内回复
-
random_elements(unique=True) on an OrderedDict: ZeroDivisionError once only zero weights remain, AssertionError with use_weighting=False可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭
难度 2/5 1-3 小时 新手友好度 85/100
维护者通常 13 天内回复
-
Validate CI command vectors before indexing Cargo subcommands可能已有人在做 @amandeavor 今天认领。 未关闭bug ci good first issue
难度 2/5 1-3 小时 新手友好度 88/100
维护者通常 1 天内回复
-
[ordering-review] workshop order graph: 1 confirmed ordering problem, 3 cycles are false positives未关闭
难度 2/5 1-3 小时 新手友好度 78/100
githubnext/gh-aw-workshop#4943 · 1 条评论 ·
维护者通常 1 天内回复