# Mina In-App Assistant

**Mina** is OmnyBot's built-in AI assistant. Mina answers product questions grounded in the app documentation and can directly execute workspace operations — searching or updating the Knowledge Base, checking channel health, reading unread conversations, managing AI bots, and organizing tags — strictly scoped to your workspace permissions.

:::note[Access & Plan Availability]
- **Every workspace member** on **every plan** can chat with Mina for product Q&A (workspace membership is the only requirement).
- **Knowledge Base write tools** and bot management require **`workspace:manage`** plus the plan's `aiReply` capability. Other action tools (reading conversations, managing tags, inspecting channel health, connecting accounts) are exposed only when your role grants the matching workspace permission.
:::

## Where to Access Mina

You can interact with Mina from three places:

1. **Home (`/{slug}/`)** — The default workspace landing page features Mina directly.
2. **Full-page Agent (`/{slug}/ai-chats` and `/{slug}/ai-chats/{threadId}`)** — Open **Agent** in the left sidebar for dedicated full-screen sessions and conversation history.
3. **Right-hand Side Panel** — Toggle Mina from any page in the app. On desktop, drag the left edge to resize the panel (**360px** to **1100px**); on mobile, it opens full-screen. Reopening the panel archives the previous conversation to history and starts a fresh thread.

## Modes, History & Live Progress

- **`Agent` vs. `Ask` Mode**: Switch modes directly in the composer (defaults to `agent`, persisted per browser).
- **Conversation History & Feedback**: Reopen past threads from history (`/threads`, `/threads/:id/activate`), lazy-load older messages, and rate replies (**helpful / unhelpful**).
- **Real-Time Streaming (SSE)**: Mina streams tool execution steps and progress live as it works.

## Supported Tool Belt

Depending on your permissions, Mina can invoke the following tool groups:

| Tool Group | Key Capabilities |
|---|---|
| **Product Support** | `search_docs` — searches OmnyBot documentation using the context of the page you are currently viewing |
| **Knowledge Base & Gaps** | `search_knowledge`, `read_knowledge`, `create_knowledge`, `batch_create_knowledge` (up to 15 articles per batch), `update_knowledge`, `delete_knowledge`, `crawl_website_knowledge`, `manage_kb_collection`, `review_knowledge_base`, `list_gaps`, `resolve_gap` |
| **AI Bot Management & Testing** | `manage_ai_bot`, `test_bot_reply` |
| **Channels & Conversations** | `nick_health` (status, errors, and unread counts for Zalo, Facebook, WhatsApp), `read_unread_conversations`, `read_conversation` (read or search inside a specific chat), `connect_account` (renders inline channel/QR connection options) |
| **Tags** | `create_tag`, `rename_tag` |

:::note[Knowledge authoring limits]
When Mina writes a Knowledge Base item (`FAQ`, `POLICY`, or `PRODUCT`), titles are capped at **200 characters** and content at **8,000 characters** to keep vector retrieval accurate.
:::

## Confirmation & Undo

- **Approval before writes**: For mutating tools configured to **Ask (`ask`)**, Mina summarizes the pending action and waits for your approval or rejection before executing. Per-tool permissions (`always` / `ask` / `deny`) are shared with [AI Connections (MCP)](/mina-mcp/mcp-server/).
- **Undo**: Applied write actions (`APPLIED`) display an action card with an **Undo** button (`POST /actions/:id/undo`) to revert the change. Connection flows such as QR login (`NICK_QR_LOGIN`, `NICK_CONNECT_OPTIONS`) are not undoable.

## Default Daily Safety Quotas

To prevent runaway loops or unintended overuse, Mina enforces daily Redis-backed limits (configurable via server environment):

- **Messages per user / day**: **300** (default)
- **Messages per workspace / day**: **1,000** (default)
- **Total tokens per workspace / day**: **5,000,000** (default)
- **Write operations per workspace / day**: **200** (default)
- **In-chat QR login starts**: up to **5 per 10 minutes** per user