The new Cheapseek's caching evidently doesn't work. Just burned $3 in about 30 minutes across 3 or 4 messages.
I'm not sure how phase 1 of Operation Cheepseek was implemented (seems that they're using some other providers, rather than DS itself), but it simply doesnt work. I just burned $3 of tokens with DS V4 Flash in 30 minutes across just a few prompts, because evidently there's no caching happening. I can see in my usage dashboard that each subrequest from the harness is something like $0.05-$0.10, rather than $0.0005, as normal.
My subscription is now at 93% monthly usage, so I dont see why I wouldn't just use DS API directly once it runs out...
Edit: folks are saying cache is fine for them. I created a new session and it is doing ok so far. It could be that I just had a one-off bug that turned out to be particularly expensive... Shame that I didnt notice it sooner.