Skip to main content

Buyer guide

Auggie CLI Team Rollout and Spend Checklist

A pilot plan for Auggie CLI teams: who gets seats, which models they may use, how to watch pooled spend, and what to get from Harness in writing.

Reading time
3 min read
Sources
12 cited

Pilot Auggie on the Standard or Business plan with a written model policy and a weekly usage check, because budgets are Enterprise-only and pooled usage keeps billing past the plan. Judge the pilot on accepted changes and their cost, and get the Harness transition written into the contract before you sign.

When you need this

  • Engineers already use Augment on personal plans and want a team plan.
  • You are choosing between Auggie CLI and another agent for the same team.
  • A renewal is coming and finance wants accepted output per dollar.

Evaluation criteria

  1. Plan choice

    Which plan does the pilot need?

    Look forStandard costs US$20 per month and Business US$100 per month. Each is a flat price for up to 50 seats, with that dollar amount of usage pooled across the team, and a seat is anyone with access to the workspace. Enterprise is custom, with unlimited users, bespoke usage limits, SSO, OIDC and SCIM, customer-managed encryption keys (CMEK), and dedicated support. Teams larger than 50 need Enterprise.

  2. Usage ceiling

    What stops one engineer's usage from surprising finance?

    Look forIncluded usage resets each cycle with no rollover, and usage past it keeps billing at the same rates. Budgets and the organization usage dashboard are Enterprise features. On Standard and Business, write a model policy and read per-member usage on the web dashboard every week. At least one engineer moved to another tool after Augment's October 20, 2025 move to credit pricing, which Augment said would raise costs for some users, so expect finance to ask about cost early.

  3. Model policy

    Which models may the team use?

    Look forOn Enterprise, admins can allow-list models by data-retention policy, restrict which models users pick, set a default model, and require EU inference for EU tenants. On other plans, write the policy down and check usage against it on the dashboard.

  4. CLI or IDE extension

    Will the team work in the IDE extension, Auggie CLI, or both?

    Look forMost public accounts describe the VS Code or JetBrains extension, and some engineers moved to Auggie CLI for speed and scripting. Completions and Next Edit have been Enterprise-only since March 31, 2026, so engineers on other plans who relied on them need another completion tool. Tool permission rules apply in the CLI and Cosmos. The IDE extension ignores them.

  5. Largest repository first

    Does the Context Engine pay off on the code your team works in most?

    Look forRun the pilot on your largest or oldest repository, where the index should matter most. Tilt began with 12 seats, which grew to 24 as engineers asked for access. Collectors ran phased trials on real work under an internal AI committee and has begun shifting to Augment as its main tool.

  6. Spend-tracking worksheet

    What will you compare when the pilot ends?

    Look forTrack per engineer and per week: merged pull requests, review time per change, defects found after merge, usage in dollars by model, and spend per accepted change. Compare each against a baseline from before the pilot. Collectors pulled its usage data together, which showed about 6% of its codebase written by AI tools, to make the case to its CFO.

Questions to ask vendors

  1. After the Harness acquisition, which entity holds our contract and our data, and do plan terms change at renewal?
  2. What is our projected monthly spend at our model mix, including the 40% service fee?
  3. Can we get budgets or per-user limits without moving to Enterprise?
  4. Which IDE features stay on our plan, and until what date?

Red flags

  • A pilot judged on prompts sent when it should be judged on accepted changes.
  • Pooled usage with no model policy and nobody reading the dashboard.
  • A plan for more than 50 people priced without an Enterprise quote.
  • A renewal signed without asking what the Harness transition changes.

Worth evaluating

Listed in no particular order.

Sources

Official documentation
8
Public source
4
  1. Augment Code pricingOfficial documentationaugmentcode.com
  2. Augment docs: Token-based pricingOfficial documentationdocs.augmentcode.com
  3. Augment docs: Usage dashboards & budgetsOfficial documentationdocs.augmentcode.com
  4. Augment docs: Using TeamsOfficial documentationdocs.augmentcode.com
  5. Augment docs: Cosmos admin checklistOfficial documentationdocs.augmentcode.com
  6. Augment docs: CompletionsOfficial documentationdocs.augmentcode.com
  7. Augment docs: Tool permissionsOfficial documentationdocs.augmentcode.com
  8. Augment blog: Augment Code's next chapter (Oct 8, 2026)Official documentationaugmentcode.com
  9. LeadDev: How Tilt's review bot transformed its code reviews (Oct 8, 2025)Public sourceyoutube.com
  10. LeadDev: How Collectors learnt to assess AI coding tools (Oct 15, 2025)Public sourceyoutube.com
  11. Hacker News: leaving Augment Code after its new pricing (Jan 8, 2026)Public sourcenews.ycombinator.com
  12. Hacker News: Augment at a day job, with timeouts and a higher price (Jul 4, 2025)Public sourcenews.ycombinator.com