DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to run a private chat app in your browser with your own key with Oriveo

Start the web client on your machine and chat with any of 15 providers using your own API key.

Credentials. Your provider API key is entered into the app, and the README says that on the web it is stored unencrypted, so use a key with limited scope and do not share the machine.

Who it is forA developer or power user who wants a chat interface on their own machine, without an account or a subscription, the moment they have a provider key.

The problemHosted chat plans add a markup and an account layer between you and the model you already pay for.

The outcomeA chat app running at localhost on your own machine, with your provider key entered on the first screen and conversations kept on the device.

What you need first

  • Node 22.22.2 or a later 22.x for the web client (Node 23+ is not supported)
  • At least one provider API key you created yourself, or a local model server such as Ollama, LM Studio, llama.cpp or vLLM
  • For iOS: a Mac with Xcode 26 and an iPhone on iOS 18 or later, plus a free Apple Developer account
  • For Android: JDK 21 and the Android SDK
  • For subscription sign-in: a ChatGPT or Grok subscription you already hold

Steps

  1. Install Node 22.22.2 or a later 22.x, and confirm that Node 23 or newer is not the active version.
  2. Run cd web in a terminal, then run npm install.
  3. Run npm run dev:app, then open http://localhost:3001 in a browser.
  4. On the first screen, enter the API key for one provider such as OpenAI, Anthropic or Google Gemini.
  5. Send a test message and confirm that a streamed reply appears.

Prompt for your agent

Clone the oriveo/oriveo repository, change into the web directory, run npm install and npm run dev:app, then confirm that http://localhost:3001 responds. Report the URL and the Node version used, and verify that the app asks for a provider API key on the first screen.

Caveat. The web client needs Node 22.x, and the README says Node 23+ is not supported.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page