Show HN: Lexeme – open-source ChatGPT text editor | Hacker News Reader

Show HN: Lexeme – open-source ChatGPT text editor

pagebrain.ai

7 pointskornesh5 comments

Everyone's favorite ChatGPT tool is the one they created themselves! Here's mine, a text editor for power users of ChatGPT, inspired by the flexibility of SQL workbench. I despise constantly switching between ChatGPT and VSCode just to copy and paste text for further editing.

Lexeme is my attempt to solve workflow issues like this, along with a few other improvements. You can easily start a chat with ChatGPT by highlighting any text. Lexeme allows you to create multiple chats within the same document, keeping each chat context separate to support an iterative writing process with the help of ChatGPT.

I have been using it almost daily for the past 4-5 months and have added a couple of features to fit my specific use cases. I'm not sure how useful this will be to others, but it's there lol

demo: https://pagebrain.ai/lexeme/

code: https://github.com/pagebrain/lexeme

Open articleView on HN

Nice UI, really great!

I've submitted you a couple of PRs that add support for custom OpenAI compatible API endpoints (local llms / llama etc...), upgraded the project to the supported current node LTS 20 version, updated your Dockerfile to drop root privileges and updated several packages to resolve critical security CVEs.

I'm over the the moon! absolutely wasn't expecting a PR, let alone two! Thanks @smcleod :)

Great, I'm using it now. If Lexeme is similar to Typora (https://typora.io), it could be fantastic and might even surpass Typora in terms of quality. On the other hand, if Typora already has these features, it's quite powerful.

The UI looks very clean, congrats on the launch.

I see you are using lexical, what was your decisions process to pick between lexical, prosemirror and other alternatives?

Thank you! I spent a lot of time reading reviews of both options and ultimately decided to go with Lexical because its API seemed easier. However, I quickly realized that the API is kind of twisted and has many restrictions. Also, the documentation was sparse but by then it was too late to restart from scratch.

Do you have any experience between these two?

Reply on news.ycombinator.com