Autostart

Configuration reference

Use autostart for commands that should start in your session. Add this to ~/.config/gnoblin/init.lua:

gnoblin.configure {
    autostart = {
        waybar = {command = {"waybar"}},
    },
}

Waybar and Mako are separate layer-shell clients running beside Firefox.

Install the program first. Gnoblin runs the command directly, without shell expansion; use one string for each argument. If you need pipes or redirection, explicitly run a shell.

Setting	Values	Default and effect
when	"on_login"	Starts once per login; this is the only supported trigger.
restart	"never", "on_failure", "always"	"never"; retry nonzero exits or signals with on_failure, any exit with always. Wait 2 s.

A new name starts when the config reloads if you are already logged in; otherwise it starts at the next login. See the autostart reference for launch failures.

Changing an entry does not stop a running process. If its active restart policy retries after it exits, the next launch uses the current config; otherwise the new command starts at the next login.

Do not add a program already started by your chosen shell. Bingux is one separate shell project that starts its own services.

Override an imported command

Use the same name to change its arguments:

gnoblin.configure {
    autostart = {
        waybar = {
            command = {"waybar", "--config", "/home/you/.config/waybar/work.jsonc"},
        },
    },
}

Replace the path with your own. Omitted fields keep their earlier values.

Disable an entry

Set enable = false on the named entry to prevent it starting in future sessions:

gnoblin.configure {
    autostart = {
        waybar = {enable = false},
    },
}

An unknown name adds a disabled entry. Disabling or removing an entry does not stop a process that is already running.

When does it run?

• A new name starts when the config reloads.
• Each name gets one launch per login. Saving again or unlocking does not start a second copy.
• Changing the command for an entry that already launched takes effect at the next login.
• Disabling or removing an entry does not stop its running process.

See command syntax for shell commands and configuration loading for how named entries combine across files.