Streamline workspace tooling and Windows automation#6
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| try { | ||
| const response = await axios.post<ChatResponse>('/api/chat', { | ||
| prompt: trimmed, | ||
| history: historyRef.current.map((entry) => ({ role: entry.role, content: entry.content })), |
There was a problem hiding this comment.
Respect API base URL in chat hook
The chat hook posts to '/api/chat' using the default axios instance, ignoring the configurable API base URL that was added for the other client requests (submitInsightRequest/submitComparisonRequest). If the UI is deployed separately from the Node server and VITE_API_BASE_URL points to the remote API host, insight and comparison requests succeed while chat continues to hit the UI origin and fails (404/CORS). The hook should reuse the configured axios client or prepend the same environment base so remote deployments keep chat functional.
Useful? React with 👍 / 👎.
Summary
Testing
Codex Task