Live data from Hacker News

Show HN: Chie – a cross-platform, native, and extensible desktop client for LLMs

chie.app

1–10 of 25 posts

Show HN: Chie – a cross-platform, native, and extensible desktop client for LLMs

#1
I'm submitting this before going to bed, so by the time it hits front page (if it does at all) I'll likely be asleep, so I won't be able to answer questions in time.

Show HN: Chie – a cross-platform, native, and extensible desktop client for LLMs
chie.app

Re: Show HN: Chie – a cross-platform, native, and extensible desktop client for LLMs

#2
Looks great! Very excited to try this out. At first glance I have one concern and one suggestion:

Concern: you mention it supports the actual ChatGPT Web API -- isn't this against their terms of service? I'd be wary of publishing something that hits internal APIs.

Suggestion: I would rename what you call the "ChatGPT" (non-web) part of the backend to "OpenAI API" instead. There is already enough confusion in the world between ChatGPT and API access to the underlying GPT models.

Re: Show HN: Chie – a cross-platform, native, and extensible desktop client for LLMs

#3
post #2

Looks great! Very excited to try this out. At first glance I have one concern and one suggestion: Concern: you mention it supports the actual ChatGPT Web API -- isn't this against their terms of service? I'd be wary of publishing something that hits internal APIs. Suggestion: I would rename what you call the "ChatGPT" (non-web) part of the backend to "OpenAI API" instead. There is already enough confusion in the worl…

> Concern: you mention it supports the actual ChatGPT Web API -- isn't this against their terms of service? I'd be wary of publishing something that hits internal APIs.

There seems to be two extensions, one called "chatgpt" and one called "chatgpt-web" (https://github.com/chieapp/chie/tree/main/src/extensions). The latter seems to be using https://chat.openai.com/backend-api/conversation which is OpenAI's private API for ChatGPT. Using this (as a user) seems to be able to get you banned, as far as I can tell by some reddit posts as of late.

However, the extension called "chatgpt" seems to correctly use the right endpoint: https://api.openai.com/v1/chat/completions, but it's not ChatGPT anymore when you use it, so the naming is a bit confusing as you said.

Re: Show HN: Chie – a cross-platform, native, and extensible desktop client for LLMs

#4
post #2

Looks great! Very excited to try this out. At first glance I have one concern and one suggestion: Concern: you mention it supports the actual ChatGPT Web API -- isn't this against their terms of service? I'd be wary of publishing something that hits internal APIs. Suggestion: I would rename what you call the "ChatGPT" (non-web) part of the backend to "OpenAI API" instead. There is already enough confusion in the worl…

> Concern: you mention it supports the actual ChatGPT Web API -- isn't this against their terms of service? I'd be wary of publishing something that hits internal APIs. There seems to be two extensions, one called "chatgpt" and one called "chatgpt-web" ( https://github.com/chieapp/chie/tree/main/src/extensions ). The latter seems to be using https://chat.openai.com/backend-api/conversation which is OpenAI's private A…

I haven't read the terms of service, but would headless browser automation be a safer solution?

Re: Show HN: Chie – a cross-platform, native, and extensible desktop client for LLMs

#5
Your 'future plan' section says you want provide a subscription plan for gpt-4. Why would I pay a subscription to access my other subscription, especially when its a feature you currently offer for free. I feel like a one time fee to unlock access to premium models could be a better option. You will need to differentiate from your main free competition, chatboxai, to get a meaningful userbase like you have stated you want.

Re: Show HN: Chie – a cross-platform, native, and extensible desktop client for LLMs

#6
post #4

Earlier quoted context omitted.

> Concern: you mention it supports the actual ChatGPT Web API -- isn't this against their terms of service? I'd be wary of publishing something that hits internal APIs. There seems to be two extensions, one called "chatgpt" and one called "chatgpt-web" ( https://github.com/chieapp/chie/tree/main/src/extensions ). The latter seems to be using https://chat.openai.com/backend-api/conversation which is OpenAI's private A…

I haven't read the terms of service, but would headless browser automation be a safer solution?

The only thing that would keep you safe, if OpenAI bans people accessing the API outside of their client-side application, is if you make those requests from a different IP than what you normally use ChatGPT from.
Post reply on HN