Portal by Spotify cut my Claude Code token usage by 90%
151–160 of 176 posts
Re: Portal by Spotify cut my Claude Code token usage by 90%
#152Re: Portal by Spotify cut my Claude Code token usage by 90%
#153And it's just the execution, I'm not even going to comment on the idea itself, as it's even worse.
How this slop-post landed on the front page...?
Re: Portal by Spotify cut my Claude Code token usage by 90%
#154Earlier quoted context omitted.
The spotify desktop app is one of the worst pieces of software by a major company I have ever used.
I timed how long it took to open Spotify and play a song on a $2500 Mac on low latency gigabit fiber internet. 15 seconds. Incredible stuff.
And no, the problems you described are not there.
On my Windows 11 laptop it takes about 2sec to start and basically any song starts in less than a second.
Maybe it's Apple making Spotify crappy on Mac to promote iTunes?
Re: Portal by Spotify cut my Claude Code token usage by 90%
#155Re: Portal by Spotify cut my Claude Code token usage by 90%
#156Re: Portal by Spotify cut my Claude Code token usage by 90%
#157Re: Portal by Spotify cut my Claude Code token usage by 90%
#158Re: Portal by Spotify cut my Claude Code token usage by 90%
#159Earlier quoted context omitted.
> I've never had an issue with Codex or Claude reading massive files Reading files isn't a problem they want to solve. The idea seems to be using a cheaper model to "scout" for the intended code, instead of an expensive one that reads all the things (and spends more tokens / thinks about them). I think this might be useful because Opus 5 especially tends to over-read. So this looks like an "LLM Bloom filter", telling…
Pretty sure claude code already delegates reading a large codebase to haiku subagents.
Re: Portal by Spotify cut my Claude Code token usage by 90%
#160fable already calls subagents (hoping not opus), so i don't really see the gain here