fix(agent): route projectless build prompts - #121
Merged
Conversation
Use project absence, not the account's first-ever run, to identify new build chats. This keeps managed projects and previews deterministic for returning users and models.
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
1 participant
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
isFirstRunas the first run of a chat; it represents the user account’s first-ever agent runWhy
Production DeepSeek V4 QA after PR #120 exposed the semantic mismatch: workspace confinement worked, but a returning user’s new projectless build chat remained in general mode and could still omit the managed preview.
Verification
pnpm typecheckpnpm turbo lintpnpm turbo build --forceAfter merge and Cloudflare deployment, this will be re-tested through the production UI with DeepSeek V4.