> For the complete documentation index, see [llms.txt](https://docs.ox.security/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ox.security/vibesec/agent-activity-log.md).

# Agent Activity Log

The Agent Activity Log page provides visibility into the agent-side activity that OX reviewed across your organization. This includes prompts developers send to their AI coding agents and tool use the agents perform, such as MCP server calls, bash commands, and external SaaS calls.

The log covers both activities that OX reviewed and approved, and activities where OX took action, such as providing inline guidance or blocking a tool call.

Reviewing this page helps you see the full picture of what VibeSec does for each agent action, including the reviews that happen in the background and never surface in the agent chat.

<figure><img src="/files/ucY8ahlrhy2H1xQzgbQB" alt="" width="563"><figcaption></figcaption></figure>

Activity appears in real time, so new rows stream in without a browser refresh. Showing the last few hours, older events are deleted.

## Activity table

The activity table lists each agent action with a summary of how VibeSec reviewed it. An **Activities** counter at the top of the page shows how many rows match the current filters.

| Column        | Description                                                                                                                                                                                                                           |
| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Action**    | The type of action the agent performed, such as User Prompt or Tool Use. Each row also shows context for the action: for a prompt, the redacted prompt notice; for a tool call, the tool name with the executed command or arguments. |
| **When**      | When the agent action occurred, shown as a relative time.                                                                                                                                                                             |
| **User**      | The user who performed the action.                                                                                                                                                                                                    |
| **Role**      | The role of the user who performed the action in the OX platform.                                                                                                                                                                     |
| **AI Tool**   | The coding tool that produced the action.                                                                                                                                                                                             |
| **OX Action** | The outcome of VibeSec's review. See [OX Action values](https://claude.ai/local_sessions/local_bb9ccf4d-71c0-4c3b-93d0-7cab12db0975#ox-action-values).                                                                                |

#### OX Action values

| Value                           | Description                                           |
| ------------------------------- | ----------------------------------------------------- |
| **No guidelines needed**        | VibeSec reviewed the prompt and no guideline applied. |
| **Security guidelines applied** | A security guideline was returned for the prompt.     |
| **Tool validated**              | The tool call was reviewed and no policy blocked it.  |
| **Tool blocked by policy**      | A policy was triggered and the tool call was blocked. |

## Filtering activity

The filter panel is shown by default at the left side of the page. Select **Hide Filters** to collapse it.

Each filter section has a search box, a checkbox for each value, and a count of matching activities next to each value. Counts update as you apply other filters.

| Filter            | Description                                                       |
| ----------------- | ----------------------------------------------------------------- |
| **Activity Type** | Filter by the type of action, such as **Prompt** or **Tool Use**. |
| **OX Action**     | Filter by the review outcome shown in the **OX Action** column.   |
| **Source**        | Filter by the AI coding tool that originated the action.          |
| **User**          | Filter by the user who performed the action.                      |

## Activity details

Select an activity to review how VibeSec evaluated it and what action, if any, was taken.

Depending on the activity type, OX displays either **User Prompt** details or **Tool Use** details.

### User Prompt details

Select a **User Prompt** activity to review how VibeSec evaluated the prompt and whether security guidance was provided to the agent.

<figure><img src="/files/G1pCu4inMjbifhqszrho" alt="" width="563"><figcaption></figcaption></figure>

<table><thead><tr><th width="194.8333740234375">Section</th><th>Description</th></tr></thead><tbody><tr><td>Status card</td><td><p>Shows the outcome of VibeSec's review.</p><p>For example, <strong>Security guidelines provided</strong> indicates that VibeSec returned security guidance to the agent.</p></td></tr><tr><td>Event Metadata</td><td><p>Displays technical details about the prompt event, as follows:</p><ul><li><strong>Model:</strong> The AI model associated with the event, when available.</li><li><strong>Application:</strong> The application associated with the event, when available.</li><li><strong>Event ID:</strong> A unique identifier for the event.</li></ul></td></tr></tbody></table>

### Tool Use details

Select a **Tool Use** activity to review how VibeSec evaluated the tool invocation.

<figure><img src="/files/TeXvBZ7fKfAdQSMb7I6b" alt="" width="563"><figcaption></figcaption></figure>

<table><thead><tr><th width="222.3333740234375">Section</th><th>Description</th></tr></thead><tbody><tr><td>Status card</td><td><p>Shows the outcome of VibeSec's review.</p><p>For example, <strong>Tool validated</strong> indicates that the tool invocation was reviewed against active policies and allowed to proceed.</p></td></tr><tr><td>Event Metadata</td><td><p>Displays technical details about the tool use event, as follows:</p><ul><li><strong>Model:</strong> The AI model associated with the event, when available.</li><li><strong>Application:</strong> The application associated with the event, when available.</li><li><strong>Tool Type:</strong> The category of tool that was invoked.Tool: The tool that was invoked.</li><li><strong>Event ID:</strong> A unique identifier for the event.</li></ul></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ox.security/vibesec/agent-activity-log.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.