Urgent.News

What's breaking now, across hundreds of outlets.

AI

The September cut took 17% of my Claude Code week. Subagents were taking 48%.

My Claude Code week started ending on Wednesday. I blamed the September 14 cut, like everyone on r/ClaudeAI did. Then I opened the usage screen and the biggest line was not me typing. It was the helpers I had told it to launch. So I read a month of my own logs before touching a single setting. 455 sessions, 63,000 requests, and a number next to every saving tip I had been told to apply. Which of…

The September cut reduced Claude Code's week by 17%, with subagents accounting for 48% of the usage. A breakdown of the month's activity included 455 sessions and 63,000 requests, with Claude Code writing JSONL files for each session and subagent run. Double counting of answers was a trap, leading to the de-duplicated figure of 9.3 billion tokens.

Subagents were responsible for 48.1% of all tokens and 64% of all output, making them the heaviest line on the meter. Each subagent run paid an entry price, with the model being another significant factor. Implementing habits such as skipping subagents for simple tasks, pinning small models, and adjusting cache timeouts can help reduce usage.

The article also discussed the impact of effort levels on costs and the potential benefits of turning off certain features.

Rewritten by urgent.news; may contain errors — check the original.

Sources: xda-developers.com · dev.to · reddit.com

This story

This is one outlet's version. Read the fullest account.

Every outlet that reported this, and when →

Read the original at dev.to →

Report a problem with this story

More in AI

Touch Grass — Brutalist Open-Source AI That Shuts Your Screen Off in 15 Seconds

This is a submission for the Hacktoberfest Open-Source AI Challenge Week 1: Touch Grass Touch Grass: The Brutalist Open-Source AI for the Real World This Week's Theme: Touch Grass — Build something…

  • Touch Grass AI helps users disconnect from screens and spend time outdoors
  • Brutalist, edge-native AI runs offline without internet connection
  • 15-second screen-to-dirt protocol encourages immediate immersion in nature

What if the problem with AI writing novels isn't context length, but how we're using memory?

I keep seeing the same argument whenever people talk about AI writing long-form fiction: AI can't really write a 100,000-word novel because eventually the context becomes too large, details get lost…

  • AI writing novels may not struggle with context length, but with how memory is utilized.
  • Treat novel creation as structured project with chapters, not one giant conversation.

More from Thursday 8 October →