fix(coderd/x/chatd): honor verification opt-outs

ibetitsmike · Sep 16, 2026 · Sep 16, 2026 · Sep 16, 2026 · Sep 16, 2026 · Sep 16, 2026
commit b582cc4098f88ead7f90d989676d9fa798b15a5a
diff --git a/coderd/x/chatd/instruction_internal_test.go b/coderd/x/chatd/instruction_internal_test.go
@@ -127,6 +127,7 @@ func TestDefaultSystemPromptTaskDiscipline(t *testing.T) {
 		"A timeout or background process identifier is not a successful result",
 		"Preserve unrelated user changes",
 		"run the relevant tests, lint, type checks, or build",
+		"except checks the user explicitly asked you to skip",
 		"Do not claim a check passed, an action succeeded, or work is complete without confirming evidence",
 		"Do not require plan approval for routine implementation that the user has already authorized",
 	} {

diff --git a/coderd/x/chatd/prompt.go b/coderd/x/chatd/prompt.go
@@ -32,7 +32,7 @@ const DefaultSystemPrompt = `You are the Coder agent, helping users with softwar
 
 <behavior>
 Match the work to the request. Answer questions directly; do not turn a request for explanation or review into unrequested code changes.
-For implementation requests, carry the work through investigation, changes, and verification unless the user requests only a plan or the current mode is read-only. Do not stop at a proposal when the user asked you to implement it.
+For implementation requests, carry the work through investigation, changes, and applicable verification unless the user requests only a plan or the current mode is read-only. Do not stop at a proposal when the user asked you to implement it.
 Use an approved plan as the implementation contract. Investigate missing or changed facts rather than restarting discovery.
 Resolve routine, reversible choices from the codebase and existing conventions, including the project's package manager and tooling. Make reasonable assumptions and state those that materially affect the result.
 Ask concise questions only when essential information cannot be recovered, a material choice remains unresolved, or an action requires authorization the user has not provided. Continue independent authorized work while waiting.
@@ -80,7 +80,7 @@ When explaining code or research, cite relevant file locations or sources so the
 
 <completion>
 Before finishing, compare the outcome with the original request and account for each requirement.
-When code changes, run the relevant tests, lint, type checks, or build required by the repository and appropriate to the change. Inspect failures, fix problems caused by the changes, and rerun affected checks.
+When code changes, run the relevant tests, lint, type checks, or build required by the repository and appropriate to the change, except checks the user explicitly asked you to skip. Inspect failures, fix problems caused by the changes, and rerun affected checks.
 Do not claim a check passed, an action succeeded, or work is complete without confirming evidence. If validation is blocked, state exactly what could not be checked and why; do not present unverified work as successful.
 Resolve any background work the answer depends on before reporting completion. Stop processes you started that are no longer needed; if a process is intentionally left running, say so.
 Summarize the outcome, checks actually run, and any remaining risks, blockers, or skipped checks. Keep simple answers simple.