From 63edd27eeb3060e16f404aaefdb71014f58a4a62 Mon Sep 17 00:00:00 2001 From: Erik Seliger Date: Mon, 26 Oct 2026 22:58:53 +0000 Subject: [PATCH 1/3] docs: explain how Agentic Batch Changes is billed The configuration page said model usage draws on Sourcegraph Model Provider credits and that Deep Search is billed separately from the agentic batch change's own metering, without saying what that metering is. Readers took this to contradict the merged-changeset pricing. Add a Billing section: merged changesets are billed in per-batch-change tiers, model usage is not billed separately, publishing stops when credits don't cover another merge, and Deep Search is billed at its own rate. Remove the Model Provider credits sentence and describe the coding agent entitlement as a limit, not metering. Amp-Thread-ID: https://ampcode.com/threads/T-01a17a60-b4a0-7520-b5d0-ca3bf24331f6 --- docs/agentic-batch-changes/configuration.mdx | 16 ++++++++++++---- 1 file changed, 12 insertions(+), 4 deletions(-) diff --git a/docs/agentic-batch-changes/configuration.mdx b/docs/agentic-batch-changes/configuration.mdx index 972c57ab6..204e06b58 100644 --- a/docs/agentic-batch-changes/configuration.mdx +++ b/docs/agentic-batch-changes/configuration.mdx @@ -142,9 +142,19 @@ All code-modifying work runs on executors: - [Sourcegraph Cloud](/cloud) customers have managed executors with no additional setup required. - Self-hosted customers need [executors deployed](/self-hosted/executors) and registered against both the `batches` and `batches-hooks` [queues](/self-hosted/executors/executors-config#queues), running a version that matches the instance. Without an executor on `batches-hooks`, batch changes can execute and publish, but CI and merge-conflict hook automations never run. +### Billing + +Agentic Batch Changes is billed per merged changeset. A changeset counts once it merges, whether it was merged on the code host or in Sourcegraph. Changesets that are closed or never merged are not billed, and model usage by the agent and its coding agent steps is not billed separately. + +Rates are tiered within each agentic batch change: its first 100 merged changesets are billed at the tier 1 rate, changesets 101 through 300 at the tier 2 rate, and every further changeset at the tier 3 rate. Each agentic batch change starts at tier 1. Subscription admins can find the current rates and consumption on the [Credits page in Enterprise Portal](/admin/enterprise-portal#credits). + +When the subscription's credits don't cover another merged changeset, the agent can't publish new changesets. Changesets that are already published can still be merged. + +The agent's [Deep Search](#deep-search) research consumes credits at the [Deep Search rate](/deep-search#credit-consumption). + ### Usage limits -Coding agent runs are metered per user through the **Batch Changes coding agent step runs** [entitlement](/admin/entitlements), managed under **Administration → Users & auth → Entitlements**. Each coding agent run in a repository consumes one unit. A default entitlement applies to every user, and an explicit grant replaces the default for a specific user: +Coding agent runs are limited per user through the **Batch Changes coding agent step runs** [entitlement](/admin/entitlements), managed under **Administration → Users & auth → Entitlements**. Each coding agent run in a repository consumes one unit. A default entitlement applies to every user, and an explicit grant replaces the default for a specific user: - Users without an entitlement have unlimited usage. - A positive limit blocks further runs once reached until its window resets. @@ -152,11 +162,9 @@ Coding agent runs are metered per user through the **Batch Changes coding agent Blocked runs tell the user which limit was hit and when it resets. -Model usage, for both the agent's own conversation and its coding agent runs, draws on your instance's [Sourcegraph Model Provider](/model-provider) credits. - ### Deep Search -Before drafting a plan, the agent researches with [Deep Search](/deep-search). Deep Search usage consumes subscription credits separately from the agentic batch change’s own metering. +Before drafting a plan, the agent researches with [Deep Search](/deep-search), which is [billed](#billing) at its own rate. The agent is built to research deliberately rather than repeatedly: From 2609030a3cd17a269a33415d7f55a730fd4c54f2 Mon Sep 17 00:00:00 2001 From: Erik Seliger Date: Mon, 26 Oct 2026 23:30:06 +0000 Subject: [PATCH 2/3] docs: drop the coding agent entitlement from Agentic Batch Changes The per-user coding agent step entitlement doesn't affect what customers pay, so it doesn't belong next to billing. Remove the Usage limits section and the context filters sentence that linked to it. Amp-Thread-ID: https://ampcode.com/threads/T-01a17a60-b4a0-7520-b5d0-ca3bf24331f6 --- docs/agentic-batch-changes/configuration.mdx | 10 ---------- docs/context-filters.mdx | 2 -- 2 files changed, 12 deletions(-) diff --git a/docs/agentic-batch-changes/configuration.mdx b/docs/agentic-batch-changes/configuration.mdx index 204e06b58..c4c091a58 100644 --- a/docs/agentic-batch-changes/configuration.mdx +++ b/docs/agentic-batch-changes/configuration.mdx @@ -152,16 +152,6 @@ When the subscription's credits don't cover another merged changeset, the agent The agent's [Deep Search](#deep-search) research consumes credits at the [Deep Search rate](/deep-search#credit-consumption). -### Usage limits - -Coding agent runs are limited per user through the **Batch Changes coding agent step runs** [entitlement](/admin/entitlements), managed under **Administration → Users & auth → Entitlements**. Each coding agent run in a repository consumes one unit. A default entitlement applies to every user, and an explicit grant replaces the default for a specific user: - -- Users without an entitlement have unlimited usage. -- A positive limit blocks further runs once reached until its window resets. -- A limit of zero blocks coding agent runs entirely. - -Blocked runs tell the user which limit was hit and when it resets. - ### Deep Search Before drafting a plan, the agent researches with [Deep Search](/deep-search), which is [billed](#billing) at its own rate. diff --git a/docs/context-filters.mdx b/docs/context-filters.mdx index 35d104a92..5beff4718 100644 --- a/docs/context-filters.mdx +++ b/docs/context-filters.mdx @@ -135,8 +135,6 @@ A blocked repository fails its execution with one of these messages, which the a The message names neither the rule nor the matching file. If the path search itself fails or returns incomplete results, the execution fails with "could not verify the repository against the agent context filters; please retry or contact your administrator" and can be retried. -A blocked coding agent step does not consume a unit of the user's coding agent step [entitlement](/agentic-batch-changes/configuration#usage-limits). - ## Verifying a filter Ask Deep Search a question that would require the excluded content, and @-mention the repository or file directly. A working filter produces an answer that does not reference the content, and the [list of sources](/deep-search) contains none of it. If you @-mention filtered content, Deep Search reports it as not found rather than acknowledging that it was excluded. From 48928f61e33fd0178dea24bd5d2014331774bf2a Mon Sep 17 00:00:00 2001 From: Erik Seliger Date: Mon, 26 Oct 2026 23:41:16 +0000 Subject: [PATCH 3/3] docs: drop merged changeset tiers from Agentic Batch Changes billing Enterprise Portal lists the tiered rates; the page links there. Amp-Thread-ID: https://ampcode.com/threads/T-01a17a60-b4a0-7520-b5d0-ca3bf24331f6 --- docs/agentic-batch-changes/configuration.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/agentic-batch-changes/configuration.mdx b/docs/agentic-batch-changes/configuration.mdx index c4c091a58..6486d7386 100644 --- a/docs/agentic-batch-changes/configuration.mdx +++ b/docs/agentic-batch-changes/configuration.mdx @@ -146,7 +146,7 @@ All code-modifying work runs on executors: Agentic Batch Changes is billed per merged changeset. A changeset counts once it merges, whether it was merged on the code host or in Sourcegraph. Changesets that are closed or never merged are not billed, and model usage by the agent and its coding agent steps is not billed separately. -Rates are tiered within each agentic batch change: its first 100 merged changesets are billed at the tier 1 rate, changesets 101 through 300 at the tier 2 rate, and every further changeset at the tier 3 rate. Each agentic batch change starts at tier 1. Subscription admins can find the current rates and consumption on the [Credits page in Enterprise Portal](/admin/enterprise-portal#credits). +Subscription admins can find the current rates and consumption on the [Credits page in Enterprise Portal](/admin/enterprise-portal#credits). When the subscription's credits don't cover another merged changeset, the agent can't publish new changesets. Changesets that are already published can still be merged.