The Vercel Sandbox CLI is now more agent-friendly

The Sandbox CLI version 4.0.1 ships four output and error improvements:

• 
  New sandboxes point users towards how to connect into them.
  
  
• 
  A sandbox not found error shows where to look for existing sandboxes.
  
  
• 
  Common mistakes, like typing a command after sh, redirect to the command that was intended.
  
  
• 
  Outdated installs show an update notice when they create a new sandbox.
  

Each of these messages now carries the action to take next instead of leaving you to work it out.

New sandboxes tell you how to connect​

create and fork output now ends with a connect hint, so a fresh sandbox never leaves you wondering what to type next.

Not found errors point you to your sandboxes​

When a command references a sandbox that does not exist, the error is quiet and actionable instead of a raw API dump. Setting DEBUG=sandbox:errors restores the request detail for debugging.

A misused command explains the right one​

sh opens a plain interactive shell, so it takes no command of its own. The CLI can now return precise answers that rewrite the attempt into the command that does what you meant, whatever the command is.

Outdated installs warn you at creation time​

create, sh, and run check for a newer published CLI and print an update notice when the install is behind. The check is cached to a file and refreshed at most once per hour; when a lookup does run it happens concurrently with the creation request, so it adds no latency. Creation defaults, such as the base image, are chosen client side, so an outdated global install silently keeps old defaults. Prerelease versions skip the check, and SANDBOX_SKIP_VERSION_CHECK=1 disables it.


Learn more in the Sandbox CLI documentation.

Read more

Continue reading...