Rethinking Monorepos in the Age of Agents

i have a parent repo that has git submodules for each area of my app (backend, frontend, docs, etc).

i have all the benefits of having multiple repos eg different c/i pipelines, but the agent sees it as a monorepo and so can I if i open the parent repo in my ide.