Easier installation, fewer update chores
By CodeLantern Team ·
One CodeLantern sign-in installs cl-dev across Claude Code, Codex, and GitHub Copilot CLI, and released builds of the CLI keep themselves up to date.
Set up cl-dev with your CodeLantern account
Run codelantern login, then codelantern setup. Setup finds Claude Code, Codex, and GitHub Copilot CLI on your machine, shows what it will change, and installs the cl-dev plugin for each one you confirm.
The plugin downloads through CodeLantern using the CodeLantern account you signed in with, so developers don’t need a GitHub account or token to install it. The Developer Setup guide covers each step, including how to invoke skills in each agent.
The CLI keeps itself current
Released builds of the codelantern CLI update themselves. After a command finishes, the CLI checks for a newer stable release at most once an hour and installs it in the background. It replaces itself only after the download verifies, and only when it can write to its install location.
Official release builds and versioned go install builds qualify. Development builds are left as they are.
The CLI and the cl-dev plugin update separately. Keep the plugin current with your coding agent’s plugin controls.
Improvements (2)
- CLIMarketplace. Setup installs from the plugin marketplace configured for your organization and names it before you confirm.
- CLISetup. A completed run ends with a separate note that desktop apps may need a full quit and reopen before the plugin appears.
Fixes (2)
- CLISetup. Setup reads the marketplace’s name from its manifest, so enabling the plugin no longer fails when that name differs from the default.
- CLICopilot. When a Copilot install fails, setup suggests closing VS Code, which can hold Copilot’s configuration files open.
Availability
Live for members of CodeLantern customer organizations. Setup needs a CodeLantern sign-in and your organization’s configured marketplace. Automatic updates apply to official CLI releases and versioned go install builds.