Skip to content

Streamline workspace tooling and Windows automation#6

Open
112-stack wants to merge 1 commit into
mainfrom
codex/create-local-python-web-application-with-chatgpt-0q4gt9
Open

Streamline workspace tooling and Windows automation#6
112-stack wants to merge 1 commit into
mainfrom
codex/create-local-python-web-application-with-chatgpt-0q4gt9

Conversation

@112-stack

Copy link
Copy Markdown
Owner

Summary

  • add an npm workspace root with a cross-platform dev orchestrator so the API and client can start together cleanly
  • harden the Windows installer/runner to validate project layout, handle paths with spaces, and warn about leftover Flask stacks
  • document the new workflow, expose configurable API base URLs for the client, and guard the server against missing OpenAI configuration

Testing

  • node --check server/src/index.js
  • node --check tools/dev.mjs

Codex Task

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 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".

Comment on lines +22 to +25
try {
const response = await axios.post<ChatResponse>('/api/chat', {
prompt: trimmed,
history: historyRef.current.map((entry) => ({ role: entry.role, content: entry.content })),

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge 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 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant