Skip to main content
An Entity’s knowledge and journal are ordinary Markdown files with different roles. Knowledge holds reusable context; the journal records reflections over time.

​
Edit knowledge

This opens the Entity’s knowledge.md in your configured editor and creates the file if needed. Organize it with second-level headings:
The knowledge store can retrieve relevant sections into a turn. Keep sections focused and update facts when they change.

​
Let the Entity maintain sections

The update_knowledge tool supports add, update, and remove. For example, the Entity can add a section with:
The tool writes a backup before editing and refreshes the knowledge store. It refuses updates or removal of a [locked] section. That lock applies to this tool, not to an operator or process with direct filesystem access. Automatic context compaction can also extract durable facts into knowledge when compaction_flush_to_knowledge is enabled. This is selective retention; it does not preserve every detail of the original conversation.

​
Inspect the journal

The journal tool appends entries, while the operator can inspect the underlying file. In Telegram, /journal shows recent entries without asking the model to rewrite them. A journal may contain personal context. “Private” describes its intended audience, not an encryption guarantee.

​
Find and preserve the files

Without a configured workspace, these files normally live under the Entity’s state directory. NGRAM_EXECUTION_WORKSPACE_DIR can redirect them to persistent storage, and portable Entities use their runtime cache layout. Use uv run ngram status rook and the persistence guide to find the actual paths. Back up both files together with the structured memory store.