Working across repositories

Most AI coding tools only see the one repository in front of them. cix can index several, so your assistant understands a system that spans more than one codebase — a web app, its API, and a shared library, for example.

Connecting more repositories

Each repository is connected the same way as the first: grant the cix GitHub App access, enable it, and run cix init in its directory. Once connected, it has its own index in your account.

Shared GitHub repos are not automatically shared cix indexes. Each cix user must index the repo once under their own account until Team index ships — granting someone GitHub access does not make the repo appear in their cix account.

Why it helps

When the pieces of a system live in different repositories, a change in one can ripple into another. An assistant that can query each index reasons about those relationships instead of guessing at the boundary — which makes large systems easier to navigate and safer to change.

Tips

• Connect the repositories that actually move together. There is little value in indexing a repo you never touch alongside the others.
• Keep each one fresh — see Keep your index fresh.
• Your number of connected repositories may be capped by your plan; see Pricing.