Image: Harness
Why it mattersTeams that already run Harness for testing and deployment gain a coding agent in the same tool, and teams on Auggie CLI or Augment's Cosmos should expect the product to move onto a different sales motion and pricing surface.
A team that already relies on Harness for its CI and deploys now has the option to let a coding agent in the same product open a pull request from a ticket.
Harness announced its acquisition of Augment Code's Cosmos software factory, the Auggie CLI, and the Code Context Engine, along with the team behind them. The company did not disclose the price. The New Stack reports that Cosmos will become the Harness Cosmos Software Factory Agent, that it is available today, and that the deeper integration Harness is pitching has not shipped.
Cosmos today, and the delivery integration later
Cosmos takes a requirement or bug report through to a pull request, with its agents writing and testing code inside isolated virtual machines. The agents can also pick up failed checks and review comments on an existing pull request, using feedback from earlier rounds to make further changes. Teams can fork and customise agents for their own workflows, while Augment's Code Context Engine retrieves relevant codebase context as they work.
The part Harness is pitching as the long-term win remains on a roadmap. The plan is to connect Augment's Code Context Engine to Harness's Software Delivery Knowledge Graph, so the agent working on new code can see deployment history, security findings, and downstream failures. When a Harness agent downstream of coding, for example a testing or deploy agent, finds a problem, it would send that back to Cosmos with the context to fix it, so the coding agent re-opens the pull request. Harness has not set a release date for this integration or explained how the two systems will exchange context.
Humans still approve, and the identity question is open
Developers still approve and merge changes. Harness founder and CEO Jyoti Bansal says teams can decide which work agents handle on their own and where a person reviews or approves. Cosmos stays reachable through Augment Code's existing site while Harness brings it into the broader platform.
Harness plans to bring Cosmos under the identity and policy controls of its Agent Harness, but has not explained how permissions will work across the two systems. The New Stack points out that this gap matters because the industry has started giving agents their own identities, and Cosmos agents already run in isolated virtual machines with configurable review checkpoints. What production data they will be allowed to read, and which downstream actions they can take, is not yet documented.
The context the coding agent gains
The idea Harness is paying for is a coding agent that reads more than the diff it is editing. The Code Context Engine already retrieves related code when the agent is working. The next step is to let the agent read the delivery side of that same code: which deploys recently failed, which security findings are still open, which changes have been rolled back and why. Augment Code co-founder Igor Ostrovsky says the goal is engineering work that becomes autonomous, with engineers reviewing only the parts where judgment is required.
Source
This item was written by an AI system from the linked source. Reveneau is responsible for what it publishes.
Get AI News in your inbox
New developer tools, model and agent releases, and how teams are actually using them to release software. Short, and only when there is something worth reading.
