Support "use workflow" serialization for Sandbox and Command

[cramforce]

Does not add "use step" anywhere, so users will have to do this themselves. It could be done, but it is hard to reconzile with the use of AbortSignals and also won't be very useful in practice.

Introduces Sandbox.setCredentials to allow creating APIClient from serialized values.

Note: this needs #109 to actually work

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
sandbox	Ready	Preview, Comment, Open in v0	Mar 27, 2026 9:54pm
sandbox-cli	Ready	Preview, Comment, Open in v0	Mar 27, 2026 9:54pm
sandbox-sdk	Ready	Preview, Comment, Open in v0	Mar 27, 2026 9:54pm
sandbox-sdk-ai-example	Ready	Preview, Comment, Open in v0	Mar 27, 2026 9:54pm
vercel-sandbox-sdk-tests	Error	Open in v0	Mar 27, 2026 9:54pm
workflow-code-runner	Ready	Preview, Comment, Open in v0	Mar 27, 2026 9:54pm

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/​next@​16.0.10
	npm/​@​workflow/​serde@​4.1.0-beta.2
	npm/​@​workflow/​core@​4.2.0-beta.73
	npm/​react@​19.2.3
	npm/​workflow@​4.2.0-beta.73
	npm/​zod@​4.3.6
	npm/​ai@​5.0.157
	npm/​react-dom@​19.2.3

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		High CVE: npm path-to-regexp vulnerable to Regular Expression Denial of Service via multiple route parameters CVE: GHSA-37ch-88jc-xwx2 path-to-regexp vulnerable to Regular Expression Denial of Service via multiple route parameters (HIGH) Affected versions: < 0.1.13 Patched version: 0.1.13 From: pnpm-lock.yaml → npm/workflow@4.2.0-beta.73 → npm/path-to-regexp@0.1.12 ℹ Read more on: This package | This alert | What is a CVE? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Remove or replace dependencies that include known high severity CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/path-to-regexp@0.1.12. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report