Hey, thanks for the detailed report. This isn’t a bug, it’s a mismatch with what repositoryDependencies actually does.
repositoryDependencies does not clone extra repos. It only expands the GitHub token scope that gets passed into the environment so your own install/start scripts (or git submodules) can clone what they need. There is no automatic checkout of sibling repos from it, so you only see the primary repo. That’s expected behavior, and the same topic was covered here: Using cloud agents with environment.json
The doc line “Cursor clones each selected repo” refers to the multi-repo environment flow, when you select multiple repos while setting up the environment (that’s what you have working as your “Personal” env). That feature is what clones all selected repos as siblings, not repositoryDependencies.
Two options for your case:
- Keep the multi-repo environment (your working “Personal” setup) if you need automatic checkout of all 5 repos.
- Keep using
environment.json, but clone the dependent repos yourself in the install script using the token. Also:- Entries must be
github.com/org/repo, notorg/repo. The bare format without a host gets filtered out and won’t be added to the token scope. - Entries must be on the same git provider and host as the primary repo.
- Entries must be
Example:
{
"install": "git clone https://github.com/humblFINANCE/humblDATA.git ../humblDATA && ...",
"repositoryDependencies": ["github.com/humblFINANCE/humblDATA"]
}
On not being able to set up multi-repo checkout fully via a committed environment.json without the dashboard flow, fair point. I’ll pass it along as a request. I can’t promise an ETA. Let me know if anything doesn’t work with the install script.