Text summary or paragraph explanation: which do you need?
Article summary or paragraph explanation in Fastreader: a practical example, checking the original, AI limits, language choice and data handling.
A text summary gives you an overview; a paragraph explanation helps clarify a difficult idea. Fastreader summarizes materials in your Telegram inbox and explains paragraphs on the website and inside Telegram. AI prepares both answers, so check important conditions and conclusions against the original.
When an article summary helps
Use a summary to check whether a note is relevant or recover its subject after a break. The answer contains three to five main points but can omit exceptions or numbers. Read the source whenever a decision depends on those details.
Summaries use the original material in your server-side Telegram inbox. Changes you later make in the reader’s local library are not included. A text pasted only into the ordinary website reader does not have a summary button.
How to summarize text in Telegram
- Send @read_agent the text, an open article link, or a forwarded text post. Wait for confirmation that the material was added to your inbox.
- Press “Key ideas” below the bot’s reply. This action starts processing the original text with an external model; there is no separate confirmation before the first summary.
- Wait for the message with the main points. Reopening a saved summary does not contact the model again.
- Press “Read” and locate the source statements that matter to your task.
The summary input limit is 32 KiB of UTF-8 text, which differs from the inbox import limit. You can read larger originals without summaries. Select the bot’s reply language with /language ru or /language en. In the reader, summary and explanation languages follow the interface language. Another language version requires separate confirmation and uses another attempt.
How to explain a paragraph
Open your material on the website or in the Telegram reader. In “Text” mode, select a sentence and choose “Explain fragment”. You can also use that action in the paused context; on a phone, open “Context” first. The explanation covers the paragraph containing your selected sentence.
The window shows the source passage, a plain-language explanation, and an optional hypothetical example. Compare them before returning to reading. For a paragraph exceeding 8 KiB, prepare a shorter meaningful passage in a copy of the text. Ordinary reading remains available.
Check an answer with a short example
Starting Monday, requests are accepted until 15:00. The manager handles urgent requests received later separately. Ordinary requests received after the cutoff move to the next working day.
This is a teaching example, not a recorded model response. Before checking a summary, identify three points yourself: the cutoff time, the separate urgent-request procedure, and the handling of late ordinary requests. “No requests are accepted after 15:00” would lose an important exception.
For an explanation, check whether urgent and ordinary requests remain distinct. A hypothetical story supplied by the model does not become an additional rule from the author. If anything remains unclear, consult the surrounding paragraphs and the original instruction.
What is sent and saved?
Summarization sends the original inbox text to an external model. Explanation sends the selected paragraph, up to 8 KiB, plus neighboring paragraphs of up to 2 KiB each. Website explanations use functional cookies. Decide whether this processing is suitable for your material before pressing the action. Ordinary reading does not require an AI request.
Received explanations are saved in your local library and included in its backup. Server-side explanation operations and answers expire after 24 hours; this does not remove your saved device copy. Summaries remain associated with inbox materials, so that 24-hour rule does not apply to them. See data and analytics for details.
Missing answers and usage limits
New summaries and explanations have separate limits of up to five attempts of each type per user per day. They share project limits of 50 requests daily and 500 monthly. Website explanations also have a network limit. Days follow Moscow time; saved answers do not require another generation.
An error does not delete your original. Use “Refresh status” for a pending explanation to check the same request. Retrying after a failure is a separate action and can use another attempt. If an answer arrives but cannot be saved in your browser, retry saving or download a library backup before closing the page.
Try this technique with your own text.
Add your text →