cloud/remote-docker git ops fail on stable with "Cannot find package '@agentbox/sandbox-*'" — fixed by #270, needs a stable release

[positonic]

Summary

On the published stable (0.27.1), every host-relay git op against a cloud/remote box fails:

host executor failed: Cannot find package '@agentbox/sandbox-remote-docker'
imported from .../runtime/hub/apps/hub/chunk-YJ5MJOXK.js

Root cause is the pre-#270 resolveCloudBackend: a variable import(pkg) that esbuild never bundles, resolving against node_modules where the private @agentbox/sandbox-* packages don't exist. It affects all cloud providers; remote-docker is just the first hit (no account needed). Dev checkouts hide it via pnpm workspace symlinks.

#270 fixes exactly this and is in the 0.28 nightlies. Verified live: stable 0.27.1 → error above; 0.28.0-nightly.202607290901 + agentbox hub restart → the remote-docker git fetch/push path works on a published-layout install (clean npm prefix, no @agentbox/* in node_modules).

Corrections to my earlier posts: "also reproduces on nightly" was a stale running hub (it serves old code until agentbox hub restart); the tarball file-listing evidence was invalid (backends are code-split into anonymously named chunks, so neither filenames nor package-name greps can show them).

Version / environment

• @madarco/agentbox 0.27.1 (latest stable) — reproduces
• 0.28.0-nightly.202607290901 — fixed, once the hub is restarted
• Host: macOS (Apple Silicon); box: remote-docker → Ubuntu x86_64 VPS over SSH

Repro (stable)

1. agentbox remote-docker add <alias> <ssh> and create a box on it
2. From inside the box git push, or host-side agentbox git push|fetch <box>
3. → Cannot find package '@agentbox/sandbox-remote-docker'

Asks

1. Cut a stable release including fix(relay): inject cloud backends instead of resolving them from node_modules #270 — on stable, no cloud/remote box can complete any host-relay git op.
2. Release-note that upgrading requires agentbox hub restart (a running hub keeps serving pre-fix code), and that the 0.28 hub now needs Node >= 22.5 (stable's hub runs on 20.x, so this will bite upgraders).

[positonic]

(Superseded — diagnosis consolidated into the issue body above. Original text said the root cause was the variable import(pkg) in resolveCloudBackend; that stands, and #270 on nightly already ships the fix.)

[positonic]

(Superseded — consolidated into the issue body above; the two verified dead-end fixes are recorded in the comment below.)

[positonic]

For the record, two fix directions verified dead before finding #270: serverExternalPackages in the hub's next config (inert — it only affects statically-named imports) and literal import('@agentbox/sandbox-*') inside the relay (recreates the sandbox-* → sandbox-cloud → sandbox-docker → relay cycle the variable form was avoiding). #299 closed accordingly — #270's injected-loader design supersedes both.

(The two comments above are superseded by the updated issue body; kept as stubs for history.)

[positonic]

Confirmed end-to-end on my setup: npm i -g @madarco/agentbox@nightly (0.28.0-nightly.202607290901, Node 24) + agentbox hub restart → relay git fetch/push against a live remote-docker box works. Leaving this open to track the stable-release ask in the issue body; happy for it to be closed once that ships (or sooner if you track releases elsewhere).

[madarco]

Thanks @positonic, I've pached this on v 0.27.2 (nightly is a bigger change coming probably in 2 weeks). Let me know if this fixes for you!