Repository navigation
Give the chat's answers 180 seconds instead of 60 - #70
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
One model call of 56 seconds used up an answer's 60 seconds on staging (2026-11-09): Vercel ended the function after the search, and the visitor got no reply.
src/app/api/chat/route.ts:maxDurationfrom 60 to 180 (Hobby allows 300: https://vercel.com/docs/functions/configuring-functions/duration)src/server/ai/cloudflare.ts: the window for starting a reminder to save, from 25 to 90 seconds, so a slow first reply still gets oneThe measurement's
LIVE_SITE_SECONDSstill says 60; it only labels the report and belongs to the measurement lane.Local:
npm run verifypasses, with a new test that fails without the change. Not run: end-to-end tests, the real model.