Repository navigation
1.2.0: small models can change your files - #19
Merged
Merged
Conversation
…d minimatch under the dev tools
…x the stale root version
…e start of long prompts
…equests by their sentences of work
…existing write path
…explain themselves
…ext use to the panel
…align the content-guard hints
…n the same window
…he window in the tier tooltip
…d draw the image icon
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.
Small models can now change part of an existing file. On the edit benchmark,
llama3.2:1bwent from 0 of 12 to 12 of 12 on the suite used during development, and from 0 of 12 to 9 of 12 on the later Python suite, with no damaged file in any 1.2.0 run. All benchmark numbers are from machine B on 2026-10-09.What changed
num_ctx, so Ollama dropped the start of long prompts. Each model now gets one window, 8k on the constrained tier and 16k on the full tier. The new setting ishirayacoder.ollama.contextLength.edit_file: changes part of a file and goes through the existingwriteFilepath, so the permission gate, diff, content guards and audit log all still apply.tools/bench-edit.js.Full notes are in
CHANGELOG.md.Worth checking in review
Dependency overrides.
package.jsonnow pinsglob^14.0.3 andminimatch^11.0.5, scoped to Mocha and@vscode/vsce. Current Mocha 12 still asks for a vulnerableglob, so upgrading would not have fixed it.npm auditwent from 13 dev-only advisories to 0. Nothing here ships, and the pins can go once both tools depend on fixed versions.3B models.
llama3.2:latestgets no benefit by default: it stays on Tier A and passed 0 of 8 and 2 of 8. Forced to Tier B it passed 16 of 16. The default line has not moved, because the other benchmarks have not been re-run with it moved. The changelog recommends the override.Testing
Run for this PR, on Windows:
npm run lint: 0 errors, 85 warnings, all reviewed in the SAST reportnode tools/bench-edit.js --selftest: passed, with a real Python on PATH (thepythoncommand on this machine is the Microsoft Store stub, and the inventory suite fails with it)npm audit: 0 vulnerabilitiesnpm run package: buildshirayacoder-1.2.0.vsixNot run:
Tagging
The version is already 1.2.0 and the changelog is dated 2026-11-06. After merging, tag
v1.2.0onmain. If the merge lands on a later day, update the changelog date first.Each file is its own signed commit, so please merge with a merge commit rather than squashing if you want to keep that history.