Chatting with the AI
Chatting with the AI
This page covers everyday chatting with the AI (asking questions, prompts, answers): sending a question, what the states while the answer is generated mean, choosing an agent and a model, regenerating or editing, stopping an answer, exporting a conversation, the blue chips, what AnyLLM remembers for you and what the AI remembers within a conversation.
What this does
You type a question, the AI answers while the text is generated, and the conversation is saved automatically in your history. Where the surface knows an issue or a page, that content can be included; where the administration allows it, the AI can also look things up in Jira and Confluence — see Letting the AI Search, Read and Create.
Who can do this
All users. Every request runs with your own Jira and Confluence permissions.
Before you start
- The app is set up, the surface you are using is enabled and — for a paid installation — the subscription is active (see Getting Started).
- You have opened AnyLLM on any surface, e.g. Apps → AnyLLM Chat.
Step by step: asking a question
- Click into the field Message AnyLLM ….
- Type your question. For a line break press Shift+Enter.
- Press Enter or click the send button (arrow icon, tooltip Send (Enter)).
- Wait for the answer. While it is generated, the field is locked and the send button becomes the stop button (tooltip Stop).
Expected result — the answer appears word by word. Below the finished answer you see the name of the model that produced it. The conversation appears under History and, after the first answer, receives a short title generated by the AI (at most six words); if that fails, the first question is used as the title.
What the states mean
| State | Meaning |
|---|---|
| Generating answer … | the request has been sent and the AI has started |
| Model is thinking … | the model is reasoning internally before it writes; with some models this can take a while without visible text |
| Small rows such as "Jira search: …", "Reading issue …", "Confluence search: …", "Reading page …", "Web search: …" | the AI is looking something up; these rows are always in English |
Notes
- Answers may contain Markdown: headings, lists, tables, code blocks and links. If an answer contains a diagram in Mermaid notation (for example because you asked for one), it is rendered as a graphic.
- Images in answers are not loaded automatically. Instead of the image you see the link view external image; a click opens it in a new tab. This prevents an image from reporting data to the outside unasked.
- The automatic save does not apply to a temporary chat — see Temporary chat.
Choosing agent and model
In the bar below the input field, next to +, there are up to two selectors:
- The agent selector (screen-reader label Choose agent) — only appears if at least one agent is available to you (predefined by the administration, shared by colleagues or your own). No agent means: general chat. If the agent has a fixed model, the model selection switches with it. More: Creating Your Own Agents and Skills.
- The model selector (screen-reader label Choose model) — only appears if more than one model is enabled. The models are grouped by connection.
Both selections are remembered for you (see Remembered choices). If you reopen a saved conversation, the model and the agent of that conversation are restored, provided both still exist.
Regenerating an answer or editing a message
- ↻ Regenerate answer appears below the last answer as soon as the AI has finished. The last answer — including any open suggestion cards — is discarded and the question is sent again. Each regeneration counts as a new request.
- Edit & resend — hover over one of your own messages and click the pencil icon. The text returns to the input field, and the conversation is cut off from that point: everything after it is discarded. Adjust the text and send again.
Stopping an answer
While the AI is writing, the send button turns into the stop button (tooltip Stop). A click hides the running answer, and you can write again immediately.
⚠️ Warning: Stop only ends the display. The request continues on the server, and the complete answer can still land in the saved history. If you do not want that, delete the conversation afterwards — see Managing Chat History.
Exporting a conversation
- On the app page, in the fullscreen overlay and on the standalone full page: click + and then ↓ Export conversation (Markdown) (shown once the conversation has messages).
- In dialogs and panels (issue panel, issue sidebar panel, issue action, page assistant, macro, issue navigator): click ↓ Export in the header.
Expected result — a Markdown file named llm-chat-YYYY-MM-DD.md is downloaded. It contains your questions, the answers and the model names used; suggestion cards are not exported. The export runs entirely in your browser; nothing is transmitted.
The blue chips
In the bar below the input field, to the left of the send button, small blue chips show what is currently active:
| Chip | Meaning | Click |
|---|---|---|
| Temporary ✕ | temporary chat active (tooltip Temporary chat active — click to end) | ends the temporary mode and starts a new chat |
| Gear icon | model parameters set (tooltip Model parameters adjusted — click to edit) | opens the parameters |
| Memory icon | memory active (tooltip Memory active — click to edit) | opens the memory notes |
| {n} issues selected or Current search (JQL) | in the issue navigator: these issues are included as context | purely informational |
Remembered choices
The model, the agent, the setting Include page context and your model parameters are saved for you and restored the next time you open the chat. Because AnyLLM is one installation for both products, the same choices apply in Jira, in Confluence, in the fullscreen overlay and on the standalone full page.
What the AI remembers within a conversation
- Only the most recent 16 messages of a conversation (at most about 32,000 characters) are sent to the AI. In long chats the AI no longer remembers earlier turns even though they stay in the history. If an early detail matters, repeat it.
- Your memory notes and the administration's site knowledge are sent with every request; page or issue context is re-read with your permissions for every message.
- Per answer the AI may look things up in at most 5 rounds (Jira/Confluence searches, reads, web search) before it must answer. Each round may take up to 120 seconds; the whole answer at most 5 minutes; each lookup result is cut at 8,000 characters. Split very long multi-step tasks into smaller questions.
- If the AI only produced a suggestion card and no text, the answer reads I proposed an action — please confirm or dismiss it above.
Common problems
| Message | Cause | Solution |
|---|---|---|
| No response from stream (timeout) — please try again. | nothing arrived from the server for 60 seconds | send again; if it happens repeatedly, inform the administration |
| Hourly limit reached (… requests/hour) — please try again later. | your administration limits requests per person and hour; the counter is shared across Jira and Confluence, starts with your first request and resets after one hour; every send counts, including regenerate | wait, then try again |
| Timeout after 120s — shorten the prompt or choose another model. | one round of the AI took longer than 120 seconds | shorten the question or choose another model |
| The endpoint … is not approved for … yet — endpoint approvals apply per product. An administrator can grant it in the AnyLLM settings of … under “Endpoint approvals”. | the AI service is not yet approved in this product (Jira or Confluence) | inform the administration — see Managing Endpoint Approvals |
| The model used its token budget (…) on internal reasoning without answering — shorten the prompt or choose a non-reasoning model. | a reasoning model used the whole answer budget for thinking | shorten the question, raise Max response tokens or choose another model |
| LLM endpoint rejects the API key (401/403). · Rate limit of the LLM endpoint reached (429). · LLM endpoint responded with HTTP … · LLM call failed: … | the AI service refused the request | see Troubleshooting; usually the administration has to act |
| Stream error. · Call failed (invocation error or timeout). | a temporary transmission problem | send again |
| This feature has been disabled by your administrator. | this surface is switched off | use another entry point, e.g. the app page |
Related topics
Rendered from the app’s own interface with sample data; the Jira/Confluence frame around it is not shown.
Documentation baseline: app version 0.2.0 · 2026-08-30