Reference

Editor feels slow

Editor lag is a delay between an editing action and the visible response. Isolate the note, its content, and surrounding activity before treating it as a general performance problem.

Updated

By Kition Docs

Verified against Kition 0.2.0 (7d49036f) on 2026-11-06

Isolate the slow interaction

Use the same short editing action for each comparison, such as typing a sentence or scrolling a section. Change one condition at a time so the result tells you which part of the experience needs investigation. The checks below are diagnostic comparisons, not a claim that a particular file size is guaranteed to perform well.

  1. Save the current work and note the file and action that feel slow.
  2. Repeat that action in a small plain note in the same workspace.
  3. Copy the slow note and remove complex blocks, such as diagrams, math, large tables, or images, one at a time.
  4. Close unrelated tabs and pause other active work, then repeat the same action.
  5. Report the reproducible case with the installed version and a redacted description of the note.
What each comparison isolates
ComparisonPossible area to investigate
Small note versus affected noteNote-specific complexity
Note with and without complex blocksRendered content such as diagrams, math, and images
Idle workspace versus active workCompeting runtime or interface activity

Isolate the editor surface

Markdown notes open in the Note kit, which edits in live preview only; it has no separate source mode to compare against. If a small note stays responsive, the slow note’s content is the place to look.

  • Open one small note and compare it with the slow one
  • Close other busy tabs, especially large media, film, or 3D documents, and restart Kition
  • Install the current stable release and retry the same note

Reduce expensive note content

Test large Mermaid diagrams, math blocks, long tables, and many images separately. Split an unusually large note and reintroduce complex blocks one at a time to identify the expensive section.

If a view stops responding

When an editor fails, Kition shows that the view stopped responding while the rest of the app keeps working. Choose Retry, or Reload Kition if it happens again.

Report a reproducible case

Record whether the issue follows one note or every note in the workspace. Copy Support diagnostics from Settings → About. Share raw logs only after inspection and redaction.

Implementation sources

Related pages

Ready when you are.

Kition is a desktop AI workspace for connected documents, structured tables, editable designs, whiteboards, visual workflows, and reviewable AI agents.