From d80e7a5fd2c560fed974d65685a14066f8d78427 Mon Sep 17 00:00:00 2001 From: Steve Yegge Date: Sat, 1 Nov 2025 19:14:24 -0700 Subject: [PATCH] Fix bd-6c68: preserve actual daemon failure reasons in bd info Don't override connect_failed/health_failed with auto_start_disabled. This preserves important diagnostic information about whether the daemon crashed vs. was never running. Amp-Thread-ID: https://ampcode.com/threads/T-a8da544a-3e59-4293-903c-ce6be85fc28b Co-authored-by: Amp --- cmd/bd/main.go | 10 +++------- 1 file changed, 3 insertions(+), 7 deletions(-) diff --git a/cmd/bd/main.go b/cmd/bd/main.go index 0565e5c4..85f26201 100644 --- a/cmd/bd/main.go +++ b/cmd/bd/main.go @@ -390,13 +390,9 @@ var rootCmd = &cobra.Command{ } } } else { - // Auto-start disabled - only override if we don't already have a health failure - if daemonStatus.FallbackReason != FallbackHealthFailed { - // For connect failures, mention that auto-start was disabled - if daemonStatus.FallbackReason == FallbackConnectFailed { - daemonStatus.FallbackReason = FallbackAutoStartDisabled - } - } + // Auto-start disabled - preserve the actual failure reason + // Don't override connect_failed or health_failed with auto_start_disabled + // This preserves important diagnostic info (daemon crashed vs not running) if os.Getenv("BD_DEBUG") != "" { fmt.Fprintf(os.Stderr, "Debug: auto-start disabled by BEADS_AUTO_START_DAEMON\n") }