How to Provide Materials in Batches When They Are Too Long?
Reduce input size, preserve structure, and pay attention to long text prompts.
First Retain the Parts That Can Answer the Question
Long logs, lengthy documents, or entire code files do not necessarily need to be sent all at once. First explain the overall structure and objective, then provide the most relevant sections, such as the records immediately before and after an error occurs, along with the corresponding configuration. When trimming, use text to indicate omitted parts, and preserve information that helps locate content such as chronological order, field names, and line numbers.
Split by Topic or Stage
When the input is too long, the page will provide a prompt; some Agent scenarios that meet certain conditions will convert long text into attachments, but this is not a uniform behavior across all modes. You can split the input yourself into “background,” “key inputs,” and “supplementary evidence,” and each time clarify the relationship between this batch of materials and the previous content.
- First send the objective, material directory, and key excerpts.
- Add the next part as needed based on the answer, rather than repeating all content.
- If an attachment appears automatically, check the file name and preview before sending.
Finally Request Cross-Verification
After completing the materials in batches, you can ask to organize which conclusions depend on which parts and what has not yet been covered. Do not simply replace specific verification with “all content has been reviewed”; instead, inquire whether key fields or excerpts have been considered. If a certain segment of the original material is missing, clearly state the limitation to avoid supplementing unknown parts as facts in the summary. Retaining the names of each batch of materials makes it easier to locate them in subsequent follow-up questions.