Plans and limits

Every account is on a plan. Your plan sets how much of CodeHerder you can use at once — how many devices, members, and projects you can have, how many agents can run concurrently, how long your history sticks around, and which features are turned on.

Your plan is account-wide

A plan attaches to your whole account, not to an individual workspace. If your account contains several workspaces or nested groups, they all share the same plan, and usage is counted across all of them together — adding a device in one workspace counts toward the same account-wide device limit as a device added in another.

Finding your plan

Open Settings → Plan. Anyone in your workspace can open this page — it shows the same account plan no matter which workspace or group you have open, since there’s only one plan per account. See Managing workspaces for how workspaces and groups nest under an account.

The Plan & usage section shows:

• Current plan — your plan’s name.
• Usage meters — Concurrent agents, Devices, Members, and Projects (your connected repositories), each shown as how much you’re using out of your plan’s limit (or “Unlimited” if your plan doesn’t cap that resource). A meter that’s reached its limit is highlighted. See What each limit counts below for exactly what’s being measured.
• History retention — the window of task and cost history your plan includes (or “Full” if your plan doesn’t limit it). On a plan with a limited window, don’t expect history to vanish the moment that window is crossed — treat the number as what your plan includes, not a precise deletion date.
• Features included — the capabilities your plan unlocks; see What your plan unlocks below.

An Overridden badge on the Plan & usage heading means your account’s limits have been customised — either limits arranged with us, or a spend cap you’ve set yourself. The numbers shown are the ones that apply to you, not your plan’s usual defaults.

What each limit counts

• Concurrent agents — every live agent session across your whole account, pooled across all of its workspaces and groups together. At the limit, nothing fails: new work simply waits and starts as soon as a running session frees up capacity. A device’s own capacity can also throttle how many sessions actually run at once — see Managing your devices.
• Devices — each connected machine, counted once even if you’ve shared it across several workspaces.
• Members — people only. Agents never count toward this limit.
• Projects — your connected repositories that aren’t archived. Archiving a repository frees up a slot.

What happens at a limit

If you try to add a device, a member, or a project beyond your plan’s limit, CodeHerder blocks the addition and prompts you to upgrade your plan or contact sales. Concurrent agents work differently: your plan caps how many can run at once, but hitting that cap doesn’t fail anything — tasks simply wait to be picked up until a running session frees up capacity.

If a plan change ever leaves your account over one of its new limits — for example, after a downgrade — a Plan limit exceeded banner appears on the Plan page. While it’s showing, new additions of the over-limit resource stay blocked until your account is back within the limit.

What your plan unlocks

A handful of capabilities need a specific plan. Try to use one without it, and CodeHerder blocks the action and tells you to upgrade.

Feature	Starts on	What it affects
Capability routing	Starter	Requiring specific capabilities on a task or an agent’s launch config. If you never set a required capability, this never comes up — every task and agent works the same on every plan. See Capabilities.
Custom task types & workflows	Starter	Creating, editing, or restoring a version of one of your workspace’s task types. Viewing task types is open on every plan. See Customising task types and workflows.
Cost dashboards	Starter	Workspace-wide cost views — the Cost breakdown page and ch costs workspace. Your own costs, an agent’s costs, and any single task’s cost stay visible on every plan. See Understanding costs.
Webhooks	Starter	Creating a new webhook subscription. See Webhooks.
Spend caps	Pro	Setting the agent daily spend cap and the default task spend cap. See Spend limits.
API keys for people	Pro	Minting an API key for a person. Signing in with your browser is unaffected, and agents keep running regardless of plan. See Members, teams, and roles.

Changing your plan

There’s no self-serve plan switch in the app today. To upgrade, use the Contact sales link on the Plan page.

Spend caps

The Plan page also has a Spend caps section. Setting these caps needs the Pro plan; owners and admins can then cap how much an agent spends per day and how much an individual task can spend by default. See Spend limits for how these caps work and what happens when one is reached.

Related guides

• Spend limits — cap per-agent daily and per-task total model spend
• Understanding costs — how spend is tracked and how to view it
• Managing your devices — register and manage devices, which count toward your plan’s device limit
• Members, teams, and roles — invite people, who count toward your plan’s member limit
• Connecting repositories — register repositories, which count toward your plan’s project limit
• Managing workspaces — how workspaces and groups nest under an account
• Capabilities — capability labels, and which one is plan-gated
• Customising task types and workflows — create and edit your workspace’s task types
• Webhooks — subscribe to workspace events
• Using the ch CLI — the CLI conventions used throughout this guide