← All features

Verified Setup & Project Profiles

Activate a folder with proof, then keep its retrieval intent portable

Most tools call a folder “indexed” the moment files land in a database. GNO does not: setup returns only after lexical search finds an exact result derived from your own corpus, so a green status means retrieval actually works. Repositories can then carry an explicit .gno/index.yml profile for collections, contexts, content types, models, and project-aware retrieval defaults, without ever putting GNO's database in source control.

Use cases
Fast first-run activation with a real retrieval proof
Repositories that need repeatable local knowledge configuration
Agents working across several projects in one GNO index

What it gives you

  • Exact corpus-derived lexical proof before setup succeeds
  • Independent resumable semantic preparation
  • Install-once connector activation for seven supported targets
  • Portable, source-controlled .gno/index.yml desired state
  • Read-only profile check, show, and diff before explicit apply
  • Create/update-only application that preserves unrelated index state
  • Small transparent project-affinity signal for trusted local CLI work
  • No implicit profile application or filesystem probing from remote hints

Try it yourself

Representative commands and entry points. Full reference lives in the documentation.

gno setup ~/notes --name notes
gno profile check
gno profile diff
gno setup . --apply-profile

Keep reading

Related features and docs.