Editor feels slow

Isolate the editor surface

Rich editing performs live-preview scans and rendering that Source view does not. If Source view remains responsive, simplify the document or close side tools before treating the embedded runtime as the cause.

• Open one small Markdown document and close search, graph, tags, tasks, backlinks, and broken-link tools
• Switch to Source view to compare the raw Markdown editor with Rich live preview
• Close other busy workspace tabs and restart Kition
• Install the current stable release and retry the same document

Reduce expensive document content

Test large Mermaid diagrams, math blocks, long tables, and many local or remote media items separately. Split an unusually large document and reintroduce complex blocks one at a time to identify the expensive section.

Workspace scans are bounded but still do work

These implementation limits are not performance promises. File size, storage latency, document content, and concurrent dialogs still affect responsiveness.

• Backlinks — scans at most 500 Markdown files
• Local graph — scans at most 400 Markdown files
• Global search — scans at most 400 files and returns at most 200 hits
• Broken links — scans at most 600 Markdown files
• Tasks — scans at most 600 Markdown files
• Vault statistics — scans at most 500 Markdown files

Report a reproducible case

Record whether the issue occurs in Rich view, Source view, or both and whether it follows one document or the complete workspace. Copy Support diagnostics from Settings → About. Share raw logs only after inspection and redaction.