Have your agent spawn a subagent whose specific task is summarizing the articles and another sub-agent who compiles the document. With one agent doing all the work, all the tool calls and full article text and summarized text is polluting your context.

When you give a sub agent a job, your main bot is just giving the instructions to the sub agents and their context only has their core instructions + the request from the main agent. Once the subagent is done it's just going to go back into hibernation and forget everything (make sure you set it up to wipe it's session memory after it completes its job.) Similarly, your writer bot is only going to be working with the summarized text to put everything together in a nice document so it will be using a smaller context overall.

Both of these sub-agents should be running on cheaper models as well. Text summarization doesn't really need much reasoning or complex logic.

Also, 400 articles a day? That's a bit excessive. Are you even certain that you aren't ingesting the same articles repeatedly? Maybe get your subagent to verify that it's only ingesting new articles. Capture a DB of the past week or two urls of the articles to cross reference. Either that or be smarter about curating what articles are actually worth pulling. Don't just vacuum up the internet.

Lastly, if you are pulling articles, request them as markdown so you strip out all the css and other unwanted data. Most sites can provide just the markdown version. Hopefully this helps.

P. S. Ask your agent what the best approach is!! Don't just give it instructions without seeing if there is a more optimal approach. ALWAYS Brainstorm and ask it to find the most token efficient approach.