Repository navigation
Description
Part of #3747. The breaking removals for 0.22. The non-breaking preparation landed in 0.21.x (see "Done in 0.21.x" below).
Each section below is one PR, and each stays under 2,500 changed lines.
Final 0.22 delivery contract
For the extracted first-party plugins, 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.
1. Plugin v1 (est. 900–1,500 lines)
- Remove the v1 loader adapter (
packages/plugins/src/legacy.ts), the v1 discovery and store branches, the manifest credential and capability fallbacks, and the install-time v1 collision checks. - Keep package-export resolution, entry containment checks and registry validation.
@agent-device/testmu: remove the v1 entry (src/plugin.ts), its build entry and theagentDevicePluginmanifest declaration.- Migration note for plugin authors: v1 manifest → v2
AgentDevicePluginFactory.
2. Managed clients (est. 1,500–2,300 lines)
createAgentDeviceClientdefaults todaemonLifecycle: 'attach'.- Remove
managedand the client transport's implicit start, replace and timeout-kill paths. - Keep explicit
ensureDaemon(), quiesce, CLI/MCP ensuring, remote attachment, and the shared startup helpers they still use. - Migration note for library clients: call
ensureDaemon()for a detached daemon, orstartAgentDevice(imported fromagent-device) to own one in-process.
3. Ambient SDK defaults (est. 900–1,600 lines)
- Remove the process captures in
src/sdk/host.ts. Released SDK functions then need an explicit host: Android adb, artifacts, Metro, remote-config and the public Limrun construction. resolveRemoteConfigProfilerequiresenv, andcreateLocalArtifactAdapterrequirescwd.- Review refactor: read host settings from HostEnvironment in root src and remaining packages #3751's waived factory boundaries one by one.
- Remove the SDK entries from R86
PROCESS_ENTRIES(scripts/layering/process-globals-policy.ts). - Keep the executable captures and
startAgentDevice's documented optional-host capture.
4. Built-in provider special cases
- After refactor(provider-limrun): ship Limrun as the
@agent-device/limrunplugin #3311 extracts Limrun, remove the built-in Limrun first-claim special case (src/builtin-provider-plugins.ts). Keep the registry's first-claim semantics. This is tracked in refactor(provider-limrun): ship Limrun as the@agent-device/limrunplugin #3311.
Done in 0.21.x (non-breaking)
startAgentDevicefrom the mainagent-deviceentry (feat(sdk): start an embedded runtime from the main entry #3843).- The embedded runtime's owner closes it:
daemon stoprefuses embedded runtimes (refactor(daemon): close embedded runtimes only from their host #3850). - TestMu's v2 plugin no longer reads capabilities from its v1 manifest (refactor(daemon): close embedded runtimes only from their host #3850).
Done when
- The 0.22 docs and release notes carry migration notes for plugin authors (v1 → v2), library clients (
ensureDaemon()orstartAgentDevicefromagent-device), and CLI/MCP users. - There are changesets for every affected package.
Activity
refactor(plugins): remove the version 1 provider plugin contract (#3759…
thymikee commentedon Nov 14, 2026
Current state: sections 1 and 3 are integrated into
0.22.4d75aa414f.e29ed5d0ac.getaddrinfo ENOTFOUND api.callstack.ai; its partial work is preserved, with no PR or final validation. No provider fallback is being used.@agent-device/limrunplugin #3311 and must follow the BrowserStack → AWS Device Farm → Limrun extraction sequence.This umbrella remains open. Managed-client removal, Limrun's built-in special-case removal, and the complete migration/release-note rollup are still required.
refactor(plugins): remove the version 1 provider plugin contract (#3759…
refactor(plugins): remove the version 1 provider plugin contract (#3759…
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 describes a planned set of breaking API removals and migration/documentation deliverables for a 0.22 release, with concrete tasks and acceptance criteria, rather than reporting broken behavior or asking for help.
refactor(plugins): remove the version 1 provider plugin contract (#3759…
refactor(client): remove managed daemon lifecycle (#4614)