Using chatgpt instead of openai
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 132
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
Hey I just saw your comment in hn. I see that your project can eat lots of openai credits, maybe it makes sense to use a chatgpt wrapper instead (https://github.com/mmabrouk/chatgpt-wrapper). The project is still nascent, I welcome any PRs :)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by locating how Helix currently uses OpenAI and compare that flow with the linked chatgpt-wrapper project. Done would mean a decided, working replacement that addresses the credit concern without leaving the existing integration incomplete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- ai, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100