Skip to main content
Unlisted page
This page is unlisted. Search engines will not index it, and only users having a direct link can access it.

3.2.3 View chat history

Moss sessions are stored locally. Use the history drawer, workspace context, and current device chip to organize work.

New session​

Click New chat at the top of the Dock for a blank thread. Good when:

  • The last task is done and you want a new topic.
  • The session’s token use is high and earlier context was compressed.
  • Device, project, or goal changed and you do not want old assumptions mixed in.

Resume history​

The history button opens the local chat list. When resuming, Moss reads that session’s messages, results, and summaries; if device or project changed, state the new target first to avoid stale assumptions.

Long sessions get summarized​

Near the model’s context limit, RDK Studio summarizes older content and keeps summaries plus recent messages. Conversation can continue, but early detail thins out. Keep important logs, configs, and conclusions as attachments or files.

Cancel and continue​

In-flight tasks can be canceled. Cancellation does not roll back finished commands, file writes, or device changes; your next message can say “continue from the failed step” and Moss will try to pick up from the last run record.

Multi-device tip​

Avoid vague “that board” in one message. Prefer device aliases, hostnames, or workspace labels to name the target.

Last updated on