Skip to main content
Every AI coworker has a Usage & Activity section with two tabs. Usage shows what the coworker spends and lets you set a monthly limit. Activity is the history of everything it has done, so you can check its work and find out why something went wrong. Your organization’s credits, plans and top-ups are covered in Plans and credits.

​
Usage

Open the coworker and go to Usage & Activity → Usage. The tab shows the coworker’s monthly usage limit and a chart of its usage over time. Change the date range, pick what to show (such as Credits spent or Events), and split the chart by a dimension such as User, Scheduled task, Trigger or Model to see where the credits go.

​
Monthly usage limit

A monthly usage limit caps what one coworker can spend in a month, so a busy scheduled task or trigger can’t use up your organization’s credits.
1

Turn on the limit

In Usage & Activity → Usage, switch on Monthly usage limit (“Pause the agent at a monthly spending limit.”).
2

Set the amount

Vybe fills in $50.00. Enter your own amount in US dollars. The minimum is $0.01. The limit saves automatically.
Since 1 credit is $0.01, a $50.00 limit equals 5,000 credits. Below the amount, Vybe shows how much the coworker has used this month and who gets email alerts. Alerts go out at 50%, 80% and 100% of the limit, to the coworker’s owner, its admins, and your organization’s Owners and Admins. People who turned off Usage reports under Email Notifications in Settings → Personal → Preferences don’t get them.

​
When a coworker reaches its limit

At 100%, “All agent activity pauses at the limit until next month or until you raise it.” That covers chat, Slack, scheduled tasks and triggers.
  • The coworker’s page shows Agent paused: usage limit reached, with a Manage limit button.
  • The AI coworkers page marks it Usage limit reached.
  • In Slack, it replies: “This agent has reached its monthly usage limit, so I can’t respond right now. Raise the limit in Vybe or wait until the next monthly reset.”
  • Scheduled tasks and triggers don’t run. Their runs show as Skipped in Activity, with the reason.
To get the coworker working again, raise the limit, turn it off, or wait until next month.
The monthly usage limit is per coworker. If your organization runs out of credits, every coworker stops, whatever its limit. Chats show Out of credits, and scheduled task and trigger runs are skipped with “No credits left”. See Plans and credits.

​
Activity

Open the coworker and go to Usage & Activity → Activity. Each entry is a run: one piece of work the coworker did, such as answering a message in Slack or in Vybe, handling an email, working on a meeting, running a scheduled task or trigger, or helping another coworker. Runs are grouped by day, newest first. The list updates on its own while runs are in progress, and loads older runs as you scroll. Each run shows:
  • A short summary, or the message that started it
  • Its status
  • Who started it, or which coworker asked for help
  • When it ran (hover for the exact time)
  • The model it used, how long it took, how many steps and tools it used, and the credits it cost
Everyone who can access the coworker can see its activity, including what each run was asked and how it replied. See Sharing and access.

​
Open a run

Click a run to expand it. You’ll see:
  • The error, if the run didn’t finish
  • Input: what the coworker was asked
  • Response: what it replied
  • Tool calls: each step it took, such as “Searched the web” or “Sent email”. Click a step to see its input and output.

​
Filter runs

Click Clear to reset the filters. With no runs yet, you see “No activity yet”. If your filters match nothing, you see “No matching activity”.

​
Run statuses

Common reasons a run is skipped:
  • The coworker reached its monthly usage limit.
  • Your organization is out of credits (“No credits left”).
  • The coworker wasn’t active, for example because it’s archived.
For triggers, the trigger’s Event history also lists every event it received, including skipped ones and why. See Triggers.

​
Shortcuts to activity

  • Overview → Information has a Recent activity card with the latest runs and View activity.
  • Automations → Scheduled tasks and Automations → Triggers each have a View activity button that opens this list filtered to those runs. See Scheduled tasks and Triggers.
  • In a trigger’s event history, View agent activity opens the run for that event.
  • In the ingestion log, Open activity opens the run behind a memory change.

​
Tips

  • Set a limit before you automate. Add a monthly usage limit before you turn on frequent scheduled tasks or busy triggers.
  • Check skipped runs first. If a scheduled task or trigger seems to do nothing, filter by Skipped and read the reason.
  • Use credits per run to tune costs. If a routine run costs more than it’s worth, run it less often or pick a cheaper model for that task.