Exit codes

Generated from the exit code constants in client/internal/cli/app.go and server/cmd/lasboltctl/main.go. Do not edit.

A script can use the exit code of a command to see what went wrong. The codes are stable.

lasbolt

With --json, a failed command also prints the error as JSON with a code. The codes are on the error codes page.

lasbolt run ends with the exit code of the program that it runs. If a signal ended that program, the code is 128 plus the signal number.

Code	Name in the source	Meaning
`0`	`ExitOK`	Success.
`1`	`ExitError`	Error. Something failed that has no code of its own. The message says what.
`2`	`ExitUsage`	Usage error. A command, a flag or an argument is wrong.
`3`	`ExitLoginRequired`	Login required. Nobody is logged in, the session ended, or the password or code is wrong.
`4`	`ExitOutsideScope`	Outside scope. The session or the scoped key may not do this, or may not see this item.
`5`	`ExitNotFound`	Not found. The item, folder or space does not exist, or the login cannot see it.
`6`	`ExitConflict`	Conflict. The item exists already, a sync dropped or kept user content, or the server state changed.
`7`	`ExitApproval`	Approval denied, expired or timed out. A per-use approval in the web app did not come.
`8`	`ExitUnavailable`	Server not available. The network failed, the server is down, or a rate limit applies.
`9`	`ExitLocked`	Locked. The end-to-end keys are not in memory. Run `lasbolt unlock`.
`10`	`ExitRollback`	Rollback. An end-to-end folder does not agree with a signed checkpoint, so writes to it are refused.

Code	Name in the source	Meaning
`0`	`exitOK`	Success.
`1`	`exitError`	Error.
`2`	`exitUsage`	Usage error. A command, a flag or an argument is wrong.
`3`	`exitNotFound`	Not found. The user or the invitation does not exist.
`4`	`exitDenied`	Forbidden, or a conflict such as removing the last owner.
`5`	`exitConnect`	Cannot connect to the control socket. Check that `lasboltd` runs and that you use the right `--socket`.

Code	Meaning
`0`	The server stopped after a signal, or the command ran well.
`1`	Error. The server could not start or stopped with an error. The log says why.