Skip to content

Conversation

cavit99
Copy link

@cavit99 cavit99 commented Jan 28, 2025

This commit updates the default fetch URL in frontend/components/chat.tsx from https://api.deepclaude.com to http://127.0.0.1:1337.

Reasoning:

The previous default configuration unintentionally directed API requests to the hosted api.deepclaude.com endpoint, even when users were running the frontend locally. This could lead to users inadvertently sending their API keys to the external server if they used the chat interface without realizing this default setting.

This change ensures that by default, the frontend communicates with the local backend server running on http://127.0.0.1:1337, aligning with the expected behavior for users who are self-hosting the application.

Security Improvement:

By pointing to the local backend by default, this commit reduces the risk of users unintentionally exposing their API keys to an external server.

Users who intend to use the managed api.deepclaude.com API can still manually change the fetch URL, but the default is now correctly configured for local development and self-hosting scenarios.

This commit updates the default `fetch` URL in `frontend/components/chat.tsx` from `https://api.deepclaude.com` to `http://127.0.0.1:1337`.

**Reasoning:**

The previous default configuration unintentionally directed API requests to the hosted `api.deepclaude.com` endpoint, even when users were running the frontend locally. This could lead to users inadvertently sending their API keys to the external server if they used the chat interface without realizing this default setting.

This change ensures that by default, the frontend communicates with the local backend server running on `http://127.0.0.1:1337`, aligning with the expected behavior for users who are self-hosting the application.

**Security Improvement:**

By pointing to the local backend by default, this commit reduces the risk of users unintentionally exposing their API keys to an external server.

Users who intend to use the managed `api.deepclaude.com` API can still manually change the fetch URL, but the default is now correctly configured for local development and self-hosting scenarios.
@KenForever1
Copy link

Hello, when I changed the code like you did, I encountered the following problem. Have you encountered it before? How was it resolved? @cavit99

I change code like this:
`471 | //const response = await fetch("https://api.deepclaude.com", {

472 | const response = await fetch("http://127.0.0.1:1337", {`

I run frontend like this:
npm run dev -- -H 0.0.0.0

Then, meet this problem:
TypeError: Failed to fetch

like this: vercel/next.js#49896

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants