Question on plugin marketplace roadmap: when will marketplace-installed plugins load executable entries?

Đang mở
  • Có gì không ổn?
#196 4 bình luận 0 reaction 0 người được giao Xem trên GitHub

Maintainer thường phản hồi trong vòng 1 ngày

Chưa có ai nhận issue này.

Đánh giá

Độ khó
5/5
Thời gian dự kiến
Hơn một tuần
Mức phù hợp với người mới
25/100
Loại issue
Tính năng
Độ rõ ràng
Cần làm rõ
Mức độ hoạt động
Sôi nổi
Công nghệ
typescript
Lĩnh vực
developer-experience, tooling

Hướng nghiên cứu

Start by reading step/plugins.ts, core/resource-loader.ts, step/mcp.ts, agent-core/src/harness/agent-harness.ts, and config/src/migrations.ts to understand the current marketplace contract and extension boundaries. No specific implementation or tests are named; done would require maintainers to define which executable and declarative plugin capabilities, remote sources, and lifecycle hooks are in scope.

Do mô hình lập chỉ mục viết ra từ nội dung của issue.

Mô tả

area/plugin enhancement

Hi Step Code team,

We've been building Step Code plugins and testing against v0.1.1. We ran into what looks like a deliberate design boundary rather than a bug, and we'd like to confirm our reading and ask about the roadmap. Line references are against a 2026-09-24 snapshot of main.

What we verified (source + local TUI):

  1. step/plugins.ts L4-8 header says the built-in marketplace has a "deliberately smaller contract" and "this module owns discovery and provisioning only".
  2. L645-646: a manifest with entry yields "Executable plugin entries are recorded but not loaded by the Step marketplace facade." So a marketplace-installed plugin can never load executable code today.
  3. core/resource-loader.ts sources commands only from extension.commands (L752); its skill discovery roots (~/.stepcode/agent/skills, <cwd>/.stepcode/skills, ~/.agents/skills, settings skills) do not include ~/.stepcode/plugins/.... Verified locally: /plugin marketplace add + /plugin install succeeds and files land in ~/.stepcode/plugins/<name>/, but the plugin's commands never appear in the palette — /reload and a full process restart don't change it.
  4. step/mcp.ts L231-232 skips string mcpServers declarations; only inline objects are started.

Net effect: for marketplace-installed plugins, the only thing that runs is an inline mcpServers process. entry is recorded-but-not-loaded; commands/skills/agents are parsed and validated but never registered.

Questions:

  1. Any timeline for letting marketplace-installed plugins load an executable entry (or bridging the marketplace and extensions channels)? This is the single blocker for "install from a marketplace and it just works" for extension-shaped plugins.
  2. Any plan to wire manifest skills/commands/agents into the resource loader, so declarative marketplace plugins become slash commands / skills?
  3. We noticed agent-core/src/harness/agent-harness.ts has this.hooks = new UnavailableRegistry("hooks.on", ...), and config/src/migrations.ts states "Hooks have been renamed to extensions." Is a lifecycle-event mechanism (equivalent to the extensions' pi.on("turn_end" / "session_before_compact" / "tool_result")) on the roadmap for marketplace plugins? Our use case must act right before compaction; extensions can do that today, marketplace-delivered ones cannot.
  4. Minor: marketplace entries with an object source are skipped ("this runtime cannot fetch"), and string sources must resolve inside the checkout. Any plan to support remote owner/repo entries, so plugin authors can keep code in their own repo and just be indexed?

Context: we published a context-archive extension (MIT) at https://github.com/uos1231234/step-context-archive, with a declarative copy pending in a community marketplace PR. Happy to help test any of the above. If 1-3 are out of scope for now, we'll document the current contract in our README so users aren't surprised.

Thanks for the great work on Step Code.

Ngôn ngữ chính
TypeScript
Star
1k
Fork
68
Merge trung bình
13 giờ 14 phút
Pull request đã merge (30 ngày)
66

Chuẩn bị môi trường

Bắt đầu từ đâu

  1. Đọc hết issue, rồi đọc hướng dẫn đóng góp của dự án.
  2. Bình luận trên issue rằng bạn sẽ nhận — tránh hai người làm cùng một việc.
  3. Fork repository và làm thay đổi trên một nhánh.
  4. Mở pull request có tham chiếu số hiệu của issue.

Issue khác của stepfun-ai/Step-Code

Tất cả issue của stepfun-ai/Step-Code

Issue tương tự

Thêm issue về TypeScript

Nhận issue mới trong hộp thư của bạn

Bản tóm tắt ngắn những issue GitHub phù hợp với người mới.