If you see this, something is wrong
First published on Saturday, May 9, 2026 and last modified on Wednesday, Sep 30, 2026
WebMagic
You can use AI in Documents Live in two ways .
Here is the breakdown.
You select some text in the editor and click the AI button. The AI reads your selection, writes a reply, and puts it in your clipboard. A message tells you “The answer is in the clipboard”. You can then paste the reply wherever you like. Nothing is inserted into your document automatically.
Use it for quick, self-contained requests: rephrase a sentence, explain a formula, translate a paragraph, suggest a title, and so on.
Your selection ──▶ Application ──▶ AI service
│
Clipboard ◀── (converted to LaTeX) ◀───┘| Sees your selection | Sees the reply | |
| The application | yes (passes it on) | yes (converts it) |
| The AI service you chose | yes | yes (it wrote it) |
| Other users of the site | no | no |
| Your document as a whole | not sent to anyone | — |
Vendors’ rules change. Check the current terms of the services you use.
If your selection contains confidential information, remember that it is sent to the AI service you chose.
You open a chat attached to a document, or to one of your document sets, and ask questions in plain language. The AI answers using the content of those documents, and the answer appears progressively as it is written. You can keep asking follow-up questions: the AI remembers what was said earlier in that chat, and you can come back to the chat later.
Think of a library with a librarian and an expert:
Both are outside companies that you choose in your AI settings, each with your own key. They can be the same company or two different ones.
Before a document can be chatted with:
Document ──▶ passages ──▶ embedding service ──▶ numbers
│ │
└──────────── saved in the application ◀┘For a document set, its documents should be prepared beforehand with the set’s “index” action. Documents that are already prepared are skipped.
Only the embedding service sees the full text of your document, and only at this stage. If you change the embedding service or model in your settings, documents need to be prepared again, because numbers from different models cannot be compared.
┌───────────────────────── saved passages
▼ (in the application)
Question ─▶ embedding ─▶ numbers ─▶ application finds 3 best passages
service │
▼
Answer ◀── AI service ◀── instructions + 3 passages + chat history + question
│
└──▶ shown to you, and saved in the chat history| Embedding service | AI service | Application | |
| Your full document | yes, once, when prepared | no | yes (stored) |
| Your question | yes | yes | yes |
| The 3 selected passages | no | yes, in readable form | yes |
| Earlier questions and answers | no | yes, each time | yes (stored) |
| The answer | no | yes (it wrote it) | yes (stored) |
| The numbers for each passage | yes (it computed them) | no | yes (stored) |
If the two services are different companies, they never communicate. Each receives its own separate request, and the application is the only link between them. The AI service does not see your whole document, only the 3 passages picked for your question. The embedding service never sees the answers.
Vendors’ rules change. Check the current terms of the services you use.
This is not absolute confidentiality: both companies see your questions, and the AI service sees the selected passages. For sensitive material, choose services whose terms you have read, and consider whether the document should be prepared for AI at all.
| Message | What to do |
| “No API key available…” | Add or update your keys in your AI settings. You need one for the AI service and one for the embedding service. |
| “This document is not AI ready” | Prepare the document for AI first. |
| “You are not authorized to access this document” | The author has restricted AI use on this document, or the chat belongs to someone else. |
| “The selected document set is empty” or “not found” | Check the set’s name and content. |
| “Chat error: …” | The AI or embedding service refused the request (for example, invalid key or exhausted credit). The text after the colon explains why. |
Before using AI in Documents Live, you need to create an account for an AI provider and get an API key for this provider. Documents Live supports currently the following providers:
API keys let Documents Live connect to your AI provider account and use it inside Documents Live.
When an API key has been generated, copy it to a safe place like a password manager, because you will not see it again.
After this is done, go to your account settings at Documents Live. There you will be able to store your API key for usage on the platform.
To create an account for Claude, follow this link .
Once this is done, you can get your API key here .
You can also visit this excellent tutorial .
Here is a video that you can find on this site.
Just follow the link to create an OpenAI account and create an OpenAI API key .
You can also have a look at this step by step guide .
Cohere is a Canadian AI provider.
There is a step by step guide about how to get a Cohere API key.
You can get your API key at the Cohere dashboard .
First create your account here . Note: DeepSeek only accepts common domain extensions or Gmail, Outlook or Yahoo emails. .com email adresses work fine.
You can put money on your account here .
And finally get an API key .
First, create a Google account .
Then, visit the Google AI studio . There you can get an API key and setup you payment details.
Visit Mistral to set up an account.
Once you are connected, you can get an API key from the console.
Below your account identifier in the Mistral AI studio, there is a link that redirects you to your billing settings.
Access you account settings from the top right dropdown menu.
There you can provide your API keys to Documents Live. Theses API keys are stored in encrypted form in the database. What you have to do is select the provider and enter the API key.
Once this is done, you will be back to your account settings. In the "Providers and models" section, you can select
Below this section in your account settings, is the list of your providers, with test buttons to test the connection for each provider. Below is a screen capture.
I use Voyage for embedding and Claude’s Haiku AI model. Haiku is relatively inexpensive, and it does a very good job at giving well formatted answers.
A document can be prepared for AI (i.e. prepare the RAG text, split and embed it) either from the documents dashboard or within the Inline Editor. We shall detail the first option.
In your documents list, documents that have been prepared for AI have a green badge that says "AI".
Before preparing a document for AI, make sure that the document has been imported recently so that its Documents Live internal model is up to date.
Then, from the "Action" dropdown menu, select the "Prepare for Al" item. That’s it!
In the left sidebar of the Inline Editor is the Chat interface. Open the "AI Chat" tab if needed.
To create a chat, click of the "New chat" button and give it a name.
When you have at least one chat, a select menu lets you chose which chat history you want to use. Select one and click the "Open" button. The chat history is revealed, with a zone at the bottom where you can enter a new question.
Be patient while your answer is being prepared.
After a while you will get your answer.
Note that in the chat history, clicking on a question collapses/expanses the answer to manage space efficiently.
A chat answer has two parts
Unless your document has a very old internal model, the links in the chat answers should lead you directly to the references that have been selected by the AI. Because the links are absolute, they will work in any Documents Live content where you have used the answer LaTeX code. Below is the screen capture of a chat example.
You can use AI right inside the code editor.
To do so, type your question in the editor, select it and click on the AI button. The AI answer will be put in the clipboard as LaTeX code, which you can re-use anywhere.
Here is an animated example.