← All features

Collections

Group sources by directory, glob, context, and per-collection egress policy

Group documents by source directory with glob patterns, includes, and excludes. Add contexts and project-aware affinity, govern each collection with a fail-closed local, LAN, or remote egress boundary, and optionally set source availability for physically tested macOS File Provider layouts.

Use cases
Keeping research and client notes separately searchable
Syncing a team wiki from git
Per-collection model overrides for code vs prose
Indexing a broad Google Drive or iCloud tree without hydrating cloud-only placeholders

What it gives you

  • Multiple document sources
  • Glob patterns for filtering
  • Include and exclude rules
  • Per-collection search
  • Collection contexts for relevance
  • Portable project profiles and transparent local project affinity
  • Per-collection local_only, lan, or remote egress policy
  • Opt-in sourceAvailability local for tested Google Drive/iCloud Drive configurations and both validated immediate OneDrive SharePoint library roots; distinct from egress
  • Measured hierarchical local scan overhead: +1.1841% median on the controlled 5,000-file all-local corpus (fixture-scoped)
  • Update commands for git sync

Try it yourself

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

gno collection add ~/notes --name notes
gno collection list
gno search 'term' -c notes
gno collection policy get notes

Keep reading

Related features and docs.