Yuna tasks collect events that need attention. Yuna long-term memory reduces repeated instructions across your merchant-team conversations.

Yuna tasks#

Common tasks include pending learning, failed AI runs, channel delivery failures, skill regression tests, and proactive outreach confirmations. Selecting a task should open the relevant detail page. Ignoring a task changes the reminder state; it should not erase the original log or business record.

Handled and ignored tasks remain available in task history. The Inbox is a reminder surface, not the only source of audit history.

Yuna long-term memory#

Yuna can remember:

• workspace-wide reporting and operating preferences;
• expression or workflow preferences for the current team member;
• confirmed context that is useful across sessions.

Use the Yuna memory page to view, correct, delete, or clear a scope. Repeated wording for the same preference is merged into one record. A clear and newer preference automatically replaces the old value, which remains in version history. If a new statement is ambiguous, Yuna keeps using the current trusted value instead of waiting for manual approval or letting uncertain content overwrite it. Invalidated records remain visible only as history and no longer affect Yuna.

You can also tell Yuna, “Remember that I prefer ...” in the conversation. Yuna saves it as your personal preference by default. It becomes a shared preference only when you explicitly say that it applies to the team or workspace. If saving fails, Yuna says it was not remembered instead of reporting success.

Memory is available by default to support answers. When memory is temporarily unavailable, Yuna should continue working and explain the limitation.

What not to store#

Prices, refund rules, customer commitments, and standard response policies must be managed through knowledge or improvement suggestions, not only in Yuna memory. Customer preferences belong in customer memory. Never store passwords, keys, or payment information.