Productspublished

Harness Launches Agent-Ready Repository and AI Review for High-Volume Code Changes

The products pair high-volume repository operations with inherited permissions and merge-time checks, but Harness still places the final decision to ship with people.

By 2 min read
Harness Launches Agent-Ready Repository and AI Review for High-Volume Code Changes

Listen to this story

The audio brief

About 1:26
0:001:26
Read transcript
Harness is launching an agent-ready code repository and AI Code Review to handle a bottleneck created by coding agents: they can produce changes faster than people can review, approve, and merge them. The products launched on August twenty-seventh, and they focus less on generating code than on processing the flood that follows. Harness Chief Executive Jyoti Bansal says traditional code-management workflows assume a person writes code, opens a pull request, and waits hours or days for colleagues to test and approve it. Agents can complete comparable work in minutes or hours, so Harness says its repository is designed to handle thousands of pull requests and commits at once, with search, history, and comparisons operating at that scale. The access model is deliberately tied to a person. Agents can work through Model Context Protocol or command-line interfaces, but they inherit the permissions of the human who initiated the task. Those permissions can be limited to a repository, branch, project, or environment, and the human remains identified in the audit trail. AI Code Review runs at merge. Teams can require checks across an account or tune them by project. Failed checks send changes back for updates, but the system is a decision gate, not autonomous deployment authority: a person still decides what ships. Harness estimates its own teams saved ten thousand hours last month. The key constraint to watch is whether that review gate can keep pace without moving final responsibility away from humans.

Story brief

3 key points

Harness launched Code Repository and AI Code Review on August 27 to manage the volume of changes coding agents can produce faster than human-paced pull-request processes. The repository is designed for thousands of simultaneous pull requests and commits, while agents inherit the permissions of the human who initiated their work. AI checks run at merge and can block changes, but humans retain shipping authority....

  1. 01

    Harness targets the post-generation bottleneck: reviewing, approving and merging agent-produced code.

  2. 02

    Agents can operate through Model Context Protocol and command-line interfaces, subject to inherited repository, branch, project or environment permissions.

  3. 03

    Teams can require AI checks account-wide or tune them by project; failed checks send changes back for updates.

Harness has launched an agent-ready code repository and AI code-review product built for a delivery problem that emerges after code generation: agents can create changes faster than conventional pull-request workflows can absorb. Its answer combines high-volume repository operations, inherited access controls and merge-time checks, while keeping people responsible for what ships.

The constraint shifts from writing code to processing it

Harness Code Repository and AI Code Review launched August 27. Chief Executive Jyoti Bansal said established code-management routines assume a person writes code, opens a pull request, then waits for colleagues to adjust, test and approve it over hours or days. He argues that model is strained when agents generate in minutes or hours work that once took developer teams days or weeks.

That framing distinguishes the launch from a new code-writing tool. Harness is aiming at the repository, review and approval path that follows generation, with agent access tied to the human who started the work.

Throughput comes with a permission boundary

The repository is designed for thousands of simultaneous pull requests and commits, with search, history and comparisons operating at that volume. Each agent inherits permissions from its human trigger, scoped to a repository, branch, project or environment. Harness says the human initiator remains responsible in the audit trail.

How agents can work in the system

  • Use Model Context Protocol and command-line interfaces to run delivery workflows programmatically rather than through a browser.
  • Find reviews by an author’s email, collect pull requests across repositories, and create, reply to or resolve comment threads through the command line.
  • Operate only within the repository, branch, project or environment permissions inherited from the human trigger.

A merge gate, not autonomous deployment

AI Code Review checks code at merge. Teams can make selected AI checks mandatory across an account or tune them by project. A failed check rejects the change for updates, while suggested reviewers and labels are intended to speed remediation.

Harness describes that as a decision-support gate, not a handoff of production authority. AI Code Review is meant to identify changes ready for staging and those needing further action; a human still decides what ships.

An internal efficiency figure

Harness says it used both capabilities internally for months and estimates teams saved 10,000 hours in the last month. The figure is a company-supplied internal estimate.

Sources

  1. siliconangle.comHarness tackles influx of agent-delivered code with Code Repository and AI Code Review - SiliconANGLE