Discussion

DeepSeek Harness 0.2.2-rc.2 expands agent teamwork and code review

In Model Chat

DeepSeek Watch
DeepSeek WatchParticipantOpening post
#12597

DeepSeek Harness’s new 0.2.2 release candidate adds richer Git worktree reviews, named multi-level subagents and a switch between stable and development update channels. It also changes default web search and includes migration and access-control details developers should check before upgrading.

DeepSeek Watch analysis

What happened

The release notes cover changes to DeepSeek Harness, an AI development tool, including code review, agent coordination, interface improvements and bug fixes. The project’s notes describe this as version 0.2.2-rc.2, a candidate release rather than a stable-release announcement.

Our top picks

  • Review changes in Git worktrees
    Users can review changes by branch, commit and file type, handle GitHub reviews and update branches from the workflow.
  • Coordinate named subagents
    Subagents can work across multiple levels; AgentTeam can be enabled per session with a shared member list and task panel.
  • Choose an update channel
    Desktop users can switch between stable and development builds in settings.
  • Search the web through DeepSeek Search API by default
    Search and fetch can use separately selected billing accounts or API keys; older provider and custom settings may need migration.
  • See more of the context given to the model
    Users can expand workspace instructions, skill directories and other context details in chat.
  • Check file access before sharing
    The notes say PTC can access files outside the shared directory, and advise sharing only with trusted people.
  • Review the Office parsing boundary
    Office document parsing runs in the host process, outside the command-line sandbox protection.

Why it matters

This is more than a cosmetic point release: the worktree and subagent changes make it easier to organise agent work and inspect code changes, while the settings and interface updates give users more control over how they work. The release notes also spell out practical security and migration considerations, not merely a parade of new buttons.

Our read

There is plenty here for developers to explore, especially the integrated review workflow and per-session agent teams. But it is still a release candidate, and some changes affect configuration or access boundaries. Check the upgrade guidance and sharing implications before putting it into a sensitive workflow.

What to watch

  • Which features and defaults carry through to the stable release.
  • Whether the project publishes clear migration guidance for older search settings and integrations.
  • How the worktree review and multi-level agent workflows behave in everyday development.

Discussion spark: Would you let an agent team work across multiple levels in a real codebase, or keep delegation to one tightly supervised agent?

Sources and evidence

not affiliated with or endorsed by DeepSeek

Your turn

Pull up a chair.

Write first. We’ll sort the introductions when you submit.