Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

Provider plugins v2, daemon ownership and host environment (umbrella)

未关闭
  • 哪里不对？
#3,747 2 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
8/100
Issue 类型
重构
描述清晰度
需要澄清
活跃度
活跃
技术栈
node.js, typescript
领域
backend, devtools

调研方向

This is a tracking umbrella with no code change of its own; the work sits in the child issues listed in the checklist (#3748 to #3759). The unblocked starting points are #3748 (refuse leases for providers without a registered runtime) and #3749 (HostEnvironment captured once at entry points), and the payload names no files or tests. Done means each child lands additively in 0.21.x and the external acceptance items are met.

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

描述

enhancement

Purpose

One provider plugin contract loaded three ways, an explicit owner for every daemon, and a daemon that reads no process globals.

The three ways a plugin loads:

  • built-in providers;
  • agent-device plugins add (the store);
  • a JS host that imports the plugin package as an ordinary npm dependency.

This replaces the current workaround in e2e's @e2e-dev/testmu. It fakes the plugin store: it symlinks the package into plugins/<uuid>/node_modules, writes a private AGENT_DEVICE_HOME, and lets a client start a detached daemon implicitly.

Release rule

Every child lands additively in 0.21.x. Superseded shapes keep working until #3759 removes them in 0.22.

Children

  • #3748 — refuse leases for providers without a registered runtime
  • #3749 — HostEnvironment captured once at entry points (foundation)
  • #3750 — HostEnvironment in platform and capture packages (blocked by #3749)
  • #3751 — HostEnvironment in root src and remaining packages (blocked by #3749)
  • #3752 — daemon runtime owns no process globals; ShutdownReport (blocked by #3749)
  • #3794 — explicit host for configuration reads; one entered runtime store (follow-up to #3763/#3772)
  • #3753 — gate: no process globals outside entry points (after #3794 part 1) (blocked by #3750, #3751, #3752)
  • #3754 — explicit daemon lifecycle: ensureDaemon() and attach clients
  • #3755 — plugin contract v2, one provider registry, inventory, ADR 0034 (blocked by #3748)
  • #3756 — @agent-device/testmu on plugin contract v2 (blocked by #3755)
  • #3757 — agent-device/host startAgentDevice() (blocked by #3772 and the HostEnvironment PRs #3763/#3775/#3777; design pass done 2026-10-17)
  • #3758 — proposal: per-lease provider options (not scheduled)
  • #3759 — 0.22 removals (blocked by all of the above and #3311)

Decisions (maintainer, 2026-10-16)

  • Plugins are factories called with options. A store install passes config.json options; a JS host calls testmu({ credentials }) directly.
  • No module-URL identity. Nothing relies on import.meta.url.
  • No Effect dependency.
  • { webDriver } stays a data descriptor. Plugins import only types from agent-device.
  • One registry. Sources compose in the order built-in → store → embedder. A plugin that fails is listed, not fatal.
  • The plugin set is fixed for a daemon's lifetime.
  • Clients never manage the daemon implicitly. Starting or replacing one is an explicit ensureDaemon() call. Embedders own their daemon through agent-device/host.
  • The ADR is brief. ADR 0034 records the plugin registry, with only a short note on daemon ownership.

External acceptance

  • e2e: tester-army/e2e migrates @e2e-dev/testmu and @e2e-dev/limrun to agent-device/host, deleting installPlugin and the CLI-based daemon stop. That work is tracked in e2e after #3757 ships.
  • #3311: the Limrun extraction ships @agent-device/limrun on the v2 contract from #3755.
主要语言
TypeScript
星标
5.1k
派生
339
平均合并
12 小时 53 分钟
30 天内合并 PR
644

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

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

callstack/agent-device 的其他 Issue

查看 callstack/agent-device 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

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