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.
Who it is forA user who already pays for a ChatGPT or Grok subscription and wants to use it in Oriveo without buying separate API credits.
The problemPaying for an API key separately duplicates a subscription you already hold.
The outcomeA chat session answered through your existing subscription, with the sign-in completed on the provider's own device-authorization page.
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
- Complete the web quickstart with
cd web,npm install, andnpm run dev:app. - Open the OpenAI or Grok provider settings in the app.
- Choose subscription sign-in instead of an API key.
- Follow the provider's device-authorization steps and approve the request.
- Send a test message and confirm the reply comes from the subscription model.
Prompt for your agent
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.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: 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