Agent Upstart

Cool things people are building with agents — and practical help getting the most out of them.

Playbooks · Coding tasks

Auggie 0.37.0: first release after the takeover

Written November 9, 2026

Auggie 0.37.0 (Nov 5) is the first version bump since the Augment CLI changed hands on Oct 8. The licence still names Augment. What's answered, what's not.

The problem it solves

A team paying for Augment Code needs to know what the takeover means for its subscription. On October 8, 2026, Harness announced it had acquired select Augment Code assets, including the Auggie CLI, Cosmos, and the Code Context Engine, with the team behind them joining the buyer. A month later, the first version bump under the new owner has appeared. What happens to existing subscriptions, unused top-ups, or code indexes is not stated anywhere in writing.

What 0.37.0 is — and what it isn't

A dependency update recorded on November 5 moves auggie to v0.37.0, the first version bump since stable 0.36.0 on August 21. That is the whole of what the release amounts to in public: Augment's own changelog still lists 0.36.0 as its newest CLI entry, with no 0.37.0 notes. What 0.37.0 changes is unpublished, so this page lists no feature changes for it. There are none to list.

Meanwhile, the 1.2.0 prereleases continue on the preview and daemon channels, with the daemon channel meant for CI and headless runners. The stable line is still the 0.x line, and latest on npm is still 0.x.

What is still unanswered

The announcement says nothing about what happens to current customers' accounts. It describes the plan — Cosmos becomes the Harness Cosmos Software Factory Agent, and the Code Context Engine is to be connected with the buyer's Software Delivery Knowledge Graph — but gives no date for that connection and no word on what current customers' accounts become.

The paperwork lags the announcement. The legal documents were last read on November 4: the CLI licence, the Professional and Enterprise terms of service (v1.9, August 28, 2025), and the privacy policy (v1.2, August 28, 2025) still name Augment Computing, Inc., while the website footer already carries the buyer's name. A licence that names a company whose assets were sold, four weeks after the deal, is a loose end a paying team should not ignore.

What to do if you run Auggie

Pin the version in CI. latest is 0.x, while the preview and daemon channels carry 1.x prereleases whose permission rules ignore some legacy tool names. An unpinned install can move you across that line without warning.

Check .augmentignore before any print-mode run: the workspace is indexed and uploaded for the Context Engine by default, except files matched by .gitignore or .augmentignore. And remember there is no operating-system sandbox for the local CLI; writing to sensitive paths needs approval since 0.34.0, but the boundary is the permission rules, not isolation.

Verdict

Hold off on signing or renewing until the buyer answers in writing. The version bump shows the CLI is still being shipped under the new owner, but the licence still names Augment and nothing published addresses current subscriptions or top-ups. A renewal is a bet that those answers will be good; there is no reason to place it before they exist.

Limits

Related playbooks

Sources

Back to: Coding playbooks hub · Also: Kilo Enterprise free for Cursor teams · November shutdowns: Runloop, Conductor, Moondream · Agent change deadlines: retirements and shutdowns