Skip to main content
The Search page is a chat-style interface for querying your knowledge graphs. When a conversation is empty, the page greets you with What are you looking for today?
Search consumes token credits under Cognee Cloud’s usage-based billing. If your workspace runs out of prepaid credits, the query is rejected and an insufficient-credits dialog explains the failure and links to Billing — see When credits run out.

​
Sending a query

  1. Type a natural language query in the search bar (placeholder Ask a question about your data…) and press Enter to send; use Shift+Enter for a newline.
  2. Results appear in the conversation area below.
Suggestion chips are shown when a conversation is empty:
  • “What are the main entities?”
  • “Summarize the uploaded documents”
  • “What relationships exist in the data?”
Click any chip to send it immediately. Past searches are loaded from the backend and shown in the history sidebar. History persists across sessions and is fetched via the GET /api/v1/search endpoint. Queries sent from this page are recall calls, and recall records the questions it answers, so your own UI searches appear in that history alongside searches made through the API — see Recall and search history.

​
Dataset

The active dataset is chosen with the dataset selector in the input area, at the right just above the search bar — not from the top bar, which carries only the workspace switcher and the page name. A query is always scoped to exactly one dataset: there is no All datasets option here, and if you have not picked one, the first dataset in the list is used. See Dataset selector. Every query searches the knowledge graph built from the documents you uploaded into that dataset. There is no memory scope to choose either: the former Company Brain / Agent Memory pills were removed, and the page no longer searches agent sessions. To look through what your connected agents stored, open Sessions instead.

​
Conversation history

The sidebar on the left lists past conversations grouped by age — Today, Yesterday, This week, This month, Older. Click any conversation to reopen it, use + to start a new one, or use the sidebar toggle to collapse and expand the history panel. Past searches are loaded from the backend via GET /api/v1/search. New conversations created during the current page session appear alongside that history, deduped by id, so a restored conversation you have continued is listed once. The sidebar shows a skeleton while history loads, rather than asserting there are no conversations before it knows. Each conversation is titled with the workspace’s own title for the session, which is computed from the full transcript — the detail endpoint returns only the last 20 turns, so on a long conversation the first visible question is not necessarily the one that was asked first. A conversation whose visible tail is blank still keeps its place in the list, and a single malformed row costs that one row rather than the whole page.
Conversations are backed by backend sessions whose ids are prefixed with search-ui-, so your history survives a page refresh. Legacy single-Q&A entries are read-only; continuing one forks it into a new session.

​
How search works

The UI search calls the POST /api/v1/recall endpoint with graph scope — a standard graph retrieval over the active dataset. For details on available search types and parameters, see Search Basics.
The Overview used to carry an inline search terminal. It no longer does — the redesigned Overview reports on your memory instead, and this page is where you query it.