cix init
Links the repository in your current directory to its cix cloud project, so your assistant's queries resolve against the right index. Run it once per project, from the repository root.
cd my-project
cix initThe repository must be a Git repository. It does not have to be connected to
GitHub — if it isn't, cix init offers the private-index path instead. See
How cix gets your code.
Re-running cix init is safe — it re-checks the connection without harming
existing state.
Flags
| Flag | What it does |
|---|---|
--client CLIENTS | Which assistants to generate project files for — claude, codex, gemini, cursor, or all. Defaults to claude. |
--yes | Pre-approve enabling indexing for this repo, skipping the confirm prompt. Only affects that step; other blockers still stop init. |
--skip-audit | Skip the convention audit and welcome banner |
--no-mcp | Don't write a project-scoped MCP entry for this repo |
--dry-run | Validate everything and exit without registering, indexing, or writing files |
--disable | Turn indexing off for this repo |
What it tells you
cix init reports which of the intake paths applies to this repository, which
is usually the fastest way to find out where you stand:
- The repo is already enabled, and init proceeds.
- The repo is covered by an owner's index and your verified collaborator access — nothing for you to index or push.
- The repo isn't reachable through a cix App installation, in which case init
points at
cix index --pushto index it privately instead.
If a blocker stops it, no changes are made — fix the blocker and re-run.
Turning indexing off
$ cix init --disableFlips this repo off. It makes no other changes and does not delete what was
already indexed; re-run cix init to turn it back on.
Related
- Verify the result with cix doctor.
- Full walkthrough: Initialize a repository.
- Troubleshooting: Repository not enabled.