Using Auryn
Working Across Many Repositories with Auryn
Ingest several repositories under one graph name so calls from one repository into another connect, and your coding agent can follow a request across the whole system.
By default every repository gets its own graph. When a system spans several repositories — a web front end, an API, a database — ingest them under one name. Calls from one repository into another connect, so your agent can follow a request across the whole system.
Order doesn’t matter. A call into a repository that isn’t ingested yet is kept as a placeholder and connects itself once that repository arrives.
Was this page helpful?