Skip to content

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

Bring lanes back after a reboot

Use this after a reboot or a stop of the daemon, when the lanes you had running show as idle.

A new daemon knows what each lane ran but not the shell environment it ran with (The daemon explains why), so each lane waits for a start from a shell. A plain start in a worktree brings back what its lane ran, with this shell’s environment, and names the other lanes that ran.

~/dev/myapp
$ devlanes start --no-ui

This starts every other lane that ran, in every project, with this shell’s environment. Lanes you stopped by hand stay stopped.

~/dev/myapp
$ devlanes lane resume --no-ui

A login service starts the daemon when you log in and keeps it running. The lanes still wait for a start or a resume from a shell.

Terminal window
$ devlanes daemon install

devlanes daemon uninstall removes it again.

To give your services a changed variable, such as a new PATH, restart the daemon from a shell that has it. It asks first, then starts again what every lane ran, with that shell’s environment.

~/dev/myapp
$ devlanes daemon restart

If a lane comes back failed, run a plain start in its worktree.

If a plain start should begin from scratch

Section titled “If a plain start should begin from scratch”

Set start.restore to false in the user config, and a plain start runs the lane’s default profile instead of what ran before.