​

Full-Text Search

​

How it works

​

What gets indexed

​

Ranking

• Term frequency (how often the term appears in the session)
• Inverse document frequency (terms that are rare across all sessions score higher)
• Position (terms appearing earlier in the document score slightly higher)

​

Search syntax

​

Single term

authentication

​

Multiple terms

react hooks useState

​

Prefix matching

refact

​

Phrase search

​

Using full-text search in the dashboard

1. Type your query in the search box.
2. Results update in real time as you type.
3. Results are sorted by relevance score.

​

Using full-text search via API

curl -X POST "https://polished-penguin-622.convex.site/search" \
  -H "Authorization: Bearer osk_your_key" \
  -H "Content-Type: application/json" \
  -d '{
    "query": "authentication middleware express",
    "type": "fulltext",
    "limit": 10
  }'

{
  "results": [
    {
      "sessionId": "j57a...",
      "title": "Express Auth Middleware Setup",
      "snippet": "...setting up authentication middleware for the Express app...",
      "score": 0.95
    },
    {
      "sessionId": "k82b...",
      "title": "Add JWT middleware",
      "snippet": "...authentication layer using JSON web tokens...",
      "score": 0.78
    }
  ]
}

​

Tips for better results

• Use specific terms. “convex mutation upsert” will return more targeted results than “database update”.
• Include technical identifiers. Function names, library names, error codes, and file paths make great search terms.
• Combine with source filters. If you know which tool you used, filter by source to narrow the results.
• Use fewer terms for broader results. Start with one or two key terms and add more if you get too many results.

​

When to use full-text vs semantic