# Activity

Source: https://www.hyperagent.com/docs/concepts/agents/activity

> For AI agents: the documentation index is at https://www.hyperagent.com/llms.txt and the complete documentation in one file at https://www.hyperagent.com/llms-full.txt. Any docs page is also served as Markdown by appending `.md` to its URL.

The agent's own thread history: every run it has done, live and interactive alike, with search and filters, each row opening the thread behind it.

When an agent runs on its own, on a schedule, in Slack, from a webhook, you need somewhere to see what it has been doing. **Activity** is that place: the agent's own history of runs, one row per thread, each opening the conversation behind it. It is where you watch a working agent rather than configure it.

Every run an agent does becomes a thread, and the Activity tab lists them all,
live runs and conversations together, so you can open any one and see exactly
what happened.

The complete run history for one named agent. Open any row to inspect its
thread, tools, approvals, files, and output.

The fleet-wide view across every agent you operate: active work, decisions,
cost, and quality trends.

## Open the agent's history [#open-the-agents-history]

Activity is a tab on the agent's own page, alongside Overview, Instructions, Autonomy, Knowledge, Integrations, Invocations, and Tools. Open an agent and select **Activity**, or go straight to it at `/agents/:id?page=activity`. It is scoped to that one agent: this is the agent's history. The fleet-wide view across every agent you operate is the [Command Center](https://www.hyperagent.com/docs/concepts/command-center).



## What each row is [#what-each-row-is]

Every row is one **thread**, which is one run or conversation the agent handled, and it links straight to that thread at `/thread/:id`. A background run started by a [schedule](https://www.hyperagent.com/docs/concepts/agents/invocations/schedules), Live Mode, or a webhook lands in the same list as a conversation you had by hand, so the whole of what the agent has done sits in one timeline. Opening a row is how you audit a run: the thread holds the complete record of what the agent read, did, and produced.

The **Search threads...** input narrows the list to matching runs, so you
can find one conversation among a long history.

The **Filter threads** control scopes which of the agent's threads are
listed; on a shared agent, that includes narrowing to your own runs versus
everyone's.

## Turn on Live Mode from here [#turn-on-live-mode-from-here]

When an agent isn't on a schedule yet, Activity is also where you start one. A **Live** card at the top of the list offers **Set up Live Mode**: turn it on and the agent checks in on a schedule, with each run landing in this list and a notification only when something needs you.

Once Live Mode is on, its scheduled runs appear in Activity right beside the
threads you started, so the tab is the single record of the agent working,
whether you kicked it off or the schedule did. See [Live
Mode](https://www.hyperagent.com/docs/concepts/agents/invocations/live-mode).

## Where to look for cost [#where-to-look-for-cost]

Activity answers "what has this agent done," not "what has it spent." Cost lives on the agent's Overview, switchable between total, per run, and per thread, and the [Usage tab](https://www.hyperagent.com/docs/concepts/threads/thread-settings#see-what-a-run-has-cost) inside any single thread breaks down that one run.

## FAQs [#faqs]

Yes, but it isn't this tab. The [Command Center](https://www.hyperagent.com/docs/concepts/command-center) is the fleet-wide dashboard: active operations, items needing attention, and cost and score trends across every agent. Activity is the per-agent drill-down you land on from there.

Yes. Every run becomes a thread, whatever started it, so schedules, Live Mode, Slack, Telegram, webhooks, and hand-started conversations all appear in the same list. Each opens the thread with the full record of that run.

Yes. Each row links to its thread, which holds the complete transcript: the messages, tool calls, approvals, and outputs. That is the place to audit a run rather than a status badge.