debug

Debugging Rust backend and React Tauri frontend failures requires a log-first investigation approach that reads rolling backend and frontend log files to identify the actual error before proposing any fix. This prevents slow trial-and-error debugging by turning uncertain bug reports into concrete root-cause diagnoses.

Diagnosing Rust backend session and agent issues starts by reading the backend log files first to find the specific logged error. When existing logs lack detail, add targeted tracing::debug! instrumentation to the failing code path, reproduce the issue, and re-read the logs to pinpoint the exact failure.

Add tracing or logger statements during error diagnosis only when existing logs are insufficient to identify the failing code path. Insert precise Rust tracing::debug! or frontend logger calls as targeted additions, then remove these temporary debug traces after resolving the root cause to maintain clean logging output.

This log-first debugging workflow applies to both frontend React/Tauri failures and backend Rust session/agent issues across common reproduction workflows. It reads frontend and backend log files first, diagnoses from the specific logged error, and adds targeted instrumentation only when logs lack the required detail.

Trial-and-error debugging takes long because it skips reading logs and relies on speculation instead of concrete error data. A log-first workflow prevents this by reading rolling backend and frontend log files to identify the actual error first, accelerating root-cause identification and eliminating uncertain guesses.

Fixing bugs with logs requires readable rolling log files to exist for both backend and frontend, and existing logs may lack the detail needed to identify the failing code path. When logs are insufficient, you must add targeted tracing or logger instrumentation and reproduce the issue to capture the missing diagnostic data.