Common Scenarios
- Frontend/Backend Split: Starting in a
backendrepo but needing access to UI code in afrontendrepo - Microservices: Working across multiple service repositories
- Shared Libraries: Accessing common utilities or components from separate repositories
Methods for Cloning Additional Repos
1. Repository Configuration Files
You can include cloning instructions in your repository’s configuration files:repo.md: Add instructions for OpenHands to clone related repositoriesagents.md: Include repository setup as part of agent initialization
repo.md:
2. Ad-hoc Prompting
During a conversation, you can directly instruct OpenHands to clone additional repositories: Example prompts:- “Please clone our frontend repository from
https://github.com/our-org/frontend-repo.gitso you can see the UI components that interact with this API.” - “Clone the shared utilities repo at
https://github.com/our-org/utils.gitinto a../utilsdirectory so you can reference the helper functions.” - “I need you to access our documentation repo. Please clone
https://github.com/our-org/docs.gitto understand the API specifications.”
Best Practices for Multi-Repo Workflows
- Specify clone location: Use relative paths like
../repo-nameto keep repositories organized - Provide context: Explain why the additional repository is needed
- Use your Git token: OpenHands will automatically use your configured Git provider token for authentication
- Be explicit about relationships: Describe how the repositories relate to each other

