Knowledge and memory
Knowledge holds the material you deliberately save. Memory holds useful facts, preferences, and lessons Gideon recalls between conversations. Use each for the job it does best.
Build your Knowledge library
Add notes, documents, bookmarks, or supported media through Knowledge. Give items recognizable names. Allow processing to finish, then ask a question you can verify against the source.
Search can combine keywords, relationships, and semantic matches when embeddings are available. If a result is missing, try exact terms from the document and check whether ingestion completed.
Keep project context clear
A project can show its own knowledge alongside items shared from other projects. Check sharing choices before relying on a project boundary. Saving an item into a project does not mean every other kind of memory has the same boundary.
Tell Gideon what to remember
Remember that I prefer short decision memos with the recommendation first, followed by evidence and open questions. Tell me what you saved.
Review saved information and correct stale facts. A remembered preference should improve future work, not silently replace the evidence for a current task.
Choose a privacy mode
A temporary conversation suppresses memory reads and writes. Incognito suppresses memory writes but can still read existing memory. Neither name means a connected service or model provider receives no request data.
For a reliable answer, ask Gideon to cite the knowledge item it used and distinguish source content from its own inference.