Getting Started

Configuration

Configure GNO via index.yml, manage collections, and pick the right model preset.

GNO is driven by a YAML config file and a set of CLI verbs. Most users never touch the file directly — they manage collections and presets via the CLI or the Web UI. But when you need it, here’s where everything lives.

Config file location

Run gno doctor to see the resolved paths for your machine.

Collections

Each collection is a named source of documents. Collections have their own include/exclude rules and can optionally override model presets.

# Add a collection
gno collection add ~/notes --name notes

# Add with a glob pattern
gno collection add ~/code --name code --pattern "**/*.{ts,md}"

# List collections
gno collection list

# Remove a collection
gno collection remove notes

Exclusions

Add an exclude array to a collection to skip files and directories:

collections:
  notes:
    path: ~/notes
    exclude:
      - node_modules
      - .git
      - "**/*.tmp"

Model presets

GNO ships four built-in presets. Switch with one command; the first pull downloads the model files and caches them locally.

gno models use balanced
gno models pull
gno models list

Per-collection model overrides

Override embed, rerank, or answer models for a single collection — useful when your code collection wants a code-specific embedding while your prose collection sticks with the general-purpose model.

collections:
  code:
    path: ~/code
    models:
      embed: nomic-ai/nomic-embed-code-v1.5

Remote model servers

Point GNO at an OpenAI-compatible server (Ollama, LM Studio, vLLM) running on another machine on your LAN.

models:
  answer:
    uri: http://localhost:11434/v1#llama3.1:8b