← All features

Verified Answers

A cited answer from a local LLM, or an honest abstention

Type a question and GNO answers from your own documents, with citations that resolve to the source paragraph. Turn on verification and it compiles one closed Context Capsule, classifies every substantive claim as supported, contradicted, insufficient, or uncertain, and withholds the draft unless support reaches 100%. A refusal that names the failing claim beats a confident paragraph you have to fact-check by hand.

Use cases
Private local RAG over notes, docs, and code
Work where a wrong answer costs more than a slow one
Remote-GPU setups that still keep the corpus local
Teams that need cited answers bound to local evidence

What it gives you

  • Local models load on demand and retire after idle grace; first use and later reloads take longer than warm reuse
  • Answers come from your documents, not the open web
  • Citations link to the exact source paragraph
  • Verification binds each claim to an evidence ID, line range, and content hash
  • Supported, contradicted, insufficient, and uncertain verdicts stay explicit
  • Below full substantive-claim support, the draft is withheld and the gap is named
  • Verifier unavailability and capability degradation are reported, never silently downgraded
  • Across 22 paired fixture tasks, verification lost no answer accuracy and produced strictly fewer unsupported claims
  • Built-in local models need no cloud API or API key
  • Optional HTTP inference offloads specific model roles while the corpus stays local
  • Per-collection model overrides for prose versus code

Try it yourself

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

gno ask 'your question' --answer
gno ask 'your question' --verify --show-sources
gno models use balanced
gno models pull

Keep reading

Related features and docs.