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
The UX slice carved out of Δ10 (#34) — the estimator/backend stays on #34 (plumbing, @Rchari1). Routing decision (cloud-solve-service spec, Locked decisions): routing is per-solve, explicit — the agent may suggest offload (estimator's sizeClass vs local RAM), the researcher confirms. No auto-classifier.
Where the executor: remote choice sits in the solve-assembly flow (the SolveSpec carries it).
Surface the sizeClass / estimate at the decision point so the choice is informed.
Ties to the freezes
Freeze 1 (S12): downstream is executor-agnostic — this UI only sets executor: remote on the SolveSpec upstream; it does NOT branch the inspector/runs path.
The UX slice carved out of Δ10 (#34) — the estimator/backend stays on #34 (plumbing, @Rchari1). Routing decision (cloud-solve-service spec, Locked decisions): routing is per-solve, explicit — the agent may suggest offload (estimator's sizeClass vs local RAM), the researcher confirms. No auto-classifier.
What (UI)
executor: remotechoice sits in the solve-assembly flow (the SolveSpec carries it).Ties to the freezes
executor: remoteon the SolveSpec upstream; it does NOT branch the inspector/runs path.Feedback question
Is agent-suggest + user-confirm the right friction, or do power users want a sticky "always cloud" default?
Depends on: #34 (the estimator provides the suggestion signal). Kate owns the UI; #34 owns the estimate.