Accounts
Separate accounts for each CLI
Each account keeps its own login and history, so work and personal never mix.
profiles/workprofiles/personalprofiles/sideUse Codex, Claude Code, Gemini CLI, Copilot, Cursor and other coding CLIs in one window. Your work and personal accounts stay separate, and your task comes with you when you switch agents.
Free · macOS 13+ · Windows 10/11 · Intel Mac?
Done. The middleware now verifies a PKCE challenge before minting a session, and the new tests cover replay and expiry.
This account's limit is used up. Pick another account and the conversation carries on there.
Picked up where Codex left off. Next I'll add rate limiting to the token exchange endpoint.
Supported coding CLIs
Features
Your CLIs still do the work. Renviel adds account management, handoff, undo, git and usage tracking around them.
Accounts
Each account keeps its own login and history, so work and personal never mix.
profiles/workprofiles/personalprofiles/sideMulti-agent
Compare two providers side by side, get a second opinion from another account, or run workflows that use several accounts.
renviel/0930-1412-codexAdded a sliding-window limiter to /token, with tests for bursts and resets.
renviel/0930-1412-claudeAdded a per-client token bucket that answers 429 with Retry-After, plus tests.
Changes
See which files a turn changed, then undo it.
Git
Commit, push and open a pull request. An agent can draft the message.
renviel/0930-14121Workspace
Open the project in an editor or a split terminal, and drag the panels wherever you want.
import { verify } from "./pkce"; /** Checks the PKCE challenge before a session is minted. */export async function middleware(req: Request) { const code = new URL(req.url).searchParams.get("code"); if (!code) return deny(400); return (await verify(code)) ? null : deny(401);}Usage
A year of daily activity, each account's limits and your biggest sessions, with an estimated API cost.
Shortcuts
Queue messages, mention files with @, jump anywhere with ⌘K / Ctrl+K.
Privacy
Your conversations, code and provider logins are kept on your computer.
Also: colour palettes, review comments on diffs, pull request checks and reviews for the agent, starting from a GitHub or Linear issue, session forking, skills and MCP servers per account, scheduled tasks, a GitHub issue queue, a project check after each turn, a session in its own window, a Mac notch island and one-click CLI install.
How it works
Sign in to each CLI once, from inside Renviel, using your own accounts.
Pick a project folder and an account, then say what you want done. Tool calls, diffs and test runs show up as they happen.
Change account or provider whenever you like. Renviel sends a short handoff note so the next agent can pick up where the last one stopped.
Handoff
You can switch at any time, not only at a usage limit. Renviel writes a short note from the session, without calling a model, and sends it with your next message. You can read it in the chat.
Download
Free for macOS and Windows.
Later updates install from inside the app.
You need at least one supported CLI. Renviel can install most of them for you. All releases and changelog
FAQ
Yes. You use your own provider accounts and subscriptions, and Renviel adds no charge. Everything in the app works without a Renviel account.
Yes. Renviel works with the official CLIs, such as Codex, Claude Code and Gemini CLI. It can install most of them for you when you add an account.
On your computer, in a .renviel folder inside your user folder. A Renviel account is optional and never holds your work. Each CLI sends your prompts straight to its provider, or to the address you set for an account.
Yes, if they are your own, for example one for work and one for personal use. Renviel keeps them apart and never switches between them by itself. At a usage limit it lists your accounts on other providers: moving to another account of the same provider to get past its limit can break that provider's terms. Some providers, such as GitHub, allow one free account per person.
Some plans are for personal, interactive use, such as Kimi Code, Qwen Coding Plan, MiMo Code and some coding plans added through OpenCode or a custom endpoint. With these Renviel only sends what you type: they don't take workflow steps, second opinions, comparisons, scheduled tasks, the issue queue or a goal loop, and they don't continue by themselves after a limit.
An account that signs in with an API key pays per token. Renviel doesn't run such accounts until you turn this on in Settings → Advanced, so nothing is billed by surprise. Gemini and Qwen are exempt, since a key is their only sign-in. An account on a custom endpoint runs when you send a message yourself, and needs the switch for scheduled tasks and the issue queue.
No. Renviel doesn't call a model itself: handoff notes and session titles are made without AI. Only the CLI uses tokens, for what you send, start or schedule, and each turn shows its count.
Yes. Renviel keeps a snapshot of the project folder before and after each turn, apart from your own Git history. You can undo any turn, and Renviel warns you first if those files changed since. Git must be installed.
Yes, with Claude Code and Codex. In Claude's Ask mode and Codex's Supervised mode, each command or edit waits for your answer in the chat. Other CLIs follow the permission mode you choose.
Another of your accounts reviews the current work in read-only mode, so it can't change files. Its reply appears in a separate card. Copilot, Grok, Amp, Goose and Cline have no read-only mode, so they can't give one.
Work that runs by itself never moves to another account because of a usage limit, and never retries after one. A workflow uses the accounts its steps name, one per provider, and pauses at a limit or an error. Scheduled tasks and the issue queue run only while Renviel is open and stop at a limit, and Renviel never pushes, merges or opens a pull request for them. When the issue queue works on a branch, it reads only what the project's own people wrote, unless you tick an outside issue after reading it.
They are other people's code, so add only what you trust. A skill is instructions and files the agent may run. A plugin can bring hooks and servers that run by themselves. An MCP server is a program the CLI starts for the agent. Renviel installs skills from a checked version, and each CLI installs its own plugins.
Some project files can make a CLI run programs or connect to servers, such as hooks, MCP settings and plugins. In a folder you haven't trusted, Renviel leaves them out, or doesn't start a CLI that can't leave them out. Trust a folder only if you know where it came from. Settings → Advanced lists the folders you trust.
No. Renviel is an independent project that works with the providers' official command-line tools.