vibe-coding-platform: BotID causes 403 on /api/errors and crashes client
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5.2k
- Forks
- 1.8k
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 6
Description
I cloned and redeployed on Vercel.
Every generation /api/errors is called once which BotID flags:
Possible misconfiguration of Vercel BotId or malicious request to 'POST /api/errors'. More info at https://vercel.com/docs/botid#add-client-side-protection
Which causes the app to crash:
Application error: a client-side exception has occurred while loading echo-vibe-coding-platform.vercel.app (see the browser console for more information).
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing a generation on the deployed example and inspect the POST /api/errors request and browser console for the BotID 403. Read the BotID warning and the example's /api/errors handling; done means generations no longer trigger the 403 or the client-side crash.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nextjs, typescript
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100