What happened
Short summary I tried to install @computeragent/runtime-e2b (and similarly @computeragent/runtime-bwrap / @computeragent/runtime-vzvm) with npm but got a 404 (package not found). The package exists in the monorepo at packages/runtime-e2b, but it appears not to be published to the public npm registry, so npm install fails.
What you expected
Either the package should be published to npm (so npm install works), or the README/docs should clearly state that these are workspace-only packages and document how to install/build them locally (e.g., clone repo + pnpm install && pnpm -w build + npm pack / local install, or instructions for npm link), or publish them to a registry (npm or GitHub Packages) and update docs with the registry URL.
Environment
macOS
Logs / stack trace
Quick checks
What happened
Short summary I tried to install @computeragent/runtime-e2b (and similarly @computeragent/runtime-bwrap / @computeragent/runtime-vzvm) with npm but got a 404 (package not found). The package exists in the monorepo at packages/runtime-e2b, but it appears not to be published to the public npm registry, so npm install fails.
What you expected
Either the package should be published to npm (so npm install works), or the README/docs should clearly state that these are workspace-only packages and document how to install/build them locally (e.g., clone repo + pnpm install && pnpm -w build + npm pack / local install, or instructions for npm link), or publish them to a registry (npm or GitHub Packages) and update docs with the registry URL.
Environment
macOS
Logs / stack trace
Quick checks
pnpm -r buildandpnpm -r testfrom the latest main