Code Indexing : how to block some folders

[jboelyIWE]

Hi, We have been using KiloCode quite a bit and are especially interested in the Code Indexing feature.

The first issue / question : Does a file that prevents indexing of certain folders/files exist ? I know the files and folders specified in .gitignore are not indexed, but we have a situation where we have a folder that should not be indexed but should not be in the .gitignore either. Is there something like a .kiloignore to prevent indexing on those files?

The second issue is we would like to be able to choose (or not) to automatically index the codebase on startup to not have very large indexing when unnecessary and only index when we want it.
As an example, I opened a repo I just cloned to look at some things not using Kilocode, but it still indexed 80k+ points into a collection I'll never use.

[jboelyIWE]

Realized just now that in fact the .kilocodeignore file works... this is very poorly explained; I only knew because of the option in context settings.

[iRonin]

Does KiloCode respect .gitignore or the entries should be duplicated?

[AlexKovynev]

@iRonin should be duplicated for indexing

[iRonin]

Thanks. Does .kilocodeignore also restricts file access? Cursor had .cursorignore and .cursorignoreindexing - I don't want some temporairly created files being indexed but I want them accessible by AI.