Cache terminal risk assessment by command only#315663
Merged
Merged
Conversation
The cache key for run_in_terminal previously included the model-generated explanation, goal, and unsandboxed-execution reason fields, which differ on every invocation even for the same command. As a result, repeating the same command showed the 'Assessing risk...' spinner instead of using the cached assessment. Narrow the cache key for run_in_terminal to just the command string.
Contributor
There was a problem hiding this comment.
Pull request overview
This PR fixes risk assessment cache misses for terminal tool invocations by narrowing the cache key used for run_in_terminal from “tool id + full parameter set” to “tool id + normalized parameters (command only)”. This prevents repeated terminal confirmations from showing “Assessing risk…” on every re-run when only model-generated descriptive fields changed.
Changes:
- Introduced a shared
_cacheKey(...)helper sogetCached(...)andassess(...)use identical cache key logic. - Added parameter normalization for
TerminalToolId.RunInTerminalso only{ command }contributes to the cache key. - Left all other tools’ cache key behavior unchanged (still based on full parameter set via
stableStringify).
Show a summary per file
| File | Description |
|---|---|
| src/vs/workbench/contrib/chat/browser/tools/chatToolRiskAssessmentService.ts | Normalizes run_in_terminal cache keys to be command-based and centralizes cache key computation to restore cache hits on repeated runs. |
Copilot's findings
- Files reviewed: 1/1 changed files
- Comments generated: 0
lszomoru
approved these changes
May 11, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
#315616
Summary
Fixes the terminal confirmation badge showing
Assessing risk…with a spinner every time, instead of using the cached assessment, when re-running the same command outside the sandbox.The risk assessment cache key was
tool.id + stableStringify(parameters). Forrun_in_terminalthe parameter set includes model-generatedexplanation,goal, andrequestUnsandboxedExecutionReasonfields, which differ on every invocation even when the underlying command is identical — so the cache never hit on the second run.This narrows the cache key for
run_in_terminalto just `{ command }`. Other tools are unaffected and still key on their full parameter set.Repro
Session Context
Key decisions from the development session: