You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
0.22: normalize provider names in the CLI and name the package in daemon-side missing-provider hints #4852
Follow-up from the review of #4846 (#4846 (comment)). Three gaps that appear now that managed providers such as Limrun are optional plugins. None is fixed in #4846.
1. Provider names are not normalized in the CLI
src/cli/connection/provider-policy.ts looks a provider up by the name as written. A remote profile with leaseProvider set to limrun (with spaces) passes the profile parser unchanged. connect --remote-config then misses both the plugin lookup and the catalog lookup, treats the profile as generic, and commits it with no plugin. A later open reaches the daemon, which trims the name to limrun.
Required: provider lookups for profiles and stored connections use the same name normalization as the daemon, before any capability check. Old records stay readable. New state is written with the canonical name.
2. The daemon-side hint names no package
packages/daemon/src/sessions/handlers/lease.ts (missing-runtime guard): the SDK leases.allocate call with leaseProvider: limrun, against a daemon that has Limrun credentials but no plugin, fails with a restart hint that names no package and no install command. The same happens for an embedded host started without the factory, and for CLI open when the plugin is in the CLI store but not in the running daemon. apps on a pending connection can say the instance is unallocated.
Required: the daemon's missing-runtime and catalog admission paths use the managed provider catalog and, for an absent managed provider, give the package, the versioned install command, and the restart or embedded-host guidance. Errors for failed registrations and for unallocated instances of registered providers stay as they are.
3. An installed Limrun plugin without credentials shows as failed
packages/provider-limrun/src/plugin.ts setup fails when LIMRUN_* is unset, so the daemon inventory lists the claim as failed (missing_provider_credentials). The built-in was dormant in that case. Decide: keep the failed listing, or make a provider with no credentials dormant.
Completion conditions
Tests for a padded provider name on connect --remote-config and on a stored connection.
Tests for the daemon hint: absent managed provider names the package and install command; failed registration and unallocated instance keep their current errors.
A recorded decision for item 3, with a test for the chosen behavior.
The issue reports concrete existing defects: non-normalized provider names can cause remote profiles to be committed without plugins, and daemon missing-runtime hints fail to name the required package or install command. It also points to specific files and completion conditions, so a maintainer can act on it.
Activity
apex-sentinel-staging commentedon Nov 20, 2026
Apex Sentinel · Issue review
Suggested label:
bugThe issue reports concrete existing defects: non-normalized provider names can cause remote profiles to be committed without plugins, and daemon missing-runtime hints fail to name the required package or install command. It also points to specific files and completion conditions, so a maintainer can act on it.
Required sections