Yar's DeepSeek Copilot v0.1.14

Released 2026-09-10 details.

• Moved to deepseek-flash (DeepSeek-V4.1-Flash) and removed the DeepSeek V4 Pro option, the analyze_images delegation tool, the hidden Vision-to-Flash fallback, and the retired-model compatibility map.
• Updated the cost catalog to the current rates with the documented peak/off-peak split, and let usage cost be displayed in USD or CNY.
• Fixed the largest avoidable cost of a long chat: a minute-precision timestamp in the system message invalidated DeepSeek's prefix cache on the first request of every generation.
• Reviewer guidance is appended as the newest message instead of being spliced into the system message, so a progress checkpoint or a completion recovery no longer re-bills the whole transcript as a cache miss. Both reviewers ignore that guidance when they read the user's request.
• The coding prompt now budgets code comments: intent that the code does not already state, never a restatement, and matching the file's existing density, since a comment costs output once and input on every later round that re-reads the file.
• The usage popover reports the conversation-wide total computed by the extension host instead of the messages the webview happens to hold.
• Auxiliary compaction uses per-phase output ceilings, the cache-hit ratio is shown per phase, and model capability flags nobody read were removed.
• A finished turn ends with an edited-files summary whose rows open the native change diff; reverting changes is out of scope.
• Pending edit_file and apply_patch previews no longer steal focus, including on macOS, where the platform activates the shown editor even when it is asked to preserve focus.
• Long conversations render lazily, with memoized message rows.
• Added the list_workspace tool; reasoning blocks render Markdown and collapse like the tool lists; fixed the tool-call chevron; attached images open a zoomable, draggable viewer; and the composer gained spacing above its toolbar.
• Added the read_func tool, which returns only the functions, methods, or types named in a source file, chained through their enclosing declarations, so reading one function no longer pulls the whole document into the context. Symbol ranges come from the editor's own language providers, so the tool follows the language instead of a text pattern. Module-level const bindings are resolvable, and an empty answer is believed only after the file has been loaded and the provider has repeated it across a short backoff.
• read_file reads a line range through offset and limit, the fallback for content the editor cannot name as a symbol: search_content locates the name and only those lines are read, with the range bounds, hasMore, and the whole-file hash.
• The prompt and both read tools state one reading order — read_func for a named declaration, search_content plus a read_file range for what the editor cannot name, and a whole-file read only for context spanning declarations — so every chat follows it instead of one conversation's habit.
• Safety decisions start from machine-verifiable facts, so a routine workspace edit or a finite diagnostic command runs without a review round; everything unproven still goes to the independent review.
• A second incomplete verdict from the completion reviewer keeps the delivered answer instead of replacing it with an error.