> ## Documentation Index > Fetch the complete documentation index at: https://docs.novacula.io/llms.txt > Use this file to discover all available pages before exploring further. # AI Assistant > Occam, the in-product chat helper — what it does and how it stays safe **Occam** is an in-product chat assistant that lives in the bottom bar of the Dashboard UI. Use it to ask about your fleet, find the right screen, draft a form before you submit it, or get pointed at the matching docs page. Occam reads — it never changes your fleet on its own. The only action it can take is filling a form you already opened, and only after you confirm; it never clicks **Next** or **Deploy** for you. Occam is available to every signed-in org role — Org Owner, Org Admin, Org Member. It does not appear in the Admin Panel. ## Open Occam Click **Ask Occam** in the floating bar at the bottom-right of any Dashboard route, or press **⌘+J** (macOS) / **Ctrl+J**. A chat panel docks above the bar. The maximise toggle in the panel header expands it to a full-height side panel; **Esc** shrinks a maximised panel back to docked, then hides it on a second press. Closing the panel does not end the active conversation — re-opening returns you to it. ## Send a message Type into the prompt input at the bottom of the panel and press **Enter** (or the send button). Responses stream in as Occam composes them. The input is disabled while a reply is in flight. A blank conversation shows **quick prompts** as one-click starters: * **Check system status** — a short fleet summary plus suggested next actions. * **Create node** — walks you toward deploying a node. * **Add a user** — opens the invite-member dialog directly. Quick prompts either send a prompt straight away or run a navigation action. ### Occam sees the screen you're on Occam reads the current page and the active tab, so prompts like *"explain this screen"* or *"open the logs tab"* work without you spelling out where you are. It works from **your session**, so it can only see and reach what your role already lets you access. ## Tool calls and confirmations Occam can pull read-only data about your org — current node and executor status, events, and incidents — to answer a question. Reading data needs no confirmation. (Metrics/telemetry history is not yet wired and returns no data.) The one thing Occam can do beyond reading is **fill a form for you**. When it offers this, a card appears in the panel: * It states exactly how many fields it will fill, with a **Fields** disclosure listing each value. * Nothing happens until you click **Fill form**. * After filling, you review the values and continue manually. **Occam never clicks Next or Deploy** — the final submit is always yours. That is the whole safety model: Occam reads, navigates, and pre-fills; you confirm and submit. If the panel isn't asking you to confirm, the action is read-only. ## Sources When an answer draws on a specific node, event, or screen, Occam attaches **Sources**. Expand them to jump straight to the screen behind the data — for example, the node details page a status came from. Sources turn an answer into a starting point for your own investigation. ## Switch and delete conversations The history popover (clock icon) in the floating bar lists every conversation you've started, newest first, with a **Search chats** box to filter by title or last message. From there you can: * **Start a new chat** with **New** — the current conversation is preserved, not deleted. * **Switch** to an earlier conversation by clicking it; its messages load back into the panel and you continue in that context. * **Delete** a conversation with the per-row trash button (asks to confirm). Deleting the active conversation resets the panel to an empty chat. The active conversation is remembered across navigation and page reloads, so re-opening Occam returns you to where you left off. ## What Occam can do * Answer questions about your fleet from read-only data — current executor and node status, events, and incidents. * Open the right screen or node tab, and highlight the field worth rechecking. * Pre-fill a form for your review (gated by **Fill form**; it stops before submit). * Walk you through a flow — *"how do I rotate an executor API key?"* — and link to the matching docs page. * Cite [Sources](#sources) inline so you can jump to the screen behind an answer. ## What Occam won't do * Change your fleet without you confirming and submitting yourself — it never clicks **Next** or **Deploy**. * Act outside your permissions. An action you couldn't perform yourself is one Occam can't perform for you; it can't escalate access. * Operate from the Admin Panel — it is Dashboard-UI only. * See more than you can. It uses your session and is scoped to your active org. ## Privacy and data handling Conversations are stored server-side and scoped to **your user within your organization** — they're private and not visible to other members. Deleting a conversation removes it from the server. Occam receives only what it needs to answer: your message stream plus the read-only context and data it resolves for the active org. For a form-fill, the exact field values are shown in the panel before you click **Fill form**. ## Permissions * **Open Occam and chat** — Org Owner, Org Admin, Org Member. * **Anything Occam fills or opens** is bounded by your own role. Occam acts as you, never above you.