When a check fails
The work record keeps the failing command, its output, the owning project area, and the next action together. The agent can inspect relevant files and configuration before proposing a change. A repair proposal does not count as a fix until it passes review and verification.
Understand a review that cannot be verified
In the VS Code extension, version 1.6.202 and later, repair review keeps the reviewer’s complete response and the specific error when its answer cannot be read or its source citation cannot be verified. The reviewer receives that error with the same requirements, failure, current source, and proposed change for correction.
If the corrected answer still cannot be verified, the proposal remains unreviewed. This differs from a valid review that rejects a repair for a stated reason. An unavailable review cannot approve a change, prove an application defect, or complete the task. Review evidence may contain project source and model responses; keep it private and review it before sharing.
In the VS Code extension, version 1.6.204 and later, Ollama streams that get stuck emitting a long uninterrupted run of backslashes are cancelled even inside an unfinished JSON code field. The same selected model receives one output recovery with the original evidence. If that also fails, the work stays at its provider-retry checkpoint. A partial response never becomes an approved patch.
Verify the repair
In the VS Code extension, version 1.6.215 and later, duplicate JSON fields and malformed repair entries are held for model correction before file changes are interpreted. A complete invalid batch is not reduced to its valid-looking entries. The original response and specific error remain available to the same model, and independent review and validation still follow a corrected proposal. Legacy recovery of a truncated response also rejects malformed completed entries.
In the VS Code extension, version 1.6.214 and later, a review citation to an existing JSON value or object member can differ in formatting whitespace. Verification preserves quoted text, keys, values, escapes and token order, and records the checked source fingerprint. Missing fields, changed values and citations taken from diagnostic output still fail verification. The independent model must still establish that the proposed repair addresses the failure.
In the VS Code extension, version 1.6.213 and later, workspace-labelled ESLint errors are recognized even when each line starts with a package and task name. For TypeScript parsing errors, repair evidence includes the effective parser settings from the failing package when available. This reads configuration without applying a fix; the model still needs to reconcile current source and diagnostics, obtain independent review, and pass validation.
In the VS Code extension, version 1.6.212 and later, a focused retry preserves the dependency setup setting from its executable validation plan. Resuming one failed check no longer silently disables setup. An explicit opt-out stays disabled, and passing that focused check still requires the remaining project validation.
In the VS Code extension, version 1.6.211 and later, validation dependency setup also checks declared workspace members when a root lockfile exists. A dependency added to a member can trigger setup before the next check. Saved validation steps inherit dependency setup unless explicitly disabled; workspace exclusions and noninteractive installs remain respected.
In the VS Code extension, version 1.6.209 and later, structured Ollama repair requests use compatible decoding guidance while retaining the complete response contract. A patch still needs its required metadata and valid changes, and a blocked answer still needs a reason. This improves response formatting; it does not mark a repair accepted or bypass independent review.
In the VS Code extension, version 1.6.207 and later, individual validation steps carry the same noninteractive settings as a complete validation bundle. Root and package commands inherit CI mode, including commands run through the visible terminal. The caller's environment is restored afterward, and failing commands keep their exit codes.
In the VS Code extension, version 1.6.206 and later, an unlimited repair using the selected Ollama model keeps a timed-out repair review at the same request. It waits 5, 10, 20, 30, then 60 seconds between retries, without spending source repair attempts or changing models. Each request still honors its deadline, and you can cancel while waiting. Finite repair policies and authentication or configuration failures retain their existing checkpoint behavior.
In the VS Code extension, version 1.6.205 and later, repair review independently reads the current contents of every file in the proposed change. Every source citation must match the current file before the review can advance. A correction request includes those current files again; proposed code and error messages are not substitutes for existing source.
Work item progress counts delivery work separately from acceptance. When a run resumes after cancellation, acceptance shows that work is in progress and identifies the previous cancellation. The earlier result remains in history. Open repair tickets still require a verified fix and a passing retest before they can close.
After an approved scoped change, run the exact failed check again. If it passes, continue with the configured project validation. The board and activity history distinguish a successful focused check from full project completion, review, or sign-off.
Keep the history
Repair limits and history retention are configurable. When the attempt limit is set to zero, repair work can continue until it is resolved or cancelled. Retained history lets you see earlier failures and proposals; it does not make a failed check pass or grant approval automatically. Automatic repair can still be turned off.
In the VS Code extension, version 1.6.203 and later, new provider and tool operations keep separate history records when the extension reloads and continues the same run. Status and completion updates stay attached to their original operation. Keep earlier exported evidence when investigating work that predates an update.
Wait for the selected Ollama model
In version 1.6.207 and later, extension requests leave model retention to Ollama's configured policy. They no longer request that a model remain loaded indefinitely. Model selection is preserved, and removing that forced retention does not delete a downloaded model.
In versions with model availability waiting enabled, a request can remain in progress while the selected local model becomes available. The agent does not switch the request to a different model or unload another loaded model as part of that wait. Availability retries do not count as source repair attempts. You can cancel the active request; retry timing and optional limits are configurable.
Check version and provider behavior
Features and settings vary by surface and installed version. Check the listing for your installed extension before relying on a control described here. Provider availability, context capacity, and data handling also depend on the selected model, endpoint, and settings. See Models and providers and the Privacy Policy.
A model response or a changed file is not proof of completion. Review the diff, validation result, and any required acceptance evidence.
Recover a repeated Writer response
In VS Code 1.6.606, a focused Writer ticket that gets repetitive output from Ollama can request one alternative approach before retrying. If the Writer still produces no usable result, the ticket remains open with its checkpoint.