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

オープン
  • 何か問題がありますか？
#196 コメント 4 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
25/100
issue の種類
機能追加
明瞭さ
説明が足りない
活発さ
活発
技術スタック
typescript
領域
developer-experience, tooling

調査の方向性

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.

索引モデルが issue の本文から書いたものです。

説明

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.

主要言語
TypeScript
スター
1k
フォーク
71
平均マージ
13時間 14分
マージ済み PR（30日）
66

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

stepfun-ai/Step-Code のほかの issue

stepfun-ai/Step-Code の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。