Skip to content
Model infoModelsSnapshot: 15 Oct 2026

Augment Code / Augment private models

Augment Completion · RLDB

Historical proprietary code-completion model update described by Augment researchers.

historicalClosed weightsCoding
Official documentation (opens in a new tab)Reviewed 15 Oct 2026
3 of 16 specification fields collected
Context windowNot collectedAwaiting source review
Maximum outputNot collectedAwaiting source review
Input billingNot collectedAugment · historical completion engine
Output billingNot collectedNo inferred price

Specifications

Provider-documented facts. “Not collected” means we have not verified that field yet, not that the feature is unsupported.

Context / input limit
Not collected

Exact version-specific value or customer API contract not established.

Maximum input tokens
Not collected

Exact version-specific value or customer API contract not established.

Maximum output
Not collected

Exact version-specific value or customer API contract not established.

Parameters
Not collected

Exact version-specific value or customer API contract not established.

Release date
Not collected

Exact version-specific value or customer API contract not established.

Knowledge cutoff
Not collected

Exact version-specific value or customer API contract not established.

Reasoning
Not collected

Exact version-specific value or customer API contract not established.

Tool calling
Not collected

Exact version-specific value or customer API contract not established.

Structured output
Not collected

Exact version-specific value or customer API contract not established.

Streaming
Not collected

Exact version-specific value or customer API contract not established.

Batch processing
Not collected

Exact version-specific value or customer API contract not established.

Fine-tuning
Not collected

Exact version-specific value or customer API contract not established.

Context caching
Not collected

Exact version-specific value or customer API contract not established.

Published training method
Reinforcement learning from developer behaviors with a learned reward model.Source for Published training method (opens in a new tab)

Access & pricing

Prices belong to an endpoint and billing tier. A provider listing does not guarantee access for every account or region.

Augment · historical completion engine

Provider source (opens in a new tab)
API model ID
Not collected

No verified raw inference model selector. Product, experiment and SDK operation names are not interchangeable API IDs.

Access
Historical managed IDE completion model. Exact current checkpoint availability is unverified.
Regions
No complete model-specific region inventory established.

Endpoint pricing has not been collected. Check the provider for applicable rates.

Data & enterprise terms

Augment says it does not train on customers’ proprietary code. The RLDB report distinguishes internal data and opt-in, appropriately licensed contributions. Indexes and product/account data may persist; the general privacy policy does not establish a universal fixed retention period or zero-data-retention contract.

Read the service policy (opens in a new tab)

Caching

Caching can reuse earlier input processing. Availability, lifetime and billing depend on the endpoint. A cache hit still generates a new response.

01 / INITIAL INPUTProcess & retain

The system processes eligible input and retains reusable state.

02 / LATER REQUESTCheck available state

Reuse depends on matching input, session state and the cache policy.

03 / CACHE HITReuse & generate

Reusing state can reduce repeated work. Any charges follow the billing rules below.

Augment · historical completion engine

Not verified

No model-specific prompt-cache contract established.

How it works
Not collected

No model-specific prompt-cache contract established.

Minimum reusable input
Not collected

No model-specific prompt-cache contract established.

Lifetime & refresh
Not collected

No model-specific prompt-cache contract established.

How to enable it
Not collected

No model-specific prompt-cache contract established.

Usage fields
Not collected

No model-specific prompt-cache contract established.

Billing rules
Not collected

No model-specific prompt-cache contract established.

Limits & data boundaries
Not collected

No model-specific prompt-cache contract established.

No verified cache rate for this endpoint. An empty rate is not a zero charge.

Caching reviewed 15 Oct 2026

What the measurements say

No benchmark observations have been added for this model. We do not turn a vendor description into a performance score.

Latency and throughput depend on the host, request size, reasoning settings and load. There is no measured speed or global usage figure in this record.

The record behind the model

Why it is included

Private classification inferred from provider-owned internal model research and product-only distribution; no public model checkpoint release established.

Classification evidence (opens in a new tab)

Lifecycle dates

Model update described in research article26 Nov 2024Source (opens in a new tab)

Sources reviewed