Accounts

Every account you add gets its own folder inside Renviel's data folder. The CLI keeps its sign-in, settings and history there, apart from your other accounts and from anything you set up in a terminal. That is how a work account and a personal account of the same tool can sit side by side.

Add an account

Choose Add account in the sidebar or in Settings → Accounts.
Pick the CLI. If it isn't installed, install it from the same window.
Sign in. Most CLIs open their own sign-in page in your browser. Some ask in a terminal window, and a few take an API key in a form inside Renviel.

When a CLI signs in through its own page, Renviel never sees your password. A key you type into Renviel is stored in your system's keychain.

More than one account of a provider

That's fine when they are all yours, for example one for work and one for personal projects. When an account reaches its usage limit, Renviel doesn't offer another account of the same provider: most providers don't allow a second account to be used to get past a limit. More in the FAQ.

API keys

An account that uses an API key pays per token. For most CLIs Renviel sends turns with such an account only after you turn on "Allow API-key billing" in Settings → Advanced. Keys exported in your shell are not passed to the CLIs while that setting is off.

Your own CLI setup

Since each account has its own folder, the instructions, skills and commands you set up for a CLI in your terminal aren't there at first. For CLIs that support it, turn on "Use my CLI setup" for an account in Settings → Accounts. Renviel copies them in and keeps them up to date. Sign-ins and history are never copied.

A custom address

Some accounts can send their requests to another address, such as a gateway or a vendor with a compatible API. Choose "Use a custom endpoint instead" when you add the account. The key is kept in the keychain, and that vendor bills the account per token.

A Renviel account

You don't need one. Everything in the app works without signing in to Renviel.