Separate sessions, transcripts, and durable memory

Verifiedon 2026-07-302026.7.1-2

Three things that should not be collapsed

A session selects a conversation context and lifecycle. A transcript is the recorded history for that session. Memory is durable Markdown in the agent workspace, with different files serving profile, long-term, and daily context. They interact, but they are not interchangeable—and none alone is a multi-tenant authorization system.

By default, direct messages can share a main session. That is convenient for a single trusted operator and unsafe as a multi-person assumption: people who can reach one shared session can inherit its context. Group chats and rooms have separate routing defaults; private recall and tool visibility have their own rules.

Lab: choose scope from a contact matrix

Classify these contacts: your own Telegram DM, your own WebChat thread, a team support room, and a contractor DM. For each, answer:

For the contractor case, the safe answer is not “use a carefully named session.” Use a separate trust boundary if they are mutually untrusted with the operator.

Checkpoint

Does incognito guarantee that no data leaves the host? No. It changes local session retention, not the normal scope of tools, model-provider processing, or diagnostic logging. Does a memory note enforce an approval rule? No. It can preserve context for a future turn, but hard controls belong in approval, tool, sandbox, and scheduling mechanisms.