Skip to content

CLI Extensions Setup

github-actions[bot] edited this page Aug 24, 2026 · 3 revisions

ed extensions setup

Enables one extension and reports every setup step that remains.

ed extensions setup <id> [--dry-run] [--install-tools] [--json]
Option Type / values Default What it does
--dry-run flag off Project the enabled state without writing settings or installing tools
--install-tools flag off Install missing required tools without prompting
--json flag off Emit the setup result and readiness report as JSON

The command is noninteractive. It does not open the app, request a permission, create a machine, or start a backend session. Those steps appear as failed checks with actionable recovery commands. Tool installation happens only when --install-tools is explicit. The operation and the Extensions pane use the same provisioning executor and preserve per-tool failures without rolling back the enabled extension.

JSON includes dryRun, changed, plannedTools, installedTools, installFailures, and report. A tool installation failure is represented in installFailures, and incomplete readiness is represented by report.verified: false.

Only requiredTools are planned or installed. optionalTools remain visible in info, readiness checks, and extension settings, but they never block core onboarding. Install one explicitly with ed tools install <id>.

ed extensions setup quinjet --dry-run --json
ed extensions setup quinjet --install-tools
ed extensions setup calendar --json

Where to go next

CLI reference

Getting Started
Config
App
Extensions
Permissions
Usage
System
Music
Calendar
Clipboard
Color
Download
Apps
Tools
Shelf
Cleaner
Machines
Machines Remote
Machines Docker
Machines Files
Machines Power
Machines Workspace
Attention
Companion
Herdr
Lid Awake
Machines Terminal
Machines Thermal

Guides

Clone this wiki locally