Setup
Install managed components such as DuckDB from the CLI, with a plan you approve first.
Some features need extra software that doesn't ship in the rolit binary. Setup downloads and configures these managed components for you. Today the example is duckdb, which powers data queries and charts.
Setup never installs anything unattended. It shows a plan (the steps, download hosts, and sizes), asks for your confirmation, and needs an interactive terminal.
From the command line
rolit setup # list components and their state
rolit setup duckdb # show the plan and ask before installing
rolit setup duckdb install
rolit setup duckdb status
rolit setup duckdb remove| Argument or flag | Meaning |
|---|---|
[component] | A component id. Omit it to list all components and their state. |
[action] | install, status, or remove. |
--yes | Skips the confirmation question. A terminal is still required. |
--json | Machine-readable output. |
From chat
| Command | What it does |
|---|---|
/setup | Opens the component list. |
/setup <component> | Shows that component's plan and asks before installing. |
/setup on | Gives the agent tools to help with installs. Off by default. |
/setup off | Removes those tools. |
/setup on and off are saved per workspace and restart the session in place, keeping your history. The panel works whether or not setup mode is on.
Setup mode for the agent
With /setup on, the agent can plan an install, start it after you approve the plan, watch its progress, and diagnose and repair failures. It only names a component. It never supplies URLs, versions, paths, or commands.
| Tool | What it does |
|---|---|
setup.list | Components, platform support, and health |
setup.plan | Steps, download hosts, and sizes. Changes nothing. |
setup.run | Starts an install after you approve the plan card |
setup.status | Phase, per-step status, and recent events |
setup.wait | Waits up to 120 seconds for the next step or completion |
setup.diagnose | The failing step, a redacted log tail, and the repairs on offer |
setup.repair | Applies one offered repair, at most 3 per step |
setup.cancel | Cancels cooperatively |
setup.run and setup.repair need explicit consent every time. They are denied in plan-only, never skipped by session Auto, and never available to subagents. Failure text and logs are redacted before the agent sees them.
When an install fails
A step with no progress for 60 seconds fails as step_stalled. Each step also has a deadline (step_timeout), and the whole run has an overall one (setup_timeout). Ask the agent to diagnose it in setup mode, or run rolit setup <component> status and rolit doctor.