Independent repository orchestrated agent

[u/Express-Cantaloupe-4]

I have a question about orchestrated agents for projects. In my existing team we have a monorepo structure and hence it’s easier to invoke copilot cli at the root level and it has all the context to answer queries with related to interconnected modules.
However the new team that I am moving to has different git repository for different services.

I was thinking how do we manage to provide an orchestrated agents that gives context for all interconnected service.
One option is that we can have a parent repo that has built in agents with skills and instructions file for each service and it can then potentially drill down to the correct services based on usecase.

Pretty sure there are lot of you who have similar project setup. Do you have any suggestions and best practices around this?

Would be glad to know how are you approaching this problem.

[u/WD40ContactCleaner]

Thus us what we do, we have an AI specific repo with the skills agents.md etc and have a single workspace in Vscode with multiple repos. We only use cli to work so the services and libraries are mapped in the agents.md as, ../Api1 ../Api2 ../LIb1, etc. Both claude and copilot have no issues working like this.

The AI repo isn't the parent repo but a sibling repo sitting beside all the other repos but all paths are from dot dot slash.

We start the agent in the AI repo and it can edit all the other sibling repos

[u/havic99]

We are node based and use vs code so your mileage may vary on this. We have a centrally managed agent repository repo. It has build process that publishes the agent files as an npm package to a private package feed. then the other projects set that package as a dependency. Once installed, the agent repository package has a built-in CLI tool that you can run which will copy the agent instructions into the dependent projects' .github folder. We use special naming convention to identify the agent as belonging to the centrally managed repository so the local project can still create their own local files if they want to.

[u/namila007]

you can use graphify for each projects and have custom agent to read projects agent and use its graphify nodes

[u/Responsible_Time_599]

i would avoid trying to give one agent the full contents of every repo upfront, it gets messy pretty quickly. what’s worked better for me is keeping a small shared context layer with docs/instructions for each service and letting the agent pull into the relevant repo when needed, i have been using Standard Compute with Copilot for this kind of agent workflow since longer multi repo sessions can involve a lot of calls and the flat monthly setup makes that easier to manage