Harness buys Augment Code assets: coding agents consolidate

On October 8, Harness announced that it bought select Augment Code assets: the Cosmos agent platform, the Auggie CLI, the Code Context Engine and related technology. The team behind those products joins Harness. A coding agent startup that sold directly to developers is now one part of a larger DevOps platform. If your team uses an AI coding agent, this is the pattern to plan for: the tool you picked last year can change owners, roadmap and price in one press release.

What actually happened in the Harness and Augment Code deal

• Assets, not the whole company. The press release says Harness acquired select assets. SiliconANGLE reports the seller as Augment Code Computing Inc. The parties did not disclose terms.
• Cosmos gets a new name. It becomes the Harness Cosmos Software Factory Agent. Harness says it takes work from a ticket or idea to merge-ready code. Then Harness's existing agents handle build, security testing, deployment and cost control.
• Context plus delivery data. Harness plans to connect Augment's Code Context Engine to its Software Delivery Knowledge Graph, which tracks builds, deployments, security and cost. The blog post gives no date for that work.
• People. Augment co-founder and CTO Igor Ostrovsky is joining Harness, according to SiliconANGLE.
• Choice, for now. CEO Jyoti Bansal says customers can keep their current coding tools, adopt Cosmos, or use both. The announcement does not say what happens to existing Augment contracts or to the Auggie CLI roadmap.

Why it matters for your business

Standalone coding agents are expensive to build and hard to make money from. Platforms with distribution, such as Harness, GitHub, Google and JetBrains, are buying them. Expect more deals like this one. For a small team, the risk is not that the tool stops working tomorrow. The risk is that it slowly turns into a feature of a platform you did not choose.

What we tell clients:

• Your context is the asset, not the agent. Keep repo instructions, coding rules and architecture notes in plain files in the repo, such as AGENTS.md. Any agent can read them. A proprietary index does not move with you.
• Keep the agent out of your pipeline's critical path. Agents open pull requests. Your CI, tests and review rules decide what merges. Then swapping the agent is a config change, not a migration.
• Read the contract after an acquisition. Check data retention, model training terms and price-change notice. New owners rewrite these.

Sources: Harness, PR Newswire, SiliconANGLE.