---
schema_version: "1"
id: 13515045c43ce0ff429c791a8bb5112dcd6837271ca1d4ebbe976bda613d79e1
title: Viewing Conversation History
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/anypoint-code-builder/vibes-conversation-history.md
canonical_url: https://docs.mulesoft.com/anypoint-code-builder/vibes-conversation-history
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 9c63830038226227128b9305de5e874b4a09a70544ba9181b41d7cafdc937ea9
description: MuleSoft Documentation Site
latest: true
---
---
product: Anypoint Code Builder
version: master
---

# Viewing Conversation History

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

MuleSoft Vibes allows you to return to tasks you have previously started and continue working from
where you left off.

To open a recently started task:

1.  In the MuleSoft Vibes panel, locate the **Recent Tasks** section.

2.  Select the task you want to reopen.

If the task is not listed under Recent Tasks:

1.  Click **View All History**.

2.  Use the search bar to find a specific task, or browse your full history list.

You can sort tasks by:

- **Newest**

- **Oldest**

- **Most Tokens**

- Other available criteria

You can also filter tasks by:

- **Workspace**

- **Favorites**

To favorite a task, click the **Star** icon next to the task entry.

## Delete History

You can remove past tasks in two ways:

- **Delete specific tasks** – Deletes the specific tasks you select.

- **Delete all history** – Clears all tasks.

## Reduce Token Usage with Chat History Summaries

MuleSoft Vibes automatically summarizes conversation history to reduce total token consumption while
preserving relevant context.

As tasks grow in complexity, conversation history becomes larger. Instead of sending the full
history with each interaction, Vibes compacts previous messages into summaries. This maintains
performance and reduces tokens usage.

Chat history summaries:

- Preserve the intent and key decisions from earlier steps

- Reduce redundant context sent to the model

- Keep interactions fast and efficient

Vibes manages this process automatically. You don’t need to manually trim or rewrite previous
messages to optimize token usage.

Even with automatic summarization, a conversation with a clear, bounded scope gives Vibes more
useful context than one long thread covering unrelated work. If your work spans several distinct
tasks, such as scaffolding a project, configuring connectors, and writing DataWeave transformations,
start a new conversation for each one instead of continuing the same thread, so Vibes doesn’t keep
the full context for changes unrelated to the current task.