Forge & Code

CLI

RodiumAi Code in your terminal. Install it once and type rodium: it reads your code, edits files, runs commands and works through a task with you, interactively or as a one-shot command you can script.

Install

Coming soon

The CLI is not public yet. The install command will be published here at launch. Join the waitlist to hear the day it opens.

Native binaries for macOS, Linux and Windows, on x64 and arm64.
The command is rodium. rodiumai is installed as an alias, so existing scripts keep working.
rodium update updates it, and a quiet check also runs at startup.

Sign in

Connection	How it works	Billing
RodiumAi account	Browser sign-in (OpenID Connect with PKCE). The CLI waits for the browser to call back on a local port.	The weekly FRODI allowance of your plan
RodiumAi API key	An `rd_sk_...` key from your dashboard, checked against the gateway before it is saved.	The balance of the key, in RODI

…

When the browser does not open, the sign-in URL is printed so you can copy it. Inside a session, use /login, /logout, /status and /account.

For scripts you can skip login and pass a key through the environment, or for a single run:

…

Interactive mode

…

Key or command	What it does
`Tab`	Switch between plan mode (read-only) and act mode
`Shift+Tab`	Turn tool auto-approval on or off
`@path`	Mention a file in your prompt
`Esc`	Close a menu or stop the running agent
`Esc Esc`	Restore a previous checkpoint
`Ctrl+P`	Open the command palette
`/model`	Pick a model (and switch connection)
`/account`, `/status`	Account, plan and weekly FRODI allowance
`/login`, `/logout`	Sign in or out
`/settings`	General, MCP servers, skills, rules and tools
`/history`, `/fork`, `/undo`, `/compact`, `/clear`	Manage the session
`/team <task>`	Run the task with a team of agents
`/help`	All shortcuts and commands

One-shot runs and pipes

…

The prompt must be a single quoted argument.
--json streams NDJSON events and needs a prompt or piped input.
--yolo approves every tool call and exits when the task completes.
-t, --timeout <seconds> stops the run after a deadline.
The exit code is 0 on success and 1 on failure, so it fits CI.

Tools and approvals

Tool calls are approved automatically by default. Turn that off to review each call. With auto-approval off, every call that reads files, fetches the web, edits or runs commands asks first. Plan mode (-p, --plan) explores and proposes changes without editing files.

…

MCP servers and skills

…

mcp install opens the add wizard with the fields prefilled (pass --yes to skip it). Skills are added with rodium skill add <owner/repo> and listed with rodium skill list. Skills and workflows also appear as slash commands in a session: type /skills to browse them.

Sessions and history

rodium history opens a picker to resume a session (--json for scripts).
rodium history export <id> and rodium history delete <id> export or remove one.
rodium --id <session-id> resumes a saved session directly.

Schedules

Run the agent on a schedule. Without --provider and --model, a schedule uses your current connection and model.

…

Running rodium schedule in a terminal opens an interactive wizard.

Use it from another editor (ACP)

rodium --acp runs RodiumAi as an Agent Client Protocol agent over stdio, for editors that support ACP. Example agent entry:

…

The editor signs in with your RodiumAi account. Credentials saved by rodium login and RODIUMAI_API_KEY are picked up automatically, and RODIUMAI_MODEL sets the default model.

Configuration

Settings, sessions and credentials live in ~/.rodiumai. Use --config <dir> to point at another configuration directory, or --data-dir <dir> for isolated local state. rodium config prints the current configuration (--json for scripts). Rules, workflows, skills and MCP servers are read from the workspace and from ~/.rodiumai; open /settings in a session to toggle them.

Variable	Purpose
RODIUMAI_API_KEY	API key (`rd_sk_...`) for the API key connection
RODIUMAI_ENVIRONMENT	`production` (default), `staging` or `local`
RODIUMAI_DIR	Configuration directory (default `~/.rodiumai`)
RODIUMAI_DATA_DIR	Data directory for sessions and settings
RODIUMAI_SANDBOX	`1` forces sandbox mode (isolated state)
RODIUMAI_NO_AUTO_UPDATE	`1` disables the background update check
RODIUMAI_LOG_LEVEL	`trace`, `debug`, `info` (default), `warn`, `error` or `silent`
RODIUMAI_LOG_ENABLED	`0` disables file logging
RODIUMAI_LOG_PATH	Log file path
RODIUMAI_DEBUG	`1` prints wrapper diagnostics
RODIUMAI_PROVIDER, RODIUMAI_MODEL	ACP defaults: `rodiumai` (account) or `rodium` (API key), and the model

Updates and diagnostics

…

The CLI trusts your operating system's certificate store, so it works behind TLS-inspecting proxies and with internal certificates. More in troubleshooting.