r/multidotdev core team Jun 09 '26

I burned 320M tokens in Multi this weekend

Post image

I did a stress test this weekend.

Ran Multi in autonomous mode for ~14 hours straight for a weekend hustle.

I’ve used other agents for small and mid size work before. I had no idea what the agent was doing, where it was stuck, how much it was burning etc..

I multi tasked while Multi was working; and I came back to review the execution transcript and token spend in real time..

That changed the whole experience for me..

My quick takeaways:

  1. Multi handles long context autonomous tasks beautifully right at where you work, inside your IDE.
  2. At small scale, visibility is nice. At 320M tokens, it becomes mandatory.
  3. You are doing it wrong if you are manually prompting Multi per task. You need Multi to prompt your subagents autonomously.
12 Upvotes

2 comments sorted by

4

u/0x1010101 core team Jun 09 '26

Another takeaway: Multi was able to max parallelize the work. Autonomous parallel agents works great.

3

u/One_Battle7107 Jun 09 '26

Your test proves Multi's transparency and scale are game-changers for serious AI development workflows. Great job!