Seer not recognizing frontend code in monorepo without explicit prompting

Environment

SaaS (https://sentry.io/)

Steps to Reproduce

Opening on behalf of a customer (see shadow ticket)

Customer originally asked:

"I'm testing Seer and enjoying it but it seems to struggle to find the files in our monorepo. xyz-frontend project in sentry is linked to our github: ourorg/xyz monorepo, so is there a way to tell the agent that the frontend lives in /frontend directory in the monorepo? Are we missing some configuration?"

Customer had conversation with Seer about their monorepo. Monorepo was already linked to Sentry. Monorepo contains both FE + BE code.
Seer did not find realize that the monorepo contained the frontend, and instead instructed the user to link a frontend

Expected Result

Seer would detect that there was frontend code in the monorepo and use that.

Actual Result

(will link Sentry conversation in shadow ticket)

Seer: "The frontend code isn't in the searchable repo: how can I add this to be searchable..."

User: "The frontend code isn't in the searchable repo: how can I add this to be searchable"

Seer: "Explorer Main Step
7.9s
Called tool
Resolve Sentry Nav
You can connect your company/myrepo-frontend GitHub repo to Sentry so it's linked to the myrepo-frontend project. Navigate to:
Settings → Integrations → GitHub
From there, add the company/myrepo-frontend repository. Once connected, Sentry will:
Index the code so Autofix and Seer can search it (which is what we needed above)
Enable stack trace linking — file paths in errors become clickable links to the exact line in GitHub
Enable suspect commits — Sentry surfaces which commits likely introduced a regression
It looks like currently only company/myrepo is connected to the myrepo-frontend project, but the frontend source lives in a separate repo. Adding that repo via the GitHub integration is all that's needed.

User: "company/myrepo is the right repo, the frontend lives in /frontend inside"

Seer: "Ah, that explains why the search came up empty — I was searching without a path scope. The repo is connected, the frontend code just lives under /frontend. Let me retry:"

[only then was Seer able to find the code]

Product Area

Other

Link

No response

DSN

No response

Version

No response

Start with the Seer conversation in the shadow ticket and the monorepo search/discovery entry point; confirm how the linked repository and /frontend path are interpreted. Done means Seer recognizes frontend code under /frontend without explicit prompting and no longer tells the user to link a separate repository.