Credits are Coworker's unit of measurement for AI usage. Every time you send a chat in Work mode, run an Agent, or trigger a Deep Work task, Coworker processes tokens through an underlying AI model — credits translate that token cost into a single, easy-to-understand number.
1 credit ≈ $0.50 in AI processing cost.
How credits are consumed
Credit consumption depends on three factors: the number of steps taken, the AI model used, and the length of inputs and outputs. As a general guide:
A typical Work chat (moderate complexity, a few tool calls): ~2–5 credits
A simple Agent run (e.g., a short summary or single data lookup): ~2 credits
A complex Agent run (e.g., multi-step research, drafting a document, coordinating across multiple tools): 5–10 credits
Agents with very broad instructions or many tool calls can consume significantly more. If you notice an Agent using more credits than expected, review its instructions and tool access — overly broad prompts are a common cause.
Your monthly credit pool
Your workspace has a monthly credit pool shared across all users and Agents. Key things to know:
Monthly credits reset at the start of each billing cycle.
Additional credits (purchased separately) roll over month to month and are spent after your monthly allocation is exhausted.
When your personal credit cap is reached, your Agents pause and Work chats are blocked for the remainder of the billing period.
When the network-wide pool is exhausted, all users and Agents are affected until an admin adds more credits or the billing cycle resets.
Checking your credit usage
You can view your credit usage at any time:
Go to Settings → Billing to see your personal usage bar and the overall workspace usage bar for the current billing period.
On the My Agents tab, each Agent row shows a usage bar indicating how many credits that Agent has consumed this billing period relative to its limit (if one is set).
Setting a credit limit on an Agent
You can cap how many credits any of your Agents can spend per month. This is useful for experimenting with new Agents without risking them consuming your full allocation.
By default, Agents have no credit limit — they draw freely from your personal allocation.
Open the Agent in the Agent Builder.
Under the Triggers section, expand Credit Limit.
Enter a monthly credit budget. A tooltip shows your current billing period, overall limit, and estimated per-run costs to help you choose a sensible value.
Click Save. The limit takes effect immediately.
Note: Setting a limit below ~2 credits will show a warning, since that is lower than the cost of the cheapest viable Agent run.
To remove a limit, clear the Credit Limit field and save. The Agent will show No limit in the Agents table.
What happens when credits run out
Agent runs that hit their per-agent limit will show a Credits Exhausted badge in Execution History and will not run again until the billing period resets or the limit is raised.
Work chats are blocked when your personal cap is reached. A message will let you know the limit has been hit.
Network-wide exhaustion: if the workspace pool is depleted, contact your admin to add more credits or wait for the next billing cycle.
If you are not an admin and need more credits, use the Request more credits button in Settings → Billing to notify your workspace administrator.
Tips for managing credit usage
Set per-Agent credit limits when testing new Agents to prevent unexpected overage.
Review Execution History if an Agent seems expensive — the detail view shows every tool call and step the Agent took.
Simpler, more focused Agent instructions generally lead to lower per-run costs.
Credits consumed by a shared Agent run (when another user triggers your Agent) are charged to the triggering user, not the Agent owner.