Skip to content

feat(cua-driver): integrate typed Driver access with Fleet Sandbox - #3654

Merged
f-trycua merged 38 commits into
mainfrom
feat/sandbox-typed-driver-20260907
Sep 9, 2026
Merged

feat(cua-driver): integrate typed Driver access with Fleet Sandbox#3654
f-trycua merged 38 commits into
mainfrom
feat/sandbox-typed-driver-20260907

Conversation

@f-trycua

@f-trycua f-trycua commented Sep 8, 2026

Copy link
Copy Markdown
Collaborator

Scope

Refs #2512, #3647, #3650, #3651, and #3653.

Adds sandbox.driver.connect(service="driver"), returning the canonical generated CuaDriver with typed inputs and results. Existing computer-server, shell, files, claims, and pool APIs remain unchanged. Fleet transport only: no host-local fallback, new credentials, or public endpoint.

This landing includes the mandatory lifecycle/deadline correction from #3655 and the trusted-launcher mode correction from #3664, already merged into this feature branch. Do not land the original accessor without those corrections.

Behavior

  • Reuse existing authenticated, namespace-authorized named-service routing.
  • Pin connection identity/generation and validate response identity, version, completion, and size. These labels are not credentials.
  • Invalidate uncertain or stale connections without automatic reconnect or replay.
  • Bound session cleanup before Sandbox disconnect, release, and destroy. Closing Driver does not delete the computer or stop the shared daemon.
  • Let the trusted launcher select the daemon's acknowledged permission mode. A remote caller cannot select authority or rebind the connection.
  • Require candidate-native bridge tests in contract CI; a missing native bridge fails instead of skipping.

Validation

The assembled candidate 43a332a66d8379b4fb9330c6a96f0654cc4afea1 includes this complete unit, Windows recovery #3109, Windows classification #3671, and verification coverage #3672:

These are cumulative candidate results, not a claim that each incremental PR contains all follow-ons. Final merge guards separately verify current-head checks, review threads, final scope, and source equivalence after ancestor updates.

Limits and rollback

The private carrier remains opt-in. No Fleet image service wiring, package publication, image publication, deployment, or installed-tool update is included. Published Fleet images are not claimed to support this route.

Live typed verify_state remains unqualified; #3672 supplies deterministic synthetic native-bridge coverage, not live accessibility proof. The broader RFC remains in review; #3647 records the accepted narrow implementation contract.

Before publication, keep the carrier disabled and use existing constructors/computer-server. Any code rollback uses reviewed revert PRs, preserving history and tests.

@codecov-commenter

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

f-trycua and others added 5 commits September 8, 2026 19:52
* fix(sandbox): bound typed Driver lifecycle and request deadlines

* fix(cua-driver): allow explicit unrestricted envelope sessions

* docs(sandbox): clarify launcher-selected Driver permissions

---------

Co-authored-by: Francesco Bonacci <195596869+f-trycua@users.noreply.github.com>
@f-trycua f-trycua changed the title feat(sandbox): add canonical typed Driver access over Fleet services feat(cua-driver): integrate typed Driver access with Fleet Sandbox Sep 9, 2026
@f-trycua
f-trycua marked this pull request as ready for review September 9, 2026 03:09
@f-trycua
f-trycua changed the base branch from feat/driver-private-http-20260907 to main September 9, 2026 03:09
@f-trycua
f-trycua merged commit c9c29dc into main Sep 9, 2026
38 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants