Documentation
Vault workflows
Connect the chat workspace with the rest of your vault using ingestion, exports, favorites, and templates.
Document ingestion pipeline
Whether you drag a file into the drawer or run Convert to Markdown, the same services run in the background.
- •The plugin decides whether files stay as attachments or are routed through the extraction pipeline based on type and size.
- •Uploads prepare the payload and send it to the SystemSculpt service before the document enters the queue.
- •Progress events feed the chat drawer timeline and the processing log so you can follow along in real time.
Queue visibility
Progress cards also log to Obsidian’s console so you can share the same events with support if you ever need help.
Everyday workflows
Summarize an active note
- Open the note you want summarized and trigger Chat with File from the command palette.
- SystemSculpt opens a chat tab, attaches the note, and shows processing status.
- Request the summary format you need, then save the chat back to the vault.
Convert a PDF and ask follow-up questions
- Right-click the PDF → SystemSculpt → Convert to Markdown to send it through the pipeline.
- Watch the Document Processing panel as extraction finishes and the markdown lands in your extractions directory.
- Open the generated file in chat, ask questions, and cite linked sections.
Resume a previous conversation
- Open a chat history file and review its metadata block.
- Run Resume Chat from Current History File to relaunch the conversation with stored model and context.
- Continue the session or export it via the chat export modal.
Saving, exporting, and favorites
Once a chat captures the intelligence you need, SystemSculpt gives you multiple exit ramps without losing metadata.
- •Export conversations as markdown, JSON, or clipboard snippets with cleaned frontmatter.
- •Favoriting a chat stores it for quick access in the ribbon and history list.
- •Templates let you save AI responses and reuse them across chats or note exports.