Reference
The local browser workspace started by gno serve: search, browse, graph, edit, capture, API, and live indexing.
gno serve starts GNO’s local browser workspace and REST API. It is the easiest surface for people who do not want to live in a terminal: add folders, watch indexing progress, search, ask, browse notes, inspect the knowledge graph, and safely edit Markdown. Everything still runs on your machine.
/api/* for scripts and internal tools.gno serve # foreground, http://localhost:3000
gno serve --port 8080 # custom port
gno serve --index research # named index
gno serve --detach # background; prints pid + url
gno serve --status --json # machine-readable status
gno serve --stop # graceful stop--port changes the browser/API port.--detach, --status, --stop, --pid-file, and --log-file use the same lifecycle contract as gno daemon.gno daemon instead when you want background indexing without the browser or API server.The Web UI exposes the same retrieval controls as the CLI. Use exact search for names and phrases, vector search for conceptual matches, hybrid for normal research, and the Ask page when you want a grounded answer with citations.
term: "spaced repetition"
intent: personal knowledge base learning loop
hyde: A note explaining how repeated review turns saved notes into long-term memory.Markdown and plain text stay editable. Converted binaries (PDF, DOCX, XLSX, PPTX) stay read-only. If you want to work on the content of a converted document, use Create editable copy in the doc view — it spawns a new markdown note with source provenance intact.