Replace local ai-agent-detection with @vercel/agent-readability#354
Replace local ai-agent-detection with @vercel/agent-readability#354
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
![vercel[bot]](https://avatars.githubusercontent.com/in/8329?s=60&v=4){kind=small}
apps/docs/proxy.ts
Outdated
| return NextResponse.rewrite(new URL(result, request.nextUrl)); | ||
| } | ||
| // Agent requested a non-existent docs URL — return helpful markdown | ||
| return new NextResponse(generateNotFoundMarkdown(pathname), { |
There was a problem hiding this comment.
AI agent not-found response returns HTTP 200 instead of 404, causing agents to incorrectly believe the page exists.
There was a problem hiding this comment.
Yes — the comment on line 92 says "Agent requested a non-existent docs URL" and the function is called generateNotFoundMarkdown, so this is clearly a 404 scenario. Without an explicit status: 404, NextResponse defaults to 200, which would mislead AI agents that check status codes to determine if a resource exists.
The fix is adding status: 404 to the response options (see the suggestion above).
- Change DetectionMethod import from deleted local file to @vercel/agent-readability - Add Vary: Accept header on agent-rewrite responses - Add discovery options (sitemapUrl, indexUrl) to generateNotFoundMarkdown Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2 participants
Summary
ai-agent-detection.tswith the shared@vercel/agent-readabilitypackagegenerateNotFoundMarkdownresponse for agents hitting non-existent docs URLsSame approach as vercel/front#65649 and vercel/geistdocs#58.
Test plan
🤖 Generated with Claude Code