> 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/kaiya/kaiya-apps/ai-summaries-in-apps.md). # AI summaries in Apps An App can generate a written summary of what you're looking at (a call plan for the selected physician, a verdict on the selected invoice etc.) at the moment you ask for it. ### **How AI summaries work** An AI summary is written when you ask for it. Press **Generate summary** and the App sends its instructions plus the data currently on screen to Tellius, which calls the model configured for Apps and returns formatted text rendered in place, alongside the data it describes. The App never holds model credentials. Every call routes through Tellius, the same boundary as live data. ### **The three controls** | Control | What it does | | ---------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Generate summary** | Writes the summary. Nothing is written until you press it. | | **Clear cache & regenerate** | Discards the stored answer and writes a new one. Use this when the underlying data changed but the text didn't. | | **Edit instructions** | Shows the guidance given to the model in a text box you can change, so you can retune tone, focus, or house rules without editing the App. Editing produces a fresh answer. | ### **What a summary can and cannot do** A summary describes what's on screen. If a number isn't in the view it was given, it isn't available to the summary. #### **Supported** * Summaries, briefings, recommendations, and verdicts * Summaries scoped to the current selection or filter state * Instructions you edit yourself * Several independent summary blocks in one App * Summaries over live-queried data #### **Not supported** * Querying the data platform - a summary only sees what was sent to it * Reasoning over the full dataset behind a chart * Generating automatically when the App opens, or on every selection change * Word-by-word streaming - the answer arrives complete * Very large selections, which are rejected #### **Caching** * An answer is stored against the exact combination of instructions and data sent, for about 15 days. * Reopening the same record weeks later returns the stored answer instantly. * Change the data, the selection, or the instructions, and a new answer is written. * If the source updated but the numbers on screen didn't change, the text won't change either. Use **Clear cache & regenerate**. #### **Adding a summary to an App** Summaries are opt-in. An app that only shows charts and tables won't have one. Ask for it explicitly. For example, type in "add an AI summary of the selected account", and Kaiya adds the block. An administrator can adjust how summaries behave across future apps. #### **Combining summaries with live data** An App can do both. Narrow the filter bar, the live cells re-query the source, and a summary block summarises those freshly returned rows. Nothing special is needed to combine them. The summary always describes whatever the cell is currently showing. ### Troubleshooting | Symptom | What's happening | What to do | | --------------------------------------------------- | ------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------- | | A cell shows an error as soon as the app opens | Your data permissions couldn't be resolved, or you have no permitted values for that filter | Ask an administrator to check data access for this dataset. The app refuses to show rows rather than show the wrong ones. | | Refresh succeeds but nothing changed | The app is fully live, so there's no captured data to refresh | Expected. A live app is always current. | | *"Show this by a different dimension"* doesn't work | Only filter values are interactive | Ask Kaiya to edit the app. Grouping is part of the app's design. | | A section stayed precomputed after *"make it live"* | Its data comes from calculation steps, so it can't be re-queried | That section keeps refresh-based data; the rest of the App is live. | | The summary text is stale after a data change | An identical earlier answer is cached for about 15 days | Use **Clear cache & regenerate**. | | **"Regenerate"** returns identical text | The stored answer is being returned for an unchanged request | Use **Clear cache & regenerate**, or edit the instructions. | | Nothing happens on open where a summary is expected | Summaries are generated on request by design | Press **Generate summary**. | | The App has no summary block at all | The request that built the App didn't ask for one | Ask for it explicitly and Kaiya will add the block. | --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.tellius.com/kaiya/kaiya-apps/ai-summaries-in-apps.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.