Skip to content

fix: clarify successful MicroSandbox startup diagnostics #1510

Closed

Description

@skevetter

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions