Repository navigation
Description
Purpose and evidence
0.22 stops bundling hosted device providers with the default installation. Limrun is the largest bundled provider and the only one with a public SDK surface: packages/provider-limrun (about 9 kLOC with tests), @limrun/api dev-bundled through tsdown.config.ts (with the @limrun/xdelta3-wasm omission alias), the agent-device/limrun export (src/sdk/limrun.ts, LimrunRuntime, session types documented in client-api.md), the LIMRUN_*/LIM_*_INSTANCE_* credential reader in src/provider-limrun-credentials.ts, the Android ADB and Apple host adapters in src/sdk/limrun-runtime-dependencies.ts, and connect limrun in src/cli/connection/limrun-profile.ts. Doublespeed (#2112) is the template for a direct instance provider as a plugin: it returns { runtime, platformModule, connection } and receives Apple helpers through host.apple.
Final 0.22 delivery contract
For Limrun (@agent-device/limrun), 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
- New publishable package
@agent-device/limrun, built frompackages/provider-limrun(the directory keeps its name; the package name losesprovider-), ESM with@limrun/apias a regulardependenciesentry, not bundled: users then get Limrun andundicisecurity fixes on reinstall or through their ownoverrides, without an agent-device release. Remove the@limrun/apialwaysBundle/neverBundleentries and the@limrun/xdelta3-wasmomission alias fromtsdown.config.ts; the plugin's install size (about 4.1 MB for@limrun/apiplusundiciandws) is accepted. Manifest declaresprovider: "limrun", theconnectioncapabilities core hardcodes today (supportsDeferredAppSelection,supportsDirectPortReverse), andcredentialVariablescovering the account and instance variables. Core's per-platform fingerprint narrowing (readLimrunCredentialValuesby lease backend) must survive: either the manifest grows a per-backend credential declaration or the plugin keeps a fingerprint hook; decide in the PR and record it inplugins.md. ProviderPluginHostgains what Limrun needs beyond Doublespeed'shost.apple: the Android ADB adapters (createInteractor, port reverse, app listing, logcat, keyboard state) anddownloadFile/archiveDirectory. Keep the SDK declaration small; prefer onehost.androidfacet mirroringsrc/sdk/limrun-runtime-dependencies.ts.connect limrunmoves into the plugin'sconnection.resolve/verify, including the instance-variable validation and the--devicerefusal. Core deleteslimrun-profile.ts,provider-limrun-credentials.ts,provider-limrun-runtime.ts, thelimrunbranches inprovider-policy.ts,provider-credential-fingerprint.ts,provider-device-runtimes.ts, and theprovider_runtime_skippedpartial-instance handling, or moves them behind the plugin seam.- Public API:
agent-device/limrunis removed from the core exports (breaking, called out in the 0.22 release notes) or re-pointed at the plugin package;client-api.md,limrun.md,device-clouds.md,plugins.md, help topics, and the README follow.
agent-device plugins add @agent-device/limrun
export LIMRUN_API_KEY=...
agent-device connect limrun --platform androidCompletion and validation
node scripts/check-provider-plugin.mjs packages/provider-limrunpasses.- The published name drops the
provider-prefix and the directory keeps it.packages/provider-limrun/package.jsondeclares"name": "@agent-device/limrun"(today the private@agent-device/provider-limrun). 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. src/__tests__/limrun-runtime.test.ts, the Limrun daemon tests (http-server-limrun-uploaded-apps, provider-credentials, lease-expiry) and the provider-scenario suites run against the plugin factory.- Size report shows the default install dropping the Limrun runtime and
@limrun/api. - Retain bundled
undiciin core only for demonstrated independent core consumers, such as provision-kit install downloads. Maestro/plugin networking is delivered by its separately installed package. After extraction, trace dependency and packed-module ownership:@limrun/apiand its runtime dependency closure resolve only from the Limrun installation, while shared core dependencies retain only their actual core callers. Do not use a bundled SDK facade or historical Maestro coupling to keep plugin implementation bytes in core. - One live Limrun iOS and one Android session with the packed plugin, recorded in the PR.
Dependencies and readiness
Blocked by: #2112 landing (shapes host.apple and the direct-provider plugin route) and the BrowserStack/AWS extractions in this milestone. After both Limrun and Doublespeed are plugins, #2616/#2624 (shared app-log poller) and the other mirrored modules (facts runtime, interaction operations, deployment runtime) can be extracted into a shared instance-provider kit without touching core.
Effort: L. Risk: high (public SDK surface, host adapters, credential fingerprint semantics).
Activity
thymikee commentedon Oct 9, 2026
Ordering correction: the shared app-log poller (#2616 / #2624) is extracted first, from Limrun into
capture-kit, as the latest #2112 review asks. It doesn't wait until both Limrun and Doublespeed are plugins. Waiting would make each plugin depend on the other's extraction. Moving Limrun out of core can then consume the shared owner. The other mirrored modules (facts runtime, interaction operations, deployment runtime) can still follow once both plugins exist.thymikee commentedon Oct 10, 2026
Scope update:
@limrun/apibecomes a regular dependency of@agent-device/limruninstead of being bundled into the plugin. Users can then take Limrun andundicisecurity fixes themselves (reinstall oroverrides), and the tsdown Limrun bundling config goes away. The larger plugin install is accepted. Core keepsundicibundled for MaestrorunScriptHTTP and provision-kit downloads. Context: #3363.thymikee commentedon Oct 16, 2026
Sequencing note from #3747 (provider plugins v2):
@agent-device/limrunshould ship on plugin contract v2 (feat(plugins): plugin contract v2 and one provider registry #3755): a default factorylimrun(options), an./agent-deviceexport, and credentials declared withbyBackend, which keeps the per-backend narrowing this issue requires.RESERVED_PLUGIN_PROVIDERSandDEFAULT_PROVIDER_RUNTIME_REQUIRED_IDS.leaseProvider: 'limrun'withprovider-not-registered(fix(daemon): refuse leases for providers without a registered runtime #3748), not record a lease with no device behind it.agent-device/hoststartAgentDevice({ plugins: [limrun(...)] })(feat(host): startAgentDevice() for embedder-owned daemons #3757). The 0.22 removals are 0.22: remove superseded plugin, client and environment APIs #3759.thymikee commentedon Oct 20, 2026
Part of the 0.22 removals (#3759, section 4). After Limrun ships as
@agent-device/limrun, remove the built-in Limrun first-claim special case insrc/builtin-provider-plugins.ts, where Limrun is dormant without credentials and its plugin is built inline. Keep the registry's first-claim semantics for whatever order the embedder or store supplies.apex-sentinel-staging commentedon Oct 31, 2026
Apex Sentinel · Issue review
Suggested label:
featureThe issue specifies a concrete refactor to extract Limrun into a separate @agent-device/limrun plugin, including required behavior, packaging, API removal, tests, and docs; this requests new structure/enhancement rather than reporting a defect or asking for help. It is blocked by related work but is detailed enough for a maintainer to act on once dependencies land.
Possible duplicates
@agent-device/browserstackplugin #3309: refactor(provider-webdriver): ship BrowserStack as the@agent-device/browserstackplugin (similarity 0.77)@agent-device/aws-device-farmplugin #3310: refactor(provider-webdriver): ship AWS Device Farm as the@agent-device/aws-device-farmplugin (similarity 0.72)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.
refactor(sdk): remove the bundled Limrun SDK facade (#4691)
thymikee commentedon Nov 19, 2026
Decision for the 0.22 Limrun extraction: defer the Android interactor routing change to the extraction PR. Keep the built-in adapter’s direct factory until the extracted package and core can switch together. At cutover, use one synchronous core-owned adapter selected by the registered runtime and bound to the admitted Android lease and its provider-owned executor. The plugin-facing contract can carry a structural, opaque lease-bound handle. Core resolves it to the branded interactor internally. Remove the direct embedded path in that cutover and report a typed capability failure if the binding is missing.
Acceptance: prove the separately installed plugin builds against the packed declaration surface, then run the packed registry-to-daemon Android session through snapshot, fill via the provider text route, and press. Record the leased serial and confirm only its resources are cleaned up. #4728 remains held for its exact-head live evidence and coordination with the host-authority review on #4720.
refactor(limrun): add transitional v2 plugin factory and move credent…
refactor(limrun): add transitional v2 plugin factory and move credent…
46 remaining items
refactor(connection): read the connection provider from one helper
fix(auth): store a pending login unless the provider plugin is refused
fix(connect): hold a login only until its provider is admitted
test(connect): name the new tests for the modules they pin
refactor(limrun): ship Limrun as the @agent-device/limrun plugin
fix(connection): forget an ended lease without loading the provider p…
fix(connection): keep a recorded ended-lease policy as the authority
fix(connection): read an unrecorded ended-lease policy from the plugi…
fix(connection): answer the ended-lease policy at the point of use
fix(connect): admit the provider plugin before authentication and bef…
fix(auth): keep a new connect login in memory until its provider is a…
refactor(connection): read the connection provider from one helper
fix(auth): store a pending login unless the provider plugin is refused
fix(connect): hold a login only until its provider is admitted
test(connect): name the new tests for the modules they pin