Repository navigation
v315: Let Scout identify the site and wait for its brief - #209
Merged
Merged
Conversation
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.
Reviews started from a product name or several URLs could skip the startup brief, then continue while background research updated the site's metadata later. Remove URL extraction at startup: Scout identifies the main product with
set_review_site, and both engines keep that call pending until the existing shared research finishes. The agent receives its private brief path or the actual research error before continuing.Keep the six-minute research limit and show the existing preparation timer while the tool waits. Cached briefs, shared-job billing, Stop, and historical task snapshots retain their behavior. Reject a brief for the wrong hostname after an owner changes the review's site. No schema changes or additional queues.
Validation:
pnpm run check: 1,665 tests passed; formatting, lint and all TypeScript checks passed.pnpm run buildpassed.checkvist.comwithout a URL. Chrome showed the preparation timer and preserved it through refresh. Firecrawl completed after about six minutes; the tool returned the saved brief path, and Scout successfully read it withbashbefore continuing. No repeated model generations occurred during the wait.Deployment: let all existing initial-start workflows finish before deploying, including Play tasks. Removing their old startup steps would otherwise cause a workflow journal mismatch. Do not merge while those tasks are running.