[KongchangAI]
· 3 min read· 1,654 words

DeepSeek Harness 0.2.2-rc.2 Full Breakdown: Reading All 76 Changes One by One

DeepSeek Harness 0.2.2-rc.2 Full Breakdown: Reading All 76 Changes One by One

DeepSeek Harness 0.2.2-rc.2 released: three new features and 76 changes analyzed

DeepSeek Harness released the 0.2.2-rc.2 pre-release with all 76 changes in the GitHub Release. The article distills what matters for daily use: three new features (Git WorkTree branch-based change display, named multi-level sub-agents, dual desktop update channels), 27 improvements to code review, narrow-screen layouts, long lists and sidebar interaction, 26 fixes for review line-number misalignment, garbled formula copying, plugin load failures blocking page startup and cross-platform display issues, and 20 other migration-critical changes covering the default switch to DeepSeek Search API, Agent Team unified into named sub-agents, PTC tool-call limits, native Office tools, and dependency upgrades. The author recommends the rc channel for users deeply reliant on review and multi-agent collaboration, while stability-focused users stay on the default version.

DeepSeek Harness has released version 0.2.2-rc.2, with all 76 changes documented in the GitHub Release. A Bilibili creator read through the entire changelog line by line, and this article distills the parts that genuinely affect daily use—three new features, experience improvements, bug fixes, and breaking changes.

Keeping both manual loading and emphasis

Three New Features: From Code Review to Multi-Agent Collaboration

The most substantive changes in this release center on three areas. Git WorkTree displays changes by file type per branch commit, which can be handled directly in the review interface, saving the back-and-forth of switching branches to revisit diffs. Sub-agents now support naming and multi-level collaboration, meaning complex tasks can be split into named sub-agents that advance in layers instead of all crammed into a single conversation. The desktop app can switch between stable and development channels, so users who want to try new features no longer need to swap packages manually.

Note that this is still a pre-release, and the default installation remains the old version. To use the new features, you need to actively switch to the rc channel.

Git WorkTree is a Git multi-worktree feature: the same repository can check out multiple branches into different directories at once, sharing the .git object store without repeatedly stashing or switching branches. The article's "displaying changes by file type per branch commit" means leveraging each branch's independent working directory in the worktree to present that branch's file changes relative to the baseline, grouped by type—so viewing and handling happen within the review interface without having to checkout the target branch, revisit the diff, and switch back. This can significantly reduce context-switching costs for teams maintaining multiple feature branches in parallel and doing frequent code reviews, but multiple worktrees consume extra disk space, and the same branch cannot be checked out in two worktrees simultaneously.

Sub-agents are subordinate agents derived from a main agent, each with its own independent context and task description: the main agent handles decomposition and scheduling, while sub-agents complete subtasks within their own context windows and return results. The naming mechanism gives each sub-agent a stable identifier, making it easy to inspect them directly in the UI, reuse them, and even call across levels; multi-level collaboration allows sub-agents to spawn further sub-agents, forming a tree-structured task hierarchy. Compared to cramming all steps into one conversation, this approach prevents context from being crowded out by irrelevant intermediate processes and reduces the burden of each reasoning pass—at the cost of more complex task coordination, result aggregation, and failure retry logic, plus greater reliance on observable hierarchical views when debugging.

27 Experience Improvements: Review, Narrow Screens, and Long Lists

Improvements are the largest category, focused on code review and the smoothness of everyday browsing. Review scenarios see better comment file navigation and narrow-screen layouts, noticeably less lag when viewing large changes, and more generous wait times when creating worktrees in large repositories. Browsing and task coordination for multi-level sub-agents are improved, with task descriptions shown first, support for expanding the main level, and retry after read failures.

Sidebar interaction is another main thread: plugin entries can tuck away infrequently used items, and re-pinning preserves the original order; sidebar file search supports searching by name or path, with adjustable exclusion rules and hidden-file display; long lists scroll and drag more smoothly, and plugin navigation and drawing lists share a scroll area.

On the personalization front, custom themes can now override interface colors for notification cards, plans, and tasks; page zoom, panning, and menu positioning in long lists are now aligned, and in dark mode the file list overlay distinguishes layers by background depth rather than a white shadow. API Key management is more secure, with saved keys displayed as masked values that can be replaced or cleared wholesale. The terminal is visible in the sidebar and can be taken over by user input.

26 Bug Fixes: From Misaligned Line Numbers to Formula Copying

Several fixes in the list have broad impact. The mismatch between review diffs and commit line numbers is fixed, and statistics for large volumes of review discussions are improved; private Gate plugin details can now be viewed properly when only SSH is connected, and optional plugin load failures no longer prevent the entire web page from starting.

The mismatch between review diffs and commit line numbers

