Find why auth_refresh is flaky in CI and fix it.
The test awaits a token with a 2 s timeout while the mock clock advances only 1.5 s.
Patched tests/auth.rs to advance the clock past expiry. 14 tests pass.
Turn finished
Open source. Thin by design. Inside VS Code.
Every coding agent.
One VS Code sidebar.
runtrol supervises the coding-agent CLIs already installed on your machine. Every project, 30 conversations at once, who is running, and how much quota is left, in one sidebar, with no extra window and no second copy of your chats.
Checking GitHub Releases for a VSIX.
Move config loading from JSON to TOML. Keep the old file readable.
Adding toml and a fallback reader for config.json.
Allow: write Cargo.toml Allow
Dependency added. Both formats load in the same test.
Everything in the sidebar. Nothing hidden behind a tab.
The release rule is strict: every connected CLI, every top-level project, the real conversation title, who is running, and how much quota is left must be readable from one screen without a click.
One tree, every project
The current folder is the first heading. Folders you keep returning to become projects on their own.
Icons that spin while work runs
Each row shows the agent and the real conversation title. The icon itself rotates while that turn is running.
Quota you can see
Per-CLI usage and reset time stay in view, read from the provider itself, never estimated.
Chats as editor tabs
Each conversation opens as its own tab. Split them like files. Typing and interrupting go to that tab.
Ask several CLIs at once
Send the same first message to Claude Code and Codex in separate linked worktrees, then compare in native diff.
Updates without a restart
After an extension update the old Core rolls to the new build the moment the machine is idle.
Install once. runtrol finds the CLIs.
There is no separate desktop app. Runtrol Studio lives where the work already happens and discovers installed CLIs, their versions, models, and flags at runtime.
- 1Install Runtrol Studio
From the Visual Studio Marketplace, or search
@id:runtrol.runtrol-studioin VS Code. - 2Open the runtrol icon
The sidebar opens inside your current VS Code window with the current folder already listed.
- 3Keep your CLIs as they are
Each CLI stays installed and signed in through its own official flow. runtrol never touches its credentials.
- 4Pick a conversation and go
Cold sessions resume through the provider's own identity. The workspace follows what you selected.
PRIMARY INSTALL
Visual Studio Marketplace
Public for six native targets, updated through VS Code.
Open Marketplace
MANUAL FALLBACK
VSIX from GitHub Releases
No public VSIX is available yet.
Check Releases
Pair once. The PC keeps owning the session.
The phone app is live at this permanent HTTPS origin. It pairs from a one-use QR in VS Code and reconnects through an end-to-end encrypted relay. Notifications carry no conversation content and open the exact session that needs you.
Secure phone app available
Open phone appThe supervisor stays out of the conversation.
Provider-owned history
runtrol transports process events. It never keeps a second transcript or rewrites meaning.
Runtime discovery
Providers, versions, models, flags, and session paths come from the installed CLI, not from a hardcoded list.
Remote default deny
Phone control is scoped, paired, and encrypted. Model credentials never cross runtrol.