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
{{ message }}
Repository navigation
Admin clear: stale repository_clone_failed on yieldhuntereth-yieldsentineleth (Source fixed to yieldhunter-connect) #430
Please clear / re-scan the Cursor Directory listing after a Source URL fix. Security agent still shows a stalerepository_clone_failed against a repo that never existed.
After edit+resubmit, the security banner still cites the oldagentsherpa/yieldhunter 404 and keeps the listing unpublished.
Ask
Please clear the stale flag / re-run the security scan against agentsherpa/yieldhunter-connect so the listing can become publishable (or tell us if another action is required).
Notes
No payment involved
Thin public connect repo only (intentional); private agent code stays private
Search on cursor.directory for yieldhunter / yieldsentinel still returns no hits (checked 8 Sep). Could you trigger a search reindex for this listing if that’s helpful?
No second listing planned — just this one quiet ping. Thanks.
Hey @agentsherpa, thanks for the clear request, and apologies for the wait. A repository_clone_failed flag that predates a Source URL fix doesn't clear on its own: the security agent doesn't re-scan on edit, and there's no Rescan control on the owner page, so it has to be re-run by the directory team. I've passed yieldhuntereth-yieldsentineleth along with the corrected source so they can clear it. I'll update here when it moves.
Activity
agentsherpa commentedon Sep 8, 2026
Follow-up after the security CLEAR:
Search on cursor.directory for
yieldhunter/yieldsentinelstill returns no hits (checked 8 Sep). Could you trigger a search reindex for this listing if that’s helpful?No second listing planned — just this one quiet ping. Thanks.
deanrie commentedon Oct 5, 2026
Hey @agentsherpa, thanks for the clear request, and apologies for the wait. A
repository_clone_failedflag that predates a Source URL fix doesn't clear on its own: the security agent doesn't re-scan on edit, and there's no Rescan control on the owner page, so it has to be re-run by the directory team. I've passedyieldhuntereth-yieldsentinelethalong with the corrected source so they can clear it. I'll update here when it moves.