Skip to content

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

States and exit codes

devlanes status, the TUI and --json output report a state for each unit and lane. Each command ends with an exit code that scripts and agents can act on.

StateMeaning
idleA service that has not run since the daemon started.
queuedWaiting for its turn to start.
startingA service whose process runs and whose ready check has not passed yet.
readyA service whose process runs and whose ready check passed.
runningA task, exec command, or setup or teardown entry whose process runs.
exitedA task, exec command, or setup or teardown entry that ended with exit code 0.
failedThe process exited with another code, could not start, or did not pass its ready check.
stoppingA stop was sent and the process has not ended yet.
stoppedEnded by a stop, or a service that ended by itself with exit code 0.
orphanedA process an earlier daemon started that still runs, unsupervised. devlanes stop ends it.
externalAn infra.external entry: devlanes routes to it and runs nothing.

A unit stays failed until you act on it. devlanes stop NAME clears a failed service or exec command; a failed task stays failed until it runs again.

Human output and the TUI show a ready service of an unused lane as throttled or frozen (Throttling and freezing). JSON keeps state: ready and adds power.

StateMeaning
startingA start is under way, or a service is starting.
runningA unit of the lane runs.
failedA service of the lane has failed.
stoppingThe whole lane is stopping.
idleNothing of the lane runs.
unassignedThe lane has no number or no ports yet, such as when the port pool is full.
no-configThe worktree has no project file for this project.
CodeMeaning
0Success.
1Failure. status also exits 1 while a unit it shows has failed.
2Usage error, or a confirmation that needs --yes.
3A lane, unit or project that matches nothing or several things, or no devlanes.yaml in the directory or its parents.
4The daemon cannot be reached or cannot start.
124--timeout passed before the units were ready.
130Ctrl-C detached the command and left the units running.

devlanes with exits with the code of the command it ran, and devlanes run with the code of the task.

ModeOutput
humanColors and symbols, for a person at a terminal.
plainThe same information without color, one line per event.
agentTerse lines for coding agents: failures first, each with the command to run next, capped in size.
jsonThe daemon’s data as JSON.

--output MODE or --json chooses the mode, then DEVLANES_OUTPUT. Without them, devlanes uses agent when a coding agent runs it, plain in CI or without a terminal, and human otherwise.

With --json, a command prints one JSON document. A list has the fields items, truncated and next_cursor. Commands that stream, such as start, logs -f and debug events, print one JSON object per line. Errors print as error: and hint: lines on standard error in every mode, --json included.