You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/ai-coder/agents/platform-controls/advisor.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -39,8 +39,8 @@ Once the experiment is enabled, configure the advisor under **AI Settings** >
39
39
| Advisor model | Use chat model | Optional dedicated chat model config for the advisor. When unset, the advisor reuses the root agent's model. |
40
40
| Reasoning effort | Model default | Overrides the selected advisor model's reasoning effort. Available only when the model supports selectable effort. |
41
41
42
-
The advisor is not available in plan mode or to subagents. Failed advisor
43
-
invocations refund the per-turn budget.
42
+
The advisor is not available in plan mode or to subagents.
43
+
Failed advisor invocations refund the per-turn budget.
Copy file name to clipboardExpand all lines: docs/ai-coder/agents/platform-controls/index.md
+9-14Lines changed: 9 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -116,18 +116,15 @@ none, if the template does not define any).
116
116
117
117
### Spend management
118
118
119
-
AI Gateway budgets cap each user's AI spend, including Coder Agents chats,
120
-
over a monthly period. Budgets are set per group, and the deployment policy
121
-
selects the group with the largest spend limit when a user belongs to several
122
-
budgeted groups. A per-user override takes priority over group budgets.
119
+
AI Gateway budgets cap each user's AI spend, including Coder Agents chats, over a monthly period.
120
+
Coder sets budgets per group, and the deployment policy selects the group with the largest spend limit when a user belongs to several budgeted groups.
121
+
A per-user override takes priority over all group budgets.
123
122
124
-
Budgets are the only spend cap for Coder Agents chats; chats no longer
125
-
enforce a separate limit of their own, and existing native limit values are
126
-
not migrated to budgets. Budget controls in the Coder UI, the group budget
127
-
endpoints, and the AI spend status endpoints all require a license that
128
-
includes AI Gateway.
123
+
Budgets are the only spend cap for Coder Agents chats.
124
+
Chats no longer enforce a separate limit of their own, and existing native limit values are not migrated to budgets.
125
+
Budget controls in the Coder UI, the group budget endpoints, and the AI spend status endpoints all require a license that includes AI Gateway.
129
126
130
-
See[Spend Management](./usage-insights.md) for details.
127
+
Refer to[Spend Management](./usage-insights.md) for details.
131
128
132
129
### Git providers
133
130
@@ -164,10 +161,8 @@ For chat debug logging (not experiment-gated), see [Chat debug logging](./chat-d
164
161
165
162
## Where we are headed
166
163
167
-
The controls above cover providers, models, system prompts, templates, MCP
168
-
servers, AI Gateway budgets, and data retention. We are continuing to invest in platform controls
169
-
based on what we hear from customers deploying agents in regulated and
170
-
enterprise environments.
164
+
The controls above cover providers, models, system prompts, templates, MCP servers, AI Gateway budgets, and data retention.
165
+
We are continuing to invest in platform controls based on what feedback we get from customers deploying agents in regulated and enterprise environments.
Coder controls agent spend with AI Gateway budgets, and surfaces the
4
-
resulting spend to both admins and users.
3
+
Coder controls agent spend with AI Gateway budgets, and surfaces the resulting spend to both admins and users.
5
4
6
5
## Budgets
7
6
8
-
Coder Agents spend is controlled by AI Gateway budgets, which cap all AI
9
-
Gateway usage (including Coder Agents chats) per user over the budget
10
-
period.
7
+
Coder Agents spend is controlled by AI Gateway budgets, which cap all AI Gateway usage (including Coder Agents chats) per user over the budget period.
11
8
12
-
-**Group budgets**: set a budget for a group from the group's settings
13
-
page. The deployment budget policy resolves which group budget applies
14
-
when a user belongs to multiple budgeted groups.
15
-
-**Per-user overrides**: set a custom budget for an individual user,
16
-
attributed to one of their groups. Takes priority over group budgets.
9
+
-**Group budgets**: set a budget for a group from the group's settings page.
10
+
The deployment budget policy resolves which group budget applies when a user belongs to multiple budgeted groups, which defaults to the group with the highest budget.
11
+
-**Per-user overrides**: set a custom budget for an individual user, attributed to one of their groups.
12
+
Per-user overrides take priority over group budgets.
17
13
18
14
The deployment flags `--ai-budget-policy` and `--ai-budget-period` currently
19
15
support only `highest` and `month`. `highest` selects the group with the
@@ -24,45 +20,36 @@ deployment-wide budget amount, and a configured spend limit cannot exceed
24
20
$1,000,000 per member per period.
25
21
26
22
> [!IMPORTANT]
27
-
> Budget controls in the Coder UI, the group budget endpoints
28
-
> (`/api/v2/groups/{group}/ai/budget`), and the AI spend status and reporting
29
-
> endpoints all require the AI Gateway entitlement. No experiment is needed.
23
+
> Budget controls in the Coder UI, the group budget endpoints (`/api/v2/groups/{group}/ai/budget`), and the AI spend status and reporting endpoints all require the AI Gateway entitlement.
24
+
> No experiment is needed.
30
25
>
31
-
> Native chat usage limits are removed from the application. Existing native
32
-
> limit values are not migrated to AI Gateway budgets and are no longer
33
-
> enforced. Configure AI Gateway budgets separately.
26
+
> Native chat usage limits are removed from the application.
27
+
> Existing native limit values are not migrated to AI Gateway budgets and are no longer enforced.
28
+
> Configure AI Gateway budgets separately.
29
+
30
+
The API reference documents how to [get](../../../reference/api/enterprise.md#get-group-ai-budget), [upsert](../../../reference/api/enterprise.md#upsert-group-ai-budget), and [delete](../../../reference/api/enterprise.md#delete-group-ai-budget) a group budget.
34
31
35
32
### Enforcement
36
33
37
-
- The AI Gateway checks the user's current spend before forwarding each
38
-
request. When spend meets or exceeds the budget, the request is rejected
39
-
and the chat shows a terminal error explaining that the budget was
40
-
exceeded.
41
-
- Brief overage is possible when concurrent requests are in flight, because
42
-
cost is recorded after the LLM responds.
34
+
- The AI Gateway checks the user's current spend before forwarding each request.
35
+
When spend meets or exceeds the budget, the request is rejected and the chat shows a terminal error explaining that the budget was exceeded.
36
+
- Brief overage is possible when concurrent requests are in flight, because cost is recorded after the LLM responds.
43
37
44
38
### User-facing status
45
39
46
-
The usage indicator on the Agents page and the summary in the user menu both
47
-
show the signed-in user's current AI spend, their budget, and the period
48
-
reset date. Both appear only when the deployment has the AI Gateway
49
-
entitlement.
40
+
The usage indicator on the Agents page and the summary in the user menu both show the signed-in user's current AI spend, their budget, and the period reset date.
41
+
Both appear only when the deployment has the AI Gateway entitlement.
50
42
51
43
## Spend visibility
52
44
53
45
Spend is shown where it is actionable:
54
46
55
-
-**Agents page and user menu**: the signed-in user's spend against their
56
-
budget, as described above.
57
-
-**Group settings**: each member's spend against the group's budget, for
58
-
admins who can manage the group.
47
+
-**Agents page and user menu**: the signed-in user's spend against their budget, as described previously.
48
+
-**Group settings**: each member's spend against the group's budget, for admins who can manage the group.
59
49
-**Chat summary panel**: the cost of one chat tree, on a chat's Summary tab.
60
-
A subagent reports the total for its whole tree, including the chat that
0 commit comments