From df4b903b1f8b7e9a6178e65cee39ac025afa8a87 Mon Sep 17 00:00:00 2001 From: Protocol-zero-0 <257158451+Protocol-zero-0@users.noreply.github.com> Date: Fri, 20 Feb 2026 17:39:38 +0000 Subject: [PATCH] fix: clarify bug responsibility in sentinel guard message Address review feedback from @HenryLoenwind: - Change "This is a bug" to "This is a bug in the calling code shown in the attached stacktrace" to prevent users from reporting against the guard itself instead of providing the calling trace. Co-authored-by: Cursor --- src/config/io.ts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/config/io.ts b/src/config/io.ts index c5ccbb2f33b..7d19893a813 100644 --- a/src/config/io.ts +++ b/src/config/io.ts @@ -1194,7 +1194,7 @@ export function createConfigIO(overrides: ConfigIoDeps = {}) { if (json.includes(REDACTED_SENTINEL)) { const sentinel_err = new Error( `Refusing to write config for "${configPath}": found redaction sentinel ` + - `"${REDACTED_SENTINEL}". This is a bug — credentials would be permanently lost. ` + + `"${REDACTED_SENTINEL}". This is a bug in the calling code shown in the attached stacktrace — credentials would be permanently lost. ` + `The config file on disk was not changed.`, ); deps.logger.error(