GCP Backend Migration | /chat Endpoint#22
Merged
Bhagat-Atul merged 1 commit intoJul 10, 2026
Conversation
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
1 participant
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.
We split the AI proxy contract into two explicit endpoints:
- POST /analyze is now analysis-only for OCR/ingredient text.
- POST /chat is now the dedicated result-chat endpoint.
High-level changes:
- Added /chat with its own backend-owned chat prompt.
- Android result chat now calls /chat directly.
- Backend docs/tests were updated for the new contract.
- Public endpoint abuse controls are still deferred and documented as a TODO before broad production launch.
Before testing the latest Android chat flow, the Cloud Run backend needs to be redeployed from the updated backend code. Current deployed
backend may not have /chat, so chat will fail until GCP is updated.