As we continue to innovate and push the boundaries of mobile app development, it's essential that our pricing model reflects the evolving needs of our customers. That's why we're excited to announce a significant change in how we charge for Augment Code.

Until now, our plans have been based on user messages per month. However, starting October 20, 2026, every plan will come with a pool of credits that can be spent across different activities. This shift is designed to provide more transparency and flexibility for developers working on large, complex codebases.

The current user message model may seem straightforward, but it has two significant problems: it's unfair to our customers and doesn't accurately represent the cost associated with running our business. In fact, usage-based pricing is quickly becoming the industry standard.

One of the main issues with the existing model is that it treats every interaction as equal. However, tasks can differ significantly in scope. For instance, asking an agent to edit a CSS class requires less effort than refactoring the mobile payment view and adding Apple Pay. This approach isn't transparent for developers, and it doesn't match where innovation in this space is heading.

State-of-the-art reasoning models are increasingly designed to stop and ask clarifying questions, effectively penalizing customers because they consume more messages despite achieving a better outcome. Our new credit model addresses these issues by allowing us to charge customers based on what they use, in a way that supports Augment Code's long-term position as the best AI platform for developers.

This change will increase costs for some Augment Code users. Over the coming weeks, we'll work to ensure our customers have all the information they need about how this change may impact them and how to forecast potential costs under the new model.

How the New Credit Model Works

A credit is the unit we use to measure usage in Augment Code. Instead of counting "messages," credits more accurately reflect the actual cost of powering your request: prompts and token usage optimized for cost and quality; industry-leading security and IP protection; as well as the cost of providing you with the best Context Engine in the world.

What Does the Credit Model Allow?

The flexibility of a credit model enables us to broaden our feature set, including:

  • Building new powerful features around AI automation across your stack, not just the IDE
  • Offering more expensive models, such as Opus
  • Adding new lightweight models that we can offer at a lower credit cost

We know our heaviest users will likely feel the change in price the most. We're actively looking to expand our model set to help make the most of your monthly credits in this new pricing structure.

What Do the New Plans Look Like?

| Plan Name | Price | Included Monthly Credits |

| --- | --- | --- |

| Trial | $0 | 30,000* |

| Indie | $20 | 40,000 |

| Standard | $60 | 130,000 |

| Max | $200 | 450,000 |

| Enterprise | Custom | Custom |

*Trial users now get a 30,000 credit pool upon signing up with a valid credit card. When you use your credits, you have the option to choose a paid plan or move to the free plan.

Which Plan is Right for You?

Based on how developers use Augment Code today, here's what typical usage looks like in the new credit-based pricing model:

  • Completions & Next Edit users: Expect to stay within the $20/month plan
  • Daily Agent users: Customers who work on a couple of tasks with an Agent each day should expect between $60–$200/month of total usage
  • Power users: If you rely on Remote Agents, CLI automation, and have most of your code written by agents, expect cost to be $200+/month

Here are three examples of what credit spend might look like per task on Sonnet 4.5:

| Task | Description | User Prompts | Tool Calls (code retrieval, terminal commands, etc.) | Total Credits Used |

| --- | --- | --- | --- | --- |

| Small Task | Quick fixes and isolated changes. Fixes a bug in an API endpoint, adds logging to a service, updates error handling, optimizes a database query, or adjusts service configuration. Typically touches 1-3 files with minimal context needed. | 21 credits (†) | 11 calls for a total of 272 credits | 293 |

| Medium Task | Feature additions or service modifications that span multiple components. Implements new API endpoints with database changes, adds third-party integrations, updates service-to-service communication, or refactors business logic. Touches 10+ files and requires understanding of related systems. | 27 credits (‡) | 23 tool calls for 833 credits | 860 |

| Complex Task | Major feature implementations or architectural changes. Builds entire new service components, implements distributed systems patterns, performs large-scale migrations, or adds cross-cutting infrastructure. Touches 20+ files and requires deep understanding of system architecture. | 87 credits (¶) | 61 tool calls for 4,174 credits | 4,261 |

What is the Impact to Existing Customers?

Your current plan dollars will be migrated to credits. To ease the transition to the new model, we're adding one month of free credits to every account, valid for three months.

| Plan Name | Price | Included Monthly Credits | One-time Bonus Migration Credits |

| --- | --- | --- | --- |

| Indie | $20 | 40,000 | 40,000 |

| Dev Legacy ($30) | $30 | 56,000 | 40,000 |

| Dev | $50 | 96,000 | 40,000 |

| Pro | $100 | 208,000 | 40,000 |

| Max | $250 | 520,000 | 40,000 |

We believe this new credit-based pricing model will better reflect the value you receive from Augment Code and provide more transparency and flexibility for your mobile app development needs.