Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.langdock.com/llms.txt

Use this file to discover all available pages before exploring further.

Give an agent its own monthly limit, separate from user limits, so a business-critical agent stays available even after the people using it reach their personal limits. Configure agent limits in Usage and spend limits in your Workspace Settings on the Agents tab.
Agent management features are only available to workspace administrators.

​
When to use an agent limit

Set an agent limit when:
  • An agent is business-critical and shouldn’t stop working when a user runs out of their personal limit.
  • An agent is expensive per message and you want to track its cost separately.
  • An agent is shared across a team and needs a predictable monthly ceiling.
Left at the default, an agent has no limit of its own and its usage counts against each user’s personal limits.

​
Set an agent limit

1. Open the Agents tab Navigate to Usage and spend limits in your Workspace Settings and open the Agents tab. Each agent row shows its limit and how much it has spent this period.
Usage and spend limits with the Agents tab selected, showing an agent's monthly limit and the Limit usage column
2. Edit the limit Find the agent, click Edit limit, and choose Custom with a monthly amount or Unlimited.
Edit monthly limit dialog for an agent with Unlimited and Custom options
For workspaces with user-level data disabled, private agents aren’t listed. Ask the owner to share the agent first.

​
Choose when usage counts

The Limit usage column controls when usage counts against the agent’s limit.
ModeWhen usage counts against the agent’s limit
After user limits (default)Usage counts against each user’s personal limits first. Once a user reaches a personal limit, further usage counts against the agent’s limit.
AlwaysUsage counts against the agent’s limit immediately, so it never draws on personal limits.
Use After user limits for a safety net that steps in only when a user is out of budget. Use Always for a shared resource that shouldn’t consume personal budgets. You can choose a mode only after setting a limit.

​
When limits are reached

Decide what an agent does once a user, workspace, or agent limit is reached. Set this for the whole workspace in Usage and spend limits in your Workspace Settings, or let each agent owner set it on the agent’s edit page. The options are:
  • Switch model (default): the agent answers with the fallback model.
  • Block usage: the agent can’t be used until the limit resets.
Use Block usage for agents that depend on a specific model, where a fallback answer would mislead.

​
What users see

Users see that an agent has a limit, but not how high it is. When the limit is reached, the agent answers with the fallback model or shows that it’s unavailable until the limit resets.

​
Requirements and Cost limit fallback model

Agent limits become available once Extra Usage is enabled for your workspace. Until then, an agent has no limit of its own and its usage counts against each user’s personal limits. When an agent reaches its limit and is set to switch models, it stays available by answering with GPT-5.2.