Skip to content

Conversation Threads

SQLsaber automatically saves your conversations locally so that you can view, resume, and manage them.

Threads allow you to pick up where you left off and track your analytical work over time.

Complete SQL row results are stored separately under SQLsaber’s private user-data query-results directory; thread messages retain only stable bounded model projections and opaque descriptors. Show, export, resume, visualization, sandbox, and notebook paths hydrate complete data from that store without rewriting thread history. Terminal and HTML views may still intentionally render a bounded table.

Capability artifacts are stored separately under the private user-data artifacts directory. Thread messages retain only publication references, not notebook, image, or generated-file bytes. For retained notebook analyses, show and resume reconstruct bounded notebook cells and available plots and list generated-file locations. If the notebook is missing or invalid, replay falls back to the generic artifact listing with an availability notice. Resume is read-only: it never reopens an old notebook kernel.

Thread retention is the source of truth for both CLI query-result and artifact retention. After pruning, SQLsaber removes unreferenced entries older than a 24-hour creation-time safety grace period. Normal saves run maintenance at most daily. If a query result or artifact is missing or corrupt, replay marks it unavailable rather than trusting or rewriting the historical descriptor.

View all your conversation threads:

Terminal window
saber threads list

View the complete transcript of a thread:

Terminal window
saber threads show bb7b4d72

List publication IDs, artifact names, kinds, sizes, and local URIs without replaying the full transcript:

Terminal window
saber threads artifacts bb7b4d72

Resume an existing conversation thread:

Terminal window
saber threads resume bb7b4d72

This:

  • Loads the full conversation context
  • Connects to the same database used in the original thread
  • Uses the same model from the original conversation
  • Allows you to continue where you left off in interactive mode
Terminal window
# Review what you analyzed
saber threads show abc123 > analysis_report.md
# Share the conversation transcript with colleagues
cat analysis_report.md

Check thread commands and options:

Terminal window
saber threads --help
saber threads list --help
saber threads resume --help
saber threads artifacts --help

Now that you understand conversation threads:

  1. Learn advanced querying techniques
  2. Explore model selection for different thread purposes
  3. Review the command reference for all thread options