Work across repositories

Browse indexed repositories

The Files view lists the repositories CodeZero has indexed for your organisation. A repository checked out on your machine expands to its real working tree. A repository that is not checked out can still expand to its indexed file list, and those files can be opened from the index.

Understand local versus indexed context

When a local checkout exists, CodeZero prefers the working tree because it includes the current branch and uncommitted changes. When no checkout exists, CodeZero uses the organisation index for read-only context.

Keep repository conversations separate

You can work across several repositories from the same VS Code window. CodeZero keeps each repository's chat and workstream separate, so a conversation about one service does not inherit the state of another.

Organisation-wide indexed context is still available inside each conversation, which is what lets a question in one repository be answered with evidence from another.

Plan a cross-repository change

A plan can name more than one repository. CodeZero keeps those repositories in scope for the agent and makes the dependency visible in Tasks.

Clone a repository when editing is required

An indexed repository can be read without being checked out, but it cannot be edited until a local checkout exists. When an approved plan requires a missing repository, Tasks identifies it and offers Clone. You choose where the checkout should be created.

This keeps cross-repository understanding available early while keeping actual writes tied to a real working tree on your machine.