Repository navigation
Description
Purpose and evidence
0.22 stops bundling hosted device providers with the default installation. AWS Device Farm already presents the plugin factory shape inside core (packages/provider-webdriver/src/aws-device-farm-provider.ts plus aws-device-farm-connection.ts, PR #3312). The one capability it needs that ProviderPluginHost does not expose is a host-command runner: the provider drives aws devicefarm ... through runHostCommand, which core currently supplies in src/provider-webdriver.ts.
Final 0.22 delivery contract
For AWS Device Farm (@agent-device/aws-device-farm), follow the maintainer decision and shared acceptance in #4591. Core may retain only declarative help/docs/schema/catalog and installation-guidance metadata. Do not ship the plugin factory, executable implementation, plugin-only workers or dedicated runtime dependencies in the core npm package. Lazy-loading code that remains in the tarball is not extraction.
Plugin code is installed separately, on demand, by the existing agent-device plugin manager. T3 Code and e2e must use that shared installation/selection lifecycle and machine-readable inventory/recovery, rather than bespoke npm commands or private-store manipulation. Keep current v2 factories and ./agent-device; older manifest/static-registration examples below describe historical preparation and do not override this final distribution contract. Preserve independently required core contracts and local-device code.
Required behavior and boundary
- Extend the experimental plugin SDK:
ProviderPluginHostgainsrunHostCommand(command, args): Promise<{ stdout }>backed byrunCmdwith the bounds core uses today (10 MiB buffer, 30 s). Keep the SDK declaration small; the packed declaration-size guard from feat: add managed provider plugin infrastructure #3121 stays green. - New workspace package
packages/provider-aws-device-farmpublishing@agent-device/aws-device-farm, built and released like TestMu. The default export returns{ webDriver, connection }; the manifest declaresprovider: "aws-device-farm"and theconnectioncapabilities fromCLOUD_WEBDRIVER_PROVIDER_DECLARATIONS(nocredentialVariables: the AWS CLI credential chain has no environment fingerprint, and the fingerprint tests pin that). - Move
aws-device-farm.ts,aws-device-farm-artifacts.ts,aws-device-farm-provider.ts,aws-device-farm-connection.ts,aws-device-farm-connection-verification.tsand their tests out ofprovider-webdriver. Therequires --aws-project-arn <arn> or AWS_DEVICE_FARM_PROJECT_ARNmessages and the flag-then-AGENT_DEVICE_*-then-AWS_*selector order stay as they are. - Core drops
aws-device-farmfromBUNDLED_CLOUD_WEBDRIVER_PROVIDERSandRESERVED_PLUGIN_PROVIDERS;connectionProviderCapabilitiesand therequiresAppAttachmentreconnect hint inconnection-presentation.tskeep working from the manifest. - Help,
website/docs/docs/aws-device-farm.md,device-clouds.md,plugins.md, and the README move the provider to the plugin install flow.
agent-device plugins add @agent-device/aws-device-farm
agent-device connect aws-device-farm --platform android --aws-project-arn <arn> --aws-device-arn <arn> --aws-app-arn <arn>Completion and validation
node scripts/check-provider-plugin.mjs packages/provider-aws-device-farmpasses with a fixtureawsonPATH.- The published name drops the
provider-prefix and the directory keeps it.packages/provider-aws-device-farm/package.jsondeclares"name": "@agent-device/aws-device-farm". The provider plugin catalog (src/commands/provider-plugin-catalog.ts), help, docs, and everyplugins addexample use that name. This is the convention thatpackages/provider-testmu(@agent-device/testmu) andpackages/provider-revyl(@agent-device/revyl) follow. - The AWS provider-scenario tests (
cloud-webdriver-provider-adapters,cloud-webdriver-provider-regressions,stale-provider-runtime-admission) build the runtime from the plugin factory with the fake host command. pnpm check:affected --runpasses; Size report shows the default install shrinking.- One live Device Farm remote-access session with the packed plugin, recorded in the PR, or the exact blocker named.
Dependencies and readiness
Blocked by: #3312 landing on main; do the BrowserStack extraction first so the packaging template is proven twice before the SDK change here.
Effort: M. Risk: medium (SDK surface grows by one method; AWS live verification needs an account).
Activity
thymikee commentedon Nov 16, 2026
Decision: plugin distribution: final 0.22 extraction means separate agent-device-managed installation, not merely lazy loading. Core retains declarative help/docs/catalog metadata, with no shipped plugin implementation or dedicated dependency closure. T3 Code and e2e use the same management owner and observable install/selection/recovery contract. The issue body now states this explicitly; #4591 owns shared consumer acceptance and the approximately 3 MB unpacked-core target. Earlier seam-only/static-registration or v1 manifest wording is historical preparation, not the final requirement. Existing extraction owners, sequencing, host/session ownership and publication prerequisites remain in force.
apex-sentinel-staging commentedon Nov 16, 2026
Apex Sentinel · Issue review
Suggested label:
featureThe issue requests a refactor/packaging change: extract AWS Device Farm support from core into a separate plugin package and add a ProviderPluginHost capability, with concrete implementation steps and validation. It is not reporting broken behavior or asking for help.
Possible duplicates
@agent-device/browserstackplugin #3309: refactor(provider-webdriver): ship BrowserStack as the@agent-device/browserstackplugin (similarity 0.81)@agent-device/limrunplugin #3311: refactor(provider-limrun): ship Limrun as the@agent-device/limrunplugin (similarity 0.72)thymikee commentedon Nov 20, 2026
Done on
0.22under this issue's own terms: #4617 extracted AWS Device Farm as the@agent-device/aws-device-farmplugin. The published nightly was installed and activated by a clean consumer (#4591 status of 2026-11-18).Stated plainly: no live AWS Device Farm session was run. The issue allows "or the exact blocker named", and the PR body names it: no admitted Device Farm route, and AWS account access and the project, device and app ARNs were not verified. The route
setUpSlot -> plugin.setup -> host.runHostCommandwith the daemon cwd and env therefore has unit and fixture coverage only. Reopen if a live run is wanted before the release.