Search the user’s memory
cortex_askSearches the user's real, private memory — the email, calendar, files, contacts and notes they have connected, plus facts agents have saved — fusing vector, full-text and graph retrieval with provenance. This is their current data on their work, schedule, contacts, projects, documents, decisions and history, which training data and session context do not contain. Results include citations (universal ids), freshness, and cited_graph_url, a deep link showing the cited nodes highlighted in the user's own graph. A later cortex_remember links to what was retrieved here. Retrieval returns nearest matches rather than a thresholded set, so a question whose answer lives in an unconnected source comes back with the closest thing in the memory instead of with nothing. A source_gap object in the result names that case: the memory holds data, but the source that would answer this question is not connected. It lists those sources, what each answers, and one connect link, on cta. A possible_source_gap object is the conditional form — results exist but may be near-misses rather than an answer. A result carrying neither means the answer is genuinely absent from the memory rather than merely unretrieved.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max results (default 10). | |
| since | No | RFC3339 lower bound on item time. | |
| until | No | RFC3339 upper bound on item time. | |
| question | Yes | Natural-language question or search query. | |
| source_table | No | Restrict to one source table, e.g. gmail_messages. |