fix(agent prompt): modification to subdomain caching delays in the agent prompt - #6796
Conversation
N43527
changed the title
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 40a9e4c. Configure here.
| - If I don't: ask me for my first name, last name, company, and email if I haven't given them already—never invent these. Run `mint signup --firstName [firstName] --lastName [lastName] --company [company] --email [email]` as a background task since it blocks until I click a verification link that can take several minutes. | ||
| 5. Needs me: I'll check my email and click the verification link. That opens a browser tab that automatically finishes the rest of account creation/logging in. I must approve the CLI, then connect a GitHub repository or let Mintlify host one. Tell me clearly this step is mine, then wait for it before continuing. | ||
| 6. Run `mint status` again to confirm an organization and subdomain now exist. Provisioning can lag a moment after onboarding finishes — if no subdomain appears yet, wait about 10 seconds and retry a few times before concluding something is wrong. | ||
| 6. Run `mint status` again to confirm an organization and subdomain now exist. The subdomain isn't provisioned until I select or connect a repository during the step 5 browser flow — so if `mint status` shows my organization but no subdomain yet, that almost always means I haven't finished the repo step, not that anything is broken. Don't treat it as an error or poll blindly: wait until I confirm I've completed onboarding, then re-run `mint status`. Provisioning can still lag a few seconds after that, so retry a few times before concluding something is wrong. |
There was a problem hiding this comment.
Resume skip bypasses subdomain wait
Medium Severity
Step 6 now treats org-without-subdomain as unfinished onboarding and tells the agent to wait, but step 3 still skips to step 7 whenever an organization exists. On resume mid-signup—an explicit prompt scenario—the agent bypasses that wait and asks for a repo URL before a project exists.
Additional Locations (1)
Reviewed by Cursor Bugbot for commit 40a9e4c. Configure here.
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
3 participants
Documentation changes
Brief description of what's being updated
Making a change to mint signup to invalidate subdomain cached value since it's stale.
Need the AI to know that it might not see a cached value for a bit, but that it should retry a bit until user is done with signup.
Closes
For Reviewers
When reviewing documentation PRs, please consider:
✅ Technical accuracy
✅ Clarity and completeness
✅ User experience
Note
Low Risk
Documentation-only change to agent setup instructions; no runtime or product behavior is modified.
Overview
Step 6 of the setup-agent prompt now explains that a missing subdomain in
mint statususually means the user has not finished connecting a repo in the browser onboarding flow—not a CLI failure.Agents are told not to treat that as an error or poll blindly; they should wait for the user to confirm onboarding is done, then re-run
mint statusand retry briefly for normal provisioning lag.Reviewed by Cursor Bugbot for commit 40a9e4c. Bugbot is set up for automated code reviews on this repo. Configure here.