concepts
Search
Full-text search across files, documentation, and projects via Meilisearch.
Glyph uses Meilisearch for instant full-text search across everything in a workspace.
What's indexed
| Index | Contents |
|---|---|
| Projects | name, description, workspace |
| Files | path, language, content (text files only) |
| Documentation | content of every (file, commit) doc entry |
Binary files (images, PDFs, executables) are not indexed. Their paths are searchable, but their contents aren't.
When indexing happens
- Project import - initial indexing of all files
- Project sync - re-indexes the file tree at the new HEAD
- Documentation save - the saved doc is indexed immediately
There's no manual "rebuild index" button in the UI - sync triggers it. To force a rebuild, use the API or restart the backend (which currently does NOT rebuild - see Search Engine for manual rebuild).
Using search
Click the search bar in the top navigation (or press Cmd/Ctrl+K) to open global search.
Results are grouped by type:
- Projects - matching project name or description
- Files - matching file path or content
- Documentation - matching doc content, with the file and commit context
Click a result to jump directly to it.
📸 Screenshot
Global search modal with grouped results
Scoping
By default, search is scoped to the current workspace. You won't see results from other workspaces - even if you're a member of them.
Within a workspace, results span all projects you have access to.
Search syntax
Meilisearch supports:
- Plain text - typo-tolerant, ranks by relevance
"exact phrase"- quoted strings match exactly-excluded- exclude a term
There is no support for regex or boolean operators (AND, OR) - those are not Meilisearch features.
Performance
Meilisearch is designed for instant search even on large datasets. A workspace with hundreds of projects and thousands of files returns results in under 50 ms on modest hardware.
The Docker container uses a few hundred MB of RAM at most. Index data is persisted to volumes/meilisearch/.
Privacy
The Meilisearch instance is private to your Glyph deployment - accessible only from the backend container, not exposed to the internet. The master key (MEILISEARCH_KEY) protects the API even if the port were exposed.
See Search Engine for configuration details.