Documents
07 - Debugging Guide
07 - Debugging Guide
Type
Document
Status
Published
Created
May 26, 2026
Updated
May 26, 2026
Template

Start with the right layer#

Helmor issues usually belong to one of four layers: frontend UI, Tauri backend command, sidecar agent execution, or repository and Git state.

Useful checks#

  • Frontend problem: inspect the visible UI, query state, and browser console.
  • Backend problem: check Tauri command errors and Rust logs.
  • Sidecar problem: inspect sidecar logs and streamed JSON events.
  • Git problem: verify the workspace path, branch, target branch, and working tree status.

Development logging#

Run the app in development mode and increase logging when needed with HELMOR_LOG=debug or a more specific level.

Pipeline debugging#

When streamed messages render incorrectly, compare raw sidecar events, accumulator output, stored database rows, and the final frontend message shape.