Ask Sai
Sai is the assistant that travels with you. Open it on any page and ask about what you are looking at: it reads the page, so you do not have to explain where you are.
Audience: all personas
When these docs do not cover something, ask Sai. These docs cover the core of the platform. For a question about a specific screen, a Workflow that is not behaving, or a surface that is not written up yet, Sai is the faster answer, and it knows your workspace rather than the general case.
Open it
Sai is a side panel, not a page. It is always one click or one shortcut away.
- The Sai tab. On the right edge of the platform, a tab reads "Ask Sai about this page". Click to open the panel.
- Ctrl+J or Cmd+J. Toggles the panel from the keyboard. The same shortcut closes it.
- Escape closes the panel when it is open.
The panel opens on the right. The page stays visible on the left, so you can keep working while you talk.
What it knows
Sai reads the page you have open. It knows which Project you are in, which surface you are on, and what is in front of you.
That is why "why is this blocked?" works as a question. You do not have to name the Work item.
When you open Sai on a page it has suggestions for, it offers them as starting points.
What it can do
- Answer questions about what you are looking at. "What does this Workflow do?" "Why is this Work item blocked?" "Which integrations are bound here?"
- Explain the platform. "What's a semantic model?" "What's the difference between a Memory and an Instruction?"
- Help you find things. "Where do I configure triggers for this Workflow?" "Take me to the audit entry for the latest run."
- Build things with you. Describe what you want and Sai can author it: a Workflow, a custom view, a Skill, a Memory, a piece of verified logic.
- Make changes you review. When Sai produces edits to files, the panel shows them for review. You apply or discard. Nothing lands without you.
Build something new from Home
When no Project is open, as on Home, describing work you want to build, automate, or set up counts as asking for a Project. "I need help building an invoice exception process" is enough. Sai creates the Project right away and names it from your words. It asks at most one short question first, and only when it cannot name the Project or cannot tell which team should own it.
When its reply is finished, you land in the new Project with the conversation copied into the Project's chat and the assistant panel open. The work continues there, where the Project's files and Workflows live. See Chat with a project.
The Sai panel cannot take attachments. Add your documents, such as SOPs or policies, in the new Project. The Project's agent can then build a Workflow from them that keeps every rule they contain: it reads every source, settles open questions with you, and checks the Workflow against each rule before it calls the build done.
Getting a better answer
Sai already knows where you are, so spend your words on what you want instead.
- Say what you are trying to achieve, not just what is wrong. "I want vendors to get a reply within an hour" gets you further than "this is slow".
- Say what you already tried. It saves being walked through it again.
- Ask it to explain before it changes. "What would you change to make this work?" gets you a plan you can read, rather than a diff you have to reverse-engineer.
- Correct it in the same conversation. It has the page and the previous answer in front of it.
Sai threads stay separate. Conversations with Sai are pinned to the Sai panel. They do not mix with the shared threads in your Projects, so asking Sai how something works does not clutter your team's record of the work. The exception is a request to build something with no Project open: Sai creates a Project and moves that conversation into it.
Where Sai is not available
Sai is deliberately hidden on a few surfaces, such as logged-out screens and a small set of administrative routes. There the tab does not appear and the shortcut does nothing.