Disable harness selector for local -> cloud handoff#10183
Conversation
|
Warning This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
This stack of pull requests is managed by Graphite. Learn more about stacking. |
7acb831 to
caf002d
Compare
240b220 to
7c5d372
Compare
|
I'm starting a first review of this pull request. You can view the conversation on Warp. I completed the review and no human review was requested for this pull request. Comment Powered by Oz |
There was a problem hiding this comment.
Overview
This PR locks the ambient agent harness selector to Warp/Oz during local-to-cloud handoff by deriving the effective selected harness from handoff state, disabling the selector UI, and ensuring spawned snapshots omit third-party harness overrides while locked.
Concerns
- None.
Verdict
Found: 0 critical, 0 important, 0 suggestions
Approve
Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).
Powered by Oz
7c5d372 to
972c4a1
Compare
caf002d to
6afb6ae
Compare
6afb6ae to
df06af3
Compare
972c4a1 to
3b4276a
Compare

Description
For local -> cloud handoff, we should disable the harness selector (as you can't go from a local warp conversation to a cloud claude conversation, using the same conversation).
This PR just locks the selector to Warp, but if/when we implement local->cloud for non-warp-harnesses we'll have to make the code respect the harness that's kicking off the cloud run.
Screenshots / Videos
https://www.loom.com/share/845bedb3e7e040dca0bb1413f8364b45
Agent Mode