# AI use cases for Oriveo (oriveo/oriveo)

Repo: [oriveo/oriveo](https://github.com/oriveo/oriveo) | Use cases: 5 | Page: https://dedupedai.com/use-cases/oriveo-oriveo/

Oriveo Community Edition is an open-source, bring-your-own-key AI chat client for iOS, Android, and the web that talks directly to model providers and local model servers using your own keys.

This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL.

- Run a private chat app in your browser with your own key: https://dedupedai.com/use-cases/oriveo-oriveo/run-web-chat-with-own-api-key/
- Chat with a local model server through a relay endpoint: https://dedupedai.com/use-cases/oriveo-oriveo/chat-with-local-model-on-own-machine/
- Build and run the iOS app on your own iPhone: https://dedupedai.com/use-cases/oriveo-oriveo/build-ios-app-on-own-iphone/
- Build a debug Android APK from source: https://dedupedai.com/use-cases/oriveo-oriveo/build-android-debug-apk/
- Chat with a ChatGPT or Grok plan you already pay for: https://dedupedai.com/use-cases/oriveo-oriveo/use-chatgpt-or-grok-subscription-in-chat/

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

Repo: [oriveo/oriveo](https://github.com/oriveo/oriveo) | Difficulty: Intermediate | Time: 15 minutes | Basis: From the README

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

**Who it is for:** A 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 problem:** Hosted chat plans add a markup and an account layer between you and the model you already pay for.

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

### 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 to paste into your agent

```text
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.

Risk, 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.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/oriveo-oriveo/run-web-chat-with-own-api-key/

## How to chat with a local model server through a relay endpoint with Oriveo

Repo: [oriveo/oriveo](https://github.com/oriveo/oriveo) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README

Point Oriveo at Ollama, LM Studio, llama.cpp or vLLM on your own network and chat with local models.

**Who it is for:** A privacy-focused user or developer who runs open models on their own machine or LAN and wants one chat app for local and hosted models.

**The problem:** Local model servers expose their own APIs, so each one needs a separate client or a manual setup for every device.

**The outcome:** A chat session answered by a local model served from your machine, with the same conversation list as your hosted providers.

### Steps

1. Start a local server such as Ollama, LM Studio, llama.cpp or vLLM on your machine and load a model in it.
2. Complete the web quickstart with `cd web`, `npm install`, and `npm run dev:app`.
3. In the app, add a Relay endpoint that points at your local server address (inferred: the relay settings screen is where this is entered).
4. On iOS or Android, let the app find the server on the local network by mDNS where the engine advertises itself, or by probing usual ports.
5. Select the local model and send a message to confirm it replies.

### Prompt to paste into your agent

```text
In the oriveo/oriveo repository, start a local model server, run the web client with npm run dev:app, and add a relay endpoint for the local server address <local-server-url>. Expected output: a reply from the local model in the chat. Verify that the request is sent to <local-server-url> and that no Oriveo account is requested.
```

### Caveat

The README says the web client can call relays on your own network directly, while most provider APIs need the Next.js route handler on the machine serving the app.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/oriveo-oriveo/chat-with-local-model-on-own-machine/

## How to build and run the iOS app on your own iPhone with Oriveo

Repo: [oriveo/oriveo](https://github.com/oriveo/oriveo) | Difficulty: Advanced | Time: 45 minutes | Basis: From the README

Build Community Edition from source in Xcode and run it on an iPhone with a free developer account.

**Who it is for:** An iPhone user with a Mac who wants a self-built chat app that does not depend on the App Store build.

**The problem:** The store builds are the commercial edition with an account layer, and you want the open source build on your own device.

**The outcome:** The Oriveo Community Edition app running on your iPhone, signed with your own team.

### Steps

1. Open `ios/Oriveo/Oriveo.xcodeproj` in Xcode 26.
2. Select the `Oriveo` scheme.
3. Under Signing & Capabilities, choose your own Team.
4. If Xcode cannot register `ai.oriveo.community`, change the bundle identifier to one your team owns.
5. Run the app on your iPhone and add a provider key on the first screen.

### Prompt to paste into your agent

```text
Open ios/Oriveo/Oriveo.xcodeproj from the oriveo/oriveo repository in Xcode 26, select the Oriveo scheme, set the signing team to <team-name>, and run on <device-name>. Expected output: the app launches on the device. Verify that the bundle identifier is registered under <team-name>.
```

### Caveat

The README says the iOS build requires Xcode 26 and iOS 18 or later, and it is built from source rather than distributed as a prebuilt binary.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/oriveo-oriveo/build-ios-app-on-own-iphone/

## How to build a debug Android APK from source with Oriveo

Repo: [oriveo/oriveo](https://github.com/oriveo/oriveo) | Difficulty: Advanced | Time: 30 minutes | Basis: From the README

Compile the Community Edition Android client into a debug APK with Gradle.

**Who it is for:** An Android developer who wants to inspect or run the open source client without the Google Play build.

**The problem:** Community Edition ships as source only, so the APK has to be built before it can be installed.

**The outcome:** A debug APK built from the repository that can be installed on an Android device.

### Steps

1. Install JDK 21 and the Android SDK, and confirm that Android Studio is a release that can sync AGP 9.3, Gradle 9.5 and Kotlin 2.3 if you use it.
2. Run `cd android`.
3. Run `./gradlew :app:assembleDebug`.
4. Locate the debug APK under the app module build output and copy it to an Android device.

### Prompt to paste into your agent

```text
In the oriveo/oriveo repository, change into android and run ./gradlew :app:assembleDebug with JDK 21 and the Android SDK available. Expected output: a debug APK in the app build output. Verify that the build finishes with no errors and report the APK path.
```

### Caveat

The README gives the build command but does not say where the APK is written, so the output path must be confirmed in the build output.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/oriveo-oriveo/build-android-debug-apk/

## How to chat with a ChatGPT or Grok plan you already pay for with Oriveo

Repo: [oriveo/oriveo](https://github.com/oriveo/oriveo) | Difficulty: Intermediate | Time: 15 minutes | Basis: From the README

Sign in with a ChatGPT or Grok subscription instead of an API key, using the provider's device flow.

**Who it is for:** A user who already pays for a ChatGPT or Grok subscription and wants to use it in Oriveo without buying separate API credits.

**The problem:** Paying for an API key separately duplicates a subscription you already hold.

**The outcome:** A chat session answered through your existing subscription, with the sign-in completed on the provider's own device-authorization page.

### Steps

1. Complete the web quickstart with `cd web`, `npm install`, and `npm run dev:app`.
2. Open the OpenAI or Grok provider settings in the app.
3. Choose subscription sign-in instead of an API key.
4. Follow the provider's device-authorization steps and approve the request.
5. Send a test message and confirm the reply comes from the subscription model.

### Prompt to paste into your agent

```text
In the oriveo/oriveo repository, run the web client with npm run dev:app and start subscription sign-in for <provider-name>. Expected output: a device code and verification step from the provider. Verify that the chat completes after approval and that no API key was entered.
```

### Caveat

The README says subscription sign-in is available for OpenAI with a ChatGPT plan and for Grok only, and it does not say which subscription tiers qualify.

Risk, credentials: This signs your subscription account into a local client, so treat the session as account access and sign out on any machine you do not control.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/oriveo-oriveo/use-chatgpt-or-grok-subscription-in-chat/