The file list view no longer crashes when browsing special filenames or extensions; copying formulas from chat no longer produces garbled text, and formulas in the same Markdown can be copied as LaTeX source. When repeatedly creating drawing branches, title numbering now skips already-used numbers; individual errors when stopping tasks or closing drawings no longer leave tasks unterminated or release resources prematurely. Issues including white flash on Windows dark mode startup, macOS window dragging and paste shortcuts, and chat text being extra-enlarged after viewport switches on mobile Safari are all addressed in this release.

Slow drawing loading and creation on Linux when long-running background processes exist is also fixed; issues with Anthropic Messages integration—signature invalidation after history prefix changes, persistent request failures after compression, and model gateway errors being misreported as invalid API Keys—are handled together. Progressively slower loading when browsing multi-page PDFs and lag during rapid page turns are also on the list.

When Linux has long-running background processes

20 Other Changes: Migration and Upgrade Essentials

This section matters most for existing users. Web search now defaults to the DeepSeekAd Search API, with search and fetch configurable separately; deprecated accounts or API Keys need adjustment by provider and custom configuration, following the upgrade guide. The default cleanup policy for archived drawings is adjusted—to keep local directories, you must disable cleanup first. Agent Team switches to unified named sub-agents, and custom plugins and SDK integrations need migration; processes sharing drawings must upgrade the SDK in sync.

PTC limits total tool calls per run implementation; exceeding the limit terminates the code and clears retained state, while completed operations are not rolled back. Computer Use adjusts the authorization method for window operations and keyboard control, and by default does not move the system mouse. Office switches to native tools, with Web and SDK both able to load skills; old packages and skills need migration. LiveShare adjusts multi-drawing sharing and plugin authorization, and old authorizations must be reconfigured.

Extensions referencing old skill names or paths need migration

On the dependency side, Zod is upgraded to 4.6.6, and StageHand to 4.4.0 with a switch to automatic extension discovery—old Extension ID configurations no longer take effect. Creator's development guidance is unified under DSH Dock, and extensions referencing old skill names or paths need migration; custom model providers support the Gemini native interface, with model listing and reasoning level configuration.

PTC (Programmatic Tool Calling) means letting the model generate and execute code to orchestrate tool calls, rather than issuing calls one by one in natural language: code can contain loops, conditional branches, and intermediate variables, converging multiple tool calls into a single execution. This reduces round trips and token consumption but introduces resource-runaway risk, hence the need to set a total tool-call limit per run. The article's "exceeding the limit terminates the code and clears retained state" means the execution environment is forcibly interrupted at the limit, and retained state such as temporary variables and context caches written in code is discarded—while external side effects already produced (such as requests already sent or data already written) are not rolled back. Callers therefore need idempotent or compensating designs for possible half-completed states.

Agent Team is a mechanism from earlier versions for organizing multiple agents to complete tasks collaboratively; its agents lacked unified naming, and its orchestration and reference methods were inconsistent with the new named sub-agent model. After this unification, team members are expressed as named sub-agents, with invocation, tracking, and permissions all going through the same abstraction—so custom plugins that directly reference the old team structure, or SDK integrations that assemble agent topologies themselves, need rewriting. The key migration points: change agents previously identified implicitly by position or role to explicit names, check whether logic that relied on intra-team message passing should now be handled by sub-agent return values, and upgrade the SDK used by processes related to shared drawings in sync to avoid collaboration call failures from mixing old and new protocols.

Who Should Upgrade, and Who Should Wait

If your daily workflow depends heavily on code review, multi-agent collaboration, or the desktop app, this version is worth trying on the rc channel—especially for pain points you hit every day like review lag and misaligned line numbers. But a pre-release means interfaces are still changing: extensions referencing old skill names, plugins relying on old error classifications, and custom SDK integrations all need to be updated per the migration guide, which is no small cost for plugin authors. Users who just want stability are safer staying on the default old version.

One-line Summary

DeepSeek Harness 0.2.2-rc.2 released: three new features and 76 changes analyzed

Paragraph Summary

DeepSeek Harness has released the 0.2.2-rc.2 pre-release, with all 76 changes recorded in the GitHub Release. The article distills by category the parts that genuinely affect daily use: three new features including Git WorkTree displaying and handling changes by branch, sub-agents supporting naming and multi-level collaboration, and the desktop app switching between stable and development channels; 27 improvements focused on code review experience, narrow-screen layouts, long lists, and sidebar interaction; 26 fixes covering misaligned review line numbers, garbled formula copying, plugin load failures preventing the page from starting, and display anomalies across platforms; and 20 other changes that are migration priorities, involving the default switch of web search to the DeepSeek Search API, Agent Team unified into named sub-agents, PTC limiting total tool calls, Office switching to native tools, and dependency upgrades. The author suggests users who deeply rely on review and multi-agent collaboration try the rc channel, while those seeking stability stay on the default old version.

#DeepSeek Harness#0.2.2-rc.2#Git WorkTree#sub-agents#Agent Team#PTC#DeepSeek Search API#changelog
Share:

Related articles