Skip to content

devlanes is in beta and not ready for production use.Report an issue

Update and uninstall

devlanes keeps itself up to date. It installs patch releases in the background and they apply the next time you start devlanes at a terminal. Use this for a release that waits for you, to change how devlanes updates, or to remove it.

An install made with cargo, or as a dependency of a project, does not update itself. devlanes update says what to run or change instead.

A minor release can change how things work, so it waits for you. devlanes tells you when one is out.

Terminal window
$ devlanes update

The command asks once, installs the latest release the way you installed devlanes, and restarts the daemon, which stops your running services and starts them again on the new version. A minor release lists its breaking changes first. Without a terminal, add --yes.

A box, a machine whose lanes are mirrored to yours, needs its own update: run the same command there. Two machines on releases with different protocols do not connect.

Set updates.mode in the user config, then restart the daemon. With notify devlanes only tells you about a new release, and with disable it never checks.

~/.devlanes/config.yaml
updates:
mode: notify
Terminal window
$ devlanes daemon restart

An update you ask for still works.

Terminal window
$ devlanes uninstall

The command stops the daemon, undoes what devlanes setup changed, including the CA trust, and removes the install. It then lists the devlanes home and the lane data, and deletes them only if you answer yes. --dry-run shows the plan without changing anything.

Containers stay in Docker with their volumes, and so do the folders services sync build output to, the MCP server registered with your agents and the skill. To remove each lane’s own containers first, see Remove lanes.

If you want to try builds of the main branch

Section titled “If you want to try builds of the main branch”

The newest build of main that passed CI is published as the next build, and the install script installs it with --channel next. From then on, updates stay on next builds.

macOS

Terminal window
$ curl -fsSL https://devlanes.run/install.sh | sh -s -- --channel next

Linux

Terminal window
$ curl -fsSL https://devlanes.run/install.sh | sh -s -- --channel next

Windows

Terminal window
PS> iex "& {$(irm https://devlanes.run/install.ps1)} -Channel next"

Uninstall with --keep-data, then install and run the setup again, as Install devlanes shows.