gezel Gezel Help

Memory, documents, and the shared library

Gezel memory

Each crew member keeps a diary. As you work together they save notes — decisions you made, preferences you expressed, lessons learned — into daily memory files they can search later. Ask your copywriter for "that tagline direction we agreed on in March" and they can actually look it up.

A note belongs to one of three places:

  • A crew member's own — how they do their work well. Your reviewer's notes about code style don't leak into your researcher's notes about sources.

  • The project's — facts and decisions shared by everyone working on that project.

  • Yours — what Gezel has learned about you: your name, your preferences, what you're working toward. Everyone on the crew reads these, so you don't have to tell each one again.

Gezel keeps the most recent things it knows about you in front of it all the time, so it doesn't have to ask again. Before answering a message, it also looks for older notes that bear on it, preferring ones from the project at hand. This works on phones too, and keeps working while the search model is still loading.

Everything is editable. Settings → About you shows what Gezel knows about you; correct or remove anything there. Each crew member's Memories tab holds their own notes and their lessons — the short list of habits they carry into every conversation. Lines you put under a ## Pinned heading in the lessons are kept exactly as you wrote them; the rest is refreshed as they learn.

The document library

Documents are shared knowledge — the things everyone on the crew should know. Your company boilerplate, your house style guide, the family holiday schedule. The library has two levels:

  • The shared library — available in every project.

  • Project documents — the About and Mission Objectives of each project, plus anything else scoped to just that work.

Gezel can read and (where you allow it) write documents itself, so the library grows as the work goes on.

Reference catalogs

You can also install knowledge catalogs: portable .gezk files containing reference documents and prepared search indexes. Gezel can search and cite them alongside project files and memories. The built-in Help uses this same format. Installing a catalog adds reference material; it does not train your chat model.

For the technical details, see How knowledge works in Gezel. To make or install one, see Working with knowledge catalogs.

The history log

Gezel keeps an audit log of meaningful events: who was added to the crew, when a project's mission changed, which tools ran. The History tab lets you filter and search it — and Gezel can search it too, which means "did anyone change the mission this week?" is a question it can answer truthfully rather than guess at.

Everything is a file

Memories are Markdown files, your library keeps its original documents, and the history log is a file. Reference catalogs carry their documents and indexes in portable .gezk archives built from SQLite and other open formats. If you want to inspect what Gezel knows, the Where files live and How knowledge works articles map the source files and search databases.

Watch this article as a slideshow · Read it as markdown, for AI agents