What to Do When Prompt Content or Context Is Too Long?

Identify Space-Consuming Material First

Check if you recently pasted large logs, repeatedly attached the same file, or caused commands to return large outputs. Do not immediately resend all the content; if the issue is capacity, resending duplicates will not solve it.

First distinguish whether a single input is too long or if the task has been ongoing for a long time. The former requires adjusting the current material, while the latter also requires organizing existing progress.

Use a Task Summary to Retain Necessary Information

You can request a summary of the current goals, confirmed facts, unresolved issues, and key file locations, then continue with this summary.

When organizing materials, do not delete premises that determine conclusions, such as target versions, test scope, and records of reproduction failures. Retaining only fragments that seem to support conclusions can cause bias; you can move unrelated large content out of the current round while listing the scope of what is retained and omitted.

1. Delete duplicate or irrelevant paragraphs to the current issue.
2. Keep text near error messages, necessary code, and the exact problem.
3. Break large materials into topics and check each part separately.
4. If a new task is needed, bring in the verified summary and necessary attachments.

Do Not Retain Only Conclusions

Summaries should retain evidence locations and constraints to avoid carrying unverified guesses into the next round. Even if automatic long-context summarization is supported, it cannot guarantee every early detail is fully preserved; important constraints should be explicitly stated when continuing. Model switching should not be treated as a method for unlimited capacity expansion; specific capacity is still limited by the current mode and account.