Do not combine multitask mode with thermo nuclear review in @cursor
I repeat, do not combine multitask with thermo nuclear review in Cursor
how the hell can an agent spend 30M tokens in less than an hour 💀
@cramforce@fal Yea, I wanted to whitelist their IPs but couldn't find them anywhere.
I've also looked into adding a bypass token to the webhook request but they do not have a way to configure it.
I think Vercel firewall is blocking @fal webhook requests.
The webhook requests appear with a 401 status code on my Fal's dashboard. I also see FalBot added in https://t.co/qQkF13YAY3
I can't find any reference on how to solve this in Vercel or Fal docs.
@cramforce help 😭
@fal@cramforce The whole webhook route handler is generated by the Workflow DevKit and I see the WDK uses the url corresponding to the deployment instead of the production URL. Could this be the issue? Maybe deployments have different protection rules?
@pranaygp Any insights?
@timneutkens@nextjs I’ve been using 'use cache' like in the snippet above.
Should I expect the cached data to be global (shared across users) or scoped per request?
@timneutkens@nextjs Excuse my ignorance, but what does “cache at runtime” mean exactly? Any function that doesn’t run at build time, like this with dynamic params?
```
export async function getPost(id) {
'use cache'
return db.query('...')
}
```
hey @rauchg I think Vercel's Bot Protection is blocking @polar_sh webhook requests.
I enabled it yesterday, and today I woke up to all Polar requests blocked with a 429 status code. I tried disabling it and resending Polar events, and it worked just fine.
The "use cache" directive does not work in Vercel
Am I reading this correctly?
This is absolutely insane. I've noticed the issue months ago and always thought I was doing something wrong.