Harness Buys Augment Code Assets for Autonomous Delivery

A production incident can teach a coding system something its source files never recorded. Harness is buying its way closer to that exchange, bringing selected Augment Code products and their builders into a business organized around releasing and operating software.

On October 8, 2026, Harness announced that it had acquired Cosmos, Auggie CLI, the Code Context Engine and related technology from Augment Code. The team behind those products will join Harness, and Cosmos is available as Harness Cosmos Software Factory Agent. The purchase price was not disclosed; the announcement concerns selected assets rather than an acquisition of the entire company.

The commercial question sits inside that scope. Augment CEO Matt McClernan chose a larger delivery platform as the place to carry forward tools his company had built independently. Harness now has a route into the creation of code, while its planned integration asks the evidence collected during delivery to become useful before the next change is written.

The Platform Choice Behind the Asset Sale

McClernan's explanation centers on reach and effectiveness. He says Harness's integrated platform can deliver Augment's developer capabilities more effectively than building them independently. For an engineering-tools company, that decision moves the business question beyond the quality of the coding assistant: the system also needs a place in the customer's broader development process.

Augment's co-founders, Igor Ostrovsky and Guy Gur-Ari, started the company in 2022. Its earlier work paired systems engineering with AI research to help software understand the codebase it was being asked to change. Ostrovsky remains identified as co-founder and CTO in the acquisition announcement, while McClernan's current CEO role is confirmed by the seller's October 8 statement.

The financing history shows how much institutional capital had already supported that effort. Augment's 2024 Series B announcement reported $227M in new financing after a $25M Series A, bringing disclosed funding at that point to $252M. Sutter Hill Ventures, Index Ventures, Innovation Endeavors, Lightspeed Venture Partners and Meritech Capital were named backers.

Those figures belong to Augment's development history. The $977M post-money valuation reported with that round supplies no purchase price for these assets, and neither party disclosed investor proceeds from the transaction. For operators reading the deal, the more useful detail is that the builders are moving with the technology they understand, keeping product knowledge near the platform expected to distribute it.

What Cosmos Adds to the Engineering Workflow

Cosmos organizes specialized agents around engineering work that continues after an initial answer. A ticket, review event or other trigger can start a workflow; agents can prepare a change, write tests and respond to feedback. Engineers define the checkpoints at which the system needs human judgment, rather than manually directing every routine step.

That changes the experience of receiving a proposed fix. The reviewer can encounter work that has already absorbed failed checks and earlier comments, while retaining responsibility for the decisions that require a person. A software factory in this context is a repeatable arrangement of agents, environments and review rules, assembled around how the team actually develops software.

Harness co-founder and CEO Jyoti Bansal is extending the platform from the other direction. Harness already addresses delivery, security testing, runtime protection and cost management. Adding Cosmos places agent-driven code creation alongside those downstream functions, giving the company a broader relationship with the engineering team buying its software.

The resulting product story still needs careful tense. Harness says Cosmos is available now, while Bansal describes wider code-context and governance connections as planned work. Availability of the software factory gives customers something to adopt; the announced integration describes how Harness intends to connect it more closely with the systems surrounding a release. Customers evaluating the offering need both pieces of information to understand what they are purchasing today.

When Delivery Evidence Travels Back to Code

The integration described by Bansal connects two views of software. Augment's Code Context Engine supplies understanding of the codebase. Harness's Software Delivery Knowledge Graph supplies information about builds, tests, deployments and operations, where a proposed change acquires a version, an environment and a history of observed behavior.

The practical value depends on those records belonging to the same change. Consider the workflow Harness outlines for a vulnerability in a deployed service: identify the affected code and version, prepare a correction, review it, run the relevant checks, then deploy and verify under the team's policies. The example describes an intended workflow, with humans and controls still determining what may proceed.

For an engineering manager, the attraction is the reduction of reconstruction work. A security finding needs enough context to explain the correction; a reviewer needs enough evidence to evaluate it; the release team needs to know which checks apply. Connecting those accounts could reduce the repeated explanation between people who are all working on the same service from different tools.

This is also an organizational choice about where learning lives. An incident report can remain a document someone must remember to consult, or become evidence an engineering workflow can use. Harness's acquisition gives the company more of the machinery needed to pursue the latter path. Its future customer experience will depend on whether the context arriving upstream is specific enough to help an engineer make a decision.

A Broader Relationship With the Engineering Buyer

Harness was co-founded in 2017 by Jyoti Bansal and Rishi Singh. The company's current leadership record identifies Singh as co-founder and board member, preserving his founding role without presenting him as today's CTO. Augment brings a Palo Alto coding business into a San Francisco platform whose original purpose concerned delivery, a convergence shaped by the work between those two activities.

Harness says customers may adopt Cosmos, keep their preferred coding tools or use both. That detail leaves room for an enterprise to expand its workflow without making a wholesale authoring-tool decision immediately. The buyer can evaluate how code creation connects with existing policies and delivery evidence while retaining the development environments its teams already know.

DevCuration has tracked adjacent efforts to make agent activity usable inside consequential workflows, including Serval's acquisition of Ensignia and Arena's financing for AI evaluation. Their products address different parts of enterprise work, but each record puts verification and responsibility close to the business being built around agents.

For Harness, that responsibility will follow the next proposed change through the people who must approve, release and operate it. McClernan's platform decision places Augment's builders nearer to that chain. When a production finding returns, the valuable conversation will be about the affected version, the correction and the evidence the next reviewer has in front of them.