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
Successful MicroSandbox startup emits debug diagnostics that look like runtime failures. The observed run finished successfully and opened VS Code, but normal helper EOFs, joined tunnel cleanup, and planned post-start delivery are labeled with error-like text.
Action items:
Keep routine one-shot external-runtime helper lifecycle messages out of ordinary debug logs, while preserving runtime stderr, warnings/errors, redaction, and detailed trace diagnostics.
Report successful pipe-bridge completion clearly; retain tunnel/handler/parent cancellation diagnostics when they indicate a genuine failure.
Describe planned post-start agent delivery as a normal strategy choice; report actual pre-start preparation/delivery failures with their cause and fallback.
Add regression coverage proving successful logs are clear and real failure diagnostics remain visible.
Keep runtime ownership, return values, cancellation, cleanup, delivery ordering, provider pins, and workspace configuration unchanged. Deliver the related fixes together in one PR.
Delivered in PR #1511, merged with all current-head CI and remote review gates passed.
Activity