> For the complete documentation index, see [llms.txt](https://help.tellius.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.tellius.com/tellius-6.4/whats-new/release-6.4-legacy/patch-6.4.1.md). # Patch 6.4.1 Tellius 6.4.1 introduces custom roles, so administrators can decide, module by module, what each role can reach. Kaiya usage is now reported as cost, Missions and Apps can read from and write to the systems you have connected, and Industry Packs give teams ready-made templates to start from. Kaiya chat confirms before switching Business Views and follows the calendar set on each Business View, with many refinements to how answers, files and progress appear in the conversation. Tellius Mobile for iPhone, iPad and Android gets a new design and a dedicated iPad layout. ## **🚀 New features** ### **Custom roles** Administrators can now create their own roles and set, module by module, what each role can reach. Roles are managed under **Settings → Workspace → Users & Access → Roles**. Select **Create role**, enter a **Role name** and **Description**, and set the access level for each module. * **No Access.** The module is not directly available to the user. * **Read Access.** The user can view and use existing content without modifying it. * **Full Access.** The user can use all supported functionality in the module. Modules are grouped into Kaiya (Chat, Apps, Missions, Context), Analytics (Vizpad, Predict, Insight, Search, Feed), Projects, Collaboration (Sharing), Data (Datasets, Business Views, Data download, Connect source) and Administration (Own settings, Manage workspace, Manage system, Content management). Sharing, Data download, Connect source, Manage workspace, Manage system and Content management offer No Access or Full Access only. Own settings is fixed at Full Access for every role. * A role's module access can only restrict. It narrows what the role can already do and never adds to it. * When you turn on a module that needs another module to work, the Roles screen raises that module to the level required and locks it, with a note naming the module that needs it. For example, turning on Missions also raises Kaiya and Data. * Assign a role from the **Role** dropdown when you edit a user, which lists custom roles alongside the built-in ones, or assign it to a group. A new group starts with no role. * When a user receives access from more than one assignment, such as their own role and a group's role, the highest level for each module applies. * The Roles page lists each role with its type, how many modules it restricts (or **All modules**), and how many users and groups hold it. Built-in roles show as **System**. * The **View effective access** dialog shows each module's level for a user and the role that granted it. Open it from **My Profile**, beside **Roles in effect**, or from a user's row menu on the Users page. * A custom role can be the default role for single sign-on. Who can share content and who can use Kaiya Context is set for each role with the Sharing and Context modules, which replace the earlier Kaiya Context settings. A new custom role starts with No Access to both, so give it access as needed. * Changes to a role apply the next time the user loads a page. ### **Kaiya usage shown as cost** Kaiya usage is now reported as cost in place of credits. Tellius records the model and token counts for each Kaiya call and works out cost from each model's rates when you view the report, so a corrected rate also updates past cost. Find it under **Settings → Intelligence → Kaiya & AI → Kaiya Cost**. * The **Monthly Usage** tab shows total cost, cost by area and by model, and lists any models that have no price yet, so you can add their rates. * On the **Model Pricing** tab, Super Users can add a model, set its input, cached input, cache write and output rates per million tokens, and add other names for the same model. * Tellius includes default rates for common Anthropic, OpenAI and Gemini models. ### **Exports from Kaiya and Missions** * Ask Kaiya, in the conversation or in a Deep Insight, to export the analysis as a PowerPoint deck, PDF report, Word document, Excel workbook or CSV file. If you don't name a format, Kaiya asks which one you want. Decks, PDFs and Word documents carry your configured logo. * When a result holds more than one table, an Excel export puts each table on its own sheet, and for a CSV Kaiya asks which table to export. * CSV and Excel files open in an in-app preview. Excel previews show sheet tabs and zoom. CSV previews show the first 1,000 rows, with a note to download the full file. * A Mission can include several export steps, so one run can deliver a PDF report together with several CSV files. Export steps produce PowerPoint, PDF, Word, Excel or CSV files, and Mission Preview shows every file the run produced. * Export is offered once any clarification is answered and the Deep Insight completes. While an export is being prepared, the Export action is disabled, so each request is exported once. ### **Missions and Apps work with your connected systems** Missions can read from and write to the systems you have connected, such as Snowflake, Slack, Salesforce, Gmail, Notion, Microsoft 365 or an MCP server your administrator adds. * A connected-system step sits in the Mission plan beside SQL and Python steps. It can pull live data into the Mission or write results out, for example by inserting rows into a Snowflake table. * Writing is off by default. The Mission owner turns it on for each step in **Manage access** with **Allow it to send, post and create**. * **Run as** sets whether the step uses the connection of whoever runs the Mission (the default) or always the Mission owner's. In 6.4.1, scheduled runs can read from connected systems but can't write to them yet, and a step set to run as the owner works only when the owner runs it. * Each step card shows what was asked, the calls that were made, and whether the write succeeded. * Deep Insights can also read from connected systems, and the **MCPs** tab under **Settings → System → Administration → Integrations** shows the callback address to register with your provider. Apps can read data from your connected systems and write back through buttons in the App, for example to create a record or a calendar event. Each write is confirmed on screen before it runs, and an App action that runs under its creator's connection needs approval first. Apps can also use unstructured data, such as indexed documents, as a step. ### **Industry Packs** * Super Users can turn each pack on or off for the workspace, and administrators see the setting as read-only. Pack content is read-only. * Skills that come with an enabled pack apply automatically to matching Business Views. * Generate a first version of a Mission or App from a pack template. The result is your own copy, so later updates to the pack leave it unchanged, and Tellius lists any parts of the template it left out of the build. * When you select Business Views for a template, Tellius checks how closely their fields match. Depending on the match, it continues, names the fields and sections that will be left out, or stops before building. * A Patient Service App is now available as a template. * Pack names are validated, and the description field takes multiple lines. Packs with no content are flagged. ### **Citations in Mission Preview** Mission Preview offers on-demand citations. Open them to see where each number in the output came from or how it was derived, with each figure marked **Verified** or **No source**. Citations are generated only when you request them in Mission Preview, never during scheduled runs. ### **A redesigned Context page** The Kaiya Context page is organized into two layers, **Skills** and **Memory**, each shown as a card with its count. A panel shows how many phrase learnings have moved to Memory and how many remain. Beside it, **Support details** lists the last attempt, the number of attempts, the reason and a reference, with **Copy details** and **Contact support**. A read-only **Legacy learnings** tab appears while phrase or query learnings remain outside Memory. ### **Tellius Mobile** Tellius Mobile is the Tellius app for iPhone, iPad and Android. Sign in to your Tellius workspace with your username and password or your company's single sign-on, then ask Kaiya about your data and follow your Missions and Apps from your phone or tablet. The app also supports Face ID or fingerprint app lock, voice dictation, sharing with people and groups, and reading recent chats while offline. This release brings the following to Tellius Mobile. * **A new design.** The app is organized into three tabs: **Today** for what's new, **Library** for Missions and Apps, and **History** for every conversation. Loading placeholders appear while content arrives, and a confirmation appears when you save. * **Built for iPad.** On iPad, a sidebar or icon rail sits beside every screen. Missions and Apps open next to their list, answers open on a canvas beside the conversation, and History uses a table layout. * **Five languages.** The app is available in English, Spanish, German, French and Portuguese (Brazil). It follows the language set in your profile and updates every screen at once. You can edit your name and language from your profile in the app. * **Today.** Today shows your latest briefing first, tells you when you're caught up, and lets you pick up where you left off. One ask box handles questions and builds, with suggestions to start from. Choose **Quick answer**, **Deep Insight**, **Build a mission** or **Build an app**, and choose the data to use. * **Talk with Kaiya.** Kaiya reads its answer aloud, then listens for your next question, so you can keep the conversation going hands-free. Mute, stop Kaiya speaking or end the conversation at any time. Speech is processed on the device. * **Answers.** Switch a chart between Bar, Line, Pie and Table. Wide tables scroll sideways rather than squeezing their columns. Visual summaries, Kaiya's interactive chart pages, open in the app. * **Files from answers.** Reports, decks and spreadsheets Kaiya creates appear under the answer that made them, with their versions, such as "PDF export · Version 2". Every file in a chat is also listed in **Files in this chat**. * **Attachments.** Photos and files you attach to a question appear as pictures and file cards, including when you reopen the chat. Tap one to open it. * **Briefings.** Each Mission run has its own briefing page with Kaiya's thought process, the summary, an interactive visual summary and every file the run produced. Open it from Today, from a Mission's run history or from a notification. A run picker lets you move between runs and shows the success rate and average run time. * **Missions.** The Library lists Published and Draft Missions, with search, sort and an access filter. A Mission's page shows its status and stats, with **Run now** and **Publish** or **Unpublish**, and lists its steps so you can see what it does. * **Scheduled missions.** See every schedule you created or that is shared with you in one place, filter by **All**, **Created by me** or **Shared with me**, and search. You can subscribe, edit or delete a schedule. Open it from **Library → Missions** or from **See all** on a Mission. * **History.** History lists the same conversations as the web: chats, App builds, Mission builds and Mission runs, newest first. The **Show** filter offers **All chats**, **Favorites**, **My chats** and **Shared with me**, the **Type** filter offers **Chat**, **Mission** and **App**, and one tap resets both. A chat you star shows as a favorite everywhere. * **What Kaiya remembers.** You can now edit the text of a memory, as well as add, turn off or forget one. * **Workspaces and sign-in.** Stay signed in to several workspaces and switch between them. Password managers, such as Bitwarden, iCloud Keychain and Google, can fill in your sign-in. * **Links.** On Android, shared Tellius links to chats, Missions, Apps and Home open in the app. On iPhone and iPad, paste a Tellius link into the ask box to open it. When a link belongs to another workspace, the app offers to switch workspaces, open the link in your browser or cancel. * **Account.** You can request deletion of your account from the app. ## **📈 Enhancements** ### **Kaiya chat** 1. When you ask Kaiya to create a Mission or an App from the conversation, it opens in its own conversation in the Mission or App builder, with a summary of the context it carries over. To keep working in the same conversation, ask Kaiya to do so. 2. Kaiya works only with the Business View you selected. When a question needs another Business View, Kaiya asks whether to switch to it or stay on the current one, and switches only after you confirm, unless the view it needs is soft-linked to the current one, in which case Kaiya adds it without asking. After a switch, the Business View picker shows the new view and follow-up questions use it. 3. Improved how Kaiya finds the Business View for a question. When several could answer, it checks the Business Views you can access before asking you to choose, and avoids offering unrelated ones. 4. When Kaiya asks which source to use, typing the name of a Business View you can access selects it, just as choosing it from the list does. 5. Conversations from earlier releases open in Kaiya chat. Earlier answers, including charts and Deep Insight results, appear read only, with a link to the classic view for anything Kaiya chat does not display. Opening a Mission or App built in an earlier conversation continues it in Kaiya chat with its history, and a conversation linked to a Mission or App has an **Open Mission**, **Open App** or **Show Artifact** action to return to it. 6. Stop a response while Kaiya is working and continue the conversation later. 7. In an App build conversation, suggested follow-up questions and actions appear as two groups, follow-up questions and actions. Selecting a question asks it in the conversation, and selecting an action starts it. 8. Follow-up questions show a short description and give you space to type your own answer. 9. Hover over a message to see when it was sent, such as "7 minutes ago", and hover over the time to see the exact time. A copy icon sits beside it for your own messages and for Kaiya's answers. Copying an answer copies all of it, and the icon briefly shows a check mark. 10. The total time for a response sits inside the Thought Process, beside the time for each step. While Kaiya works, the header shows **Working…** with a Stop button. 11. Refined how Kaiya writes its answers, so notes about its next steps stay out of the answer and the answer starts with the results. 12. File type restrictions are removed from every place you can attach files in Kaiya, including the chat composer, the Home page composer, the Insight Apps sidebar and Kaiya Architect chat. Each accepts the same file types: images, PDF, Word (DOCX), Excel (XLSX and XLS), PowerPoint (PPTX), and CSV, TXT, LOG, JSON, HTML, HTM and MD files, up to 20 MB each. Each file you attach appears in the message you sent, including after you reload the page or reopen the conversation. 13. Kaiya reads the text in attached PDF, Word, PowerPoint and HTML files, and reads each sheet of a spreadsheet separately. 14. Kaiya works out periods such as "this week" or "last month" from the calendar set on the Business View, including fiscal and custom calendars, and measures them from the latest date in the data. No new setup is needed. 15. Weekly results label each week with its week-ending date, such as Dec 01, 2024, and list weeks in date order. To see ISO week numbers such as 2024-W01, ask for them or add a custom skill. 16. Kaiya chat uses your saved memories across conversations. With each message it looks for relevant memories, and it asks for your approval before saving a new one. Kaiya can also suggest a takeaway from the conversation to save to Memory. 17. Kaiya can check the numbers in an answer or a Mission output by running its own queries, trace where a difference comes from, and update the Mission steps so the output matches what you asked for. 18. Super Users and Content Admins can open another user's conversation, including its files and Rich Summary, and select **Continue this conversation** to carry on in their own copy. The files also open for users the conversation is shared with. ### **Deep Insights** 1. A Rich Summary appears as a **Visual summary** card in the conversation. While the summary is being built, the card reads "Preparing summary…", and you can select it as soon as the summary is ready. The side panel opens only when you select the card, including for export cards and when you return to a conversation. 2. Deep Insight progress is shown in one place while the analysis runs. ### **Missions** 1. When a Mission with input steps runs from the conversation, Kaiya asks you for each value, such as a region or a threshold, and offers the step's default as the first option. Selecting **Run** still asks for these values. Scheduled runs use the value saved with the schedule, or the default. 2. Run a Mission by asking Kaiya for it by name, or select **Run** on the Briefing page or a Mission Library card. **Run** opens a new conversation and runs the published Mission straight away, and the Briefing page shows runs made from Kaiya chat. 3. Opening a draft Mission from the Mission Library or the Home page takes you to the conversation it was built in. A published Mission opens its own page. On an App's page, the chat icon opens the App's conversation. 4. A Mission run from the conversation shows **Working…** with live progress while it runs. 5. Weekly grouping in Missions and Kaiya chat uses the Business View's custom calendar. If that calendar doesn't cover the period you asked about, Kaiya says so in the answer, with both date ranges and the week convention it used instead. 6. Mission schedule times are shown in your browser's time zone, including when Kaiya confirms a schedule or reports a run time in the conversation. 7. On the Scheduled Missions page, the Mission and User filters load more results as you scroll, and search and A to Z sorting apply across all Missions and users. The Mission filter lists scheduled Missions, and choosing a user narrows it to that user's Missions. The Mission picker in the schedule form also loads more Missions as you scroll. 8. When you create a schedule from **Missions → Schedules**, the Mission dropdown lists published Missions from the Modern view, both your own and those shared with you. 9. In a Mission's Business View dropdown, the selected Business Views appear at the top. 10. In the classic Mission compose view, **Approve & Run** stays available after the plan is generated, so you can run a preview and then publish. ### **Kaiya Apps** 1. After Kaiya saves an App, it views the App the way you would, screen by screen and tab by tab, and checks for blank values, charts that drew nothing, overlapping charts and content that overflows the page, so it can correct what it finds in the same turn. 2. When Kaiya finishes building an App in the conversation, the side panel shows the App on its own. A later change that creates a new version shows a notice with an option to view it. 3. The App page has a refreshed design, including the Plan and Analysis tabs, the Publish dialog, and the version and refresh schedule menus. 4. Long App titles stay on one line with an ellipsis, so the creator and last-updated time stay visible on App cards. ### **Kaiya Architect** 1. A Business View that joins several sources, including two fact tables with their dimensions, can be built and validated in the conversation. When the sources are not all joined, Kaiya Architect names the datasets in each separate group so the joins can be fixed, and a direct join between fact tables on a unique key is allowed with a note. 2. When two or more fact tables share a dimension in one model, Kaiya Architect stops before publishing, shows the shared dimensions and asks how you want to resolve it. 3. Kaiya Architect has a refreshed design across its chat, sidebars, tabs and Browse Data dialog. ### **Data and administration** 1. Data source swap works across source types, for example Snowflake to Redshift, Redshift to Snowflake, or MySQL to Microsoft SQL Server. Before the swap, Tellius checks that the columns match and lists any that don't. It asks for the details the target source needs. For a database source, you choose a load method: DB Table with the table name, or Custom SQL. For AWS sources, you enter a storage path. A tooltip notes that Vizpads, Insights and Predict models built on the dataset may be affected. 2. When you import content and map a dataset or Business View to an existing one, the mapping is accepted when the target holds every source column by name, even if it has extra columns. Column order doesn't matter, and Tellius names any source columns the target lacks. 3. Kaiya uses the model provider and settings configured for your workspace. A custom endpoint or custom headers set on an Anthropic, OpenAI, OpenRouter or Gemini model connection are applied to Kaiya, so requests go through your own gateway. Add the endpoint in the **Model Parameter** JSON and any headers in **Default Header**. 4. Refined the Content Admin experience. Content Admins can create folders and import Business Views and Datasets, use dataset tools such as scripting, data fusion, schedules, and Python and SQL transforms on other users' datasets, export those datasets, and see all users' content on the Connect and Refresh Pipeline tabs. "Author" filters are renamed "User". 5. Kaiya Semantic Views can be managed from the interface. ### **Home page** 1. The Home page has **Your Missions** and **Your Apps** sections. Your Missions shows today's completed Mission briefings first, then Missions that have not run today. Your Apps shows your most recently updated published Apps, including Apps shared with you, with a count of any more. 2. A new page lets you browse your saved queries, filter them by category or Business View, and load one into the composer. 3. Select the search icon in the home page ask box to search across your content. Results are grouped into tabs for Kaiya conversations, Vizpads, charts, Insights, Business Views and settings. 4. **Suggested for you** lists the most recently updated items first, and each card opens the matching Mission or App. The notification count shows on the icon when the sidebar is collapsed. ### **Platform** 1. Expanded automated testing for Kaiya, Deep Insights and Kaiya Architect, added load testing for many concurrent conversations, and refined the infrastructure and usage tracking behind them. ## **🛠️ Minor fixes** ### **Kaiya chat** 1. Improved how Kaiya joins tables on keys that span more than one column, so counts stay accurate. 2. Ensured that Custom Skills are applied when Kaiya runs a query. 3. Resolved an issue where an earlier message could keep showing **Working…** after you sent a new one, so each message shows its own state. 4. Refined the stop action so it ends the active response, and the message shows **Response stopped**. 5. Ensured that each result shows the name of the Business View its query used, including after you switch Business Views and after a new Business View is created and published in the conversation. The name appears in the "Based on…" label right away, without a page refresh. 6. Ensured that results show the Business View you selected, rather than "Auto-detect". 7. Resolved an issue where Kaiya could report a Business View you can access as unavailable, for example when it has no description. Kaiya now finds Business Views based on your access, so it uses them without asking you to enable access. 8. Refined the review status so it shows the final result once an automatic retry succeeds. 9. Improved the elapsed-time counter so it keeps counting from the start of the response when you collapse and expand progress. 10. Improved SQL output so it displays in a readable code format, and **Copy Code** confirms when the copy succeeds. 11. Refined chart rendering so charts display without flickering and resize with the layout. 12. Refined chart sorting so values follow the measure on the Y-axis rather than the alphabetical order of the labels. 13. Removed the **Open reviewer session** option from reviewer output. 14. Refined how Excel and CSV exports display in the side panel, and ensured that image previews display. Follow-up questions and actions match the standard Kaiya layout, and HTML files can be previewed. 15. Ensured that the export preview card appears in the conversation once a Deep Insight or export completes. 16. Refined the export view so its title sits clear of the action icons and the view can be closed. 17. Improved scrolling when loading older messages, so the view stays at the message you were reading instead of jumping to the top or bottom. 18. Ensured that conversations opened from the **Recent** list in the sidebar open in the current Kaiya chat. 19. Opening a conversation that has not been shared with you shows a message naming its owner, so you can ask them to share it. 20. Refined the alignment of the arrow in the plan approval input, and the spacing between the Assistant and Send controls. 21. Improved how formatted text in Kaiya responses and citation details is handled, so the page keeps showing your content. 22. Resolved an issue where images attached in the conversation or in Apps were ignored by models from providers other than Anthropic and Amazon Bedrock, such as OpenAI, Azure, Gemini and OpenRouter models. 23. Improved how the Mission page handles an interrupted query, so the page stays available. When Kaiya is briefly unavailable as you start a new conversation, your message goes back into the chat input with your selected Business Views, and a notice asks you to try again in a moment. ### **Deep Insights** 24. Ensured that a long Deep Insight shows its progress without a generic "contact support" message while the analysis is still running, including when it pauses to ask a clarifying question. 25. Improved how Rich Summary pages load, so a Deep Insight's Rich Summary displays when it is ready and shows the selected Business View name. 26. Refined Rich Summary layout. Every page has the same even padding in the side panel, and new Rich Summaries use the same text sizes as the conversation. 27. Ensured that the "Based on" label uses the same capitalization throughout the Thought Process. ### **Missions** 28. Ensured that creating a Mission from a Deep Insight conversation creates a single draft Mission. 29. Refined Business View selection when creating a Mission, so the prompt clears once you choose and the processing steps appear. 30. Improved the Mission conversation so you can add more context as soon as a response finishes or is stopped, without refreshing the page. 31. Improved access handling for Mission queries that join two Business Views you can access. 32. Ensured that each chart in a Mission run appears once. 33. Ensured that a Mission published from the conversation shows as Published in the conversation, in its configuration and in the Mission Library, where its version is marked Active. 34. Improved publishing a Mission from the conversation. Kaiya asks you to confirm with **Publish** or **Not now**, and Python steps run on scheduled runs too, so they don't hold up publishing. After a successful preview, an unchanged plan is not run again, and Kaiya adds or changes a schedule only when you ask. 35. Mission Preview shows each planned step with its title, SQL or Python code, status, row and column counts, a five-row preview and run time. Files a step exports, including HTML reports, appear as cards in that step, open in the Artifact view, and stay available after you reload the page. 36. Refined spacing between SQL steps in the Mission view. 37. Ensured that a Mission built in Kaiya chat opens from **Edit Steps**. 38. Improved consistency between a published Mission's report and its step outputs when the Mission runs in a new conversation. Running a Mission uses its published version, editing works on its draft, and saved Python steps always run their saved code. 39. Refined the message shown when publishing after editing steps that have already run. 40. Refined padding on Mission Briefing reports, so content stays clear of the card edges. 41. Ensured that deleting a Mission built in a conversation keeps the conversation. ### **Apps** 42. Improved the App conversation so it stays active while the App is being built. 43. Ensured that an App Kaiya reports as built and saved displays in the interface. When Kaiya retries the start of an App build, it continues on the same App, so the App you open holds the finished build. 44. Kaiya confirms an App plan update once the saved plan has changed, and tells you clearly when an update is not supported. 45. Any App version, active or not, can be renamed from its version menu, and it keeps its published state. 46. The Plan tab on older Insight Apps shows the plan as formatted text, with headings and bullet lists. ### **Data and Vizpads** 47. Improved how large decimal values with more than 15 digits are loaded, so they keep their exact value. 48. Ensured that the compare column is filled in when you export a table that uses a compare-filter measure. 49. When a Vizpad export to Excel or CSV is interrupted by a temporary issue, a dialog offers to retry it once. 50. Resolved an issue with creating a Snowflake data source connection that uses OAuth. 51. Ensured that filtering sync jobs by **Queued** in the Notifications list returns queued jobs. 52. Ensured that the **User** filter on the unstructured connector list shows the selected user's connectors. Super Users can view every user's unstructured connectors. ### **Interface** 53. Refined listing pages so they display steadily when you scroll to the end of the list. 54. Card titles for Vizpads, Insights, Projects, Predict and Kaiya Apps, along with listing page headers, use a heavier font weight and the primary text color. 55. Removed the repeated description on the My Kaiya Credits page. 56. In the Home page composer's Business View dropdown, long names are shortened so the checkmark for the selected Business View stays visible. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.tellius.com/tellius-6.4/whats-new/release-6.4-legacy/patch-6.4.1.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.