Repository navigation
[Improve] Make setup conversational and agent-led - #2539
Merged
brunobergher merged 24 commits intoSep 14, 2026
Merged
Conversation
Contributor
|
No new code issues found. See task
Reviewed bc7fc4b |
roomote-roomote
Bot
requested review from
brunobergher,
daniel-lxs and
mrubens
as code owners
September 11, 2026 18:12
Contributor
Author
|
Fixed the duplicate starter-work launch and resolved the branch against current |
…y-2rv9qvia3cjxq' into improve/setup-integration-history-2rv9qvia3cjxq # Conflicts: # apps/web/src/trpc/commands/setup/setup-session.test.ts # packages/types/src/setup-new.test.ts # packages/types/src/setup-new.ts
…gration-history-2rv9qvia3cjxq
brunobergher
approved these changes
Sep 14, 2026
brunobergher
deleted the
improve/setup-integration-history-2rv9qvia3cjxq
branch
September 14, 2026 17:11
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
starter_selectionturn exclusively own selected starter-task launches so a ready sandbox cannot cause the capability-response turn to launch the same work again.develop.Why this change was made
Setup should adapt to what an administrator has already provided without coercive gates or repeated questions. Starter work also needs one durable launch owner so each selected task starts exactly once when compute is ready.
Impact
Administrators can connect or skip source control and integrations, start their own work, or select starter tasks without setup reopening skipped choices. When starter tasks are selected, setup waits for a usable sandbox and launches each selected task once; launch attempts can still complete setup even when an individual launch fails.