Skip to main content

Sessions as context

Knox: View Memory → Sessions lists Memory Brain’s session rows (not the same UI as Knox: View History, which is the chat overlay).

Sessions tab with Use as context and Delete session on a past chat
Sessions tab: Use as context pins that summary into later injects. It does not create a second store.

Two actions matter:

ActionWhat it does
Use as contextPins that session’s summary and top-ranked rows into the next inject. No new database, no copy of the whole transcript into sqlite.
DeleteRemoves that session row from Brain. Chat files under ~/.knoxcoder/sessions/ are separate; History delete is the overlay.

Use as context is for “keep last week’s auth-refactor decisions in play” without pasting the log. It lasts for the inject cycle you just requested, not forever — pin individual memories if you want a durable fact.

History overlay vs Sessions tab​

SurfaceCommandFor
HistoryKnox: View HistoryRename, delete, reopen chats; Use as context also exists there for the live composer
Memory → SessionsKnox: View MemoryBrain’s session index: delete, Use as context into memory inject

Neither uploads. /share writes a local Markdown file and a knoxcoder:// URI — Slash commands.

Next​

Memory Brain · Memories tab · Chat UI