Skip to main content
The autostart feature registers the Toolkit daemon with your operating system’s startup mechanism so it’s always available the moment you log in — no need to run toolkit ui or toolkit daemon by hand every session. Once enabled, the daemon starts in the background according to the mode you choose, and every Toolkit feature (proxy routes, ports inspection, hosts management, and the web dashboard) is ready before you open your first terminal.

​
Startup Modes

Toolkit supports three startup behaviors. Choose the one that fits your workflow:
Starts the Toolkit daemon silently in the background, then sends a native desktop notification once all services (proxy, API server) are ready and accepting connections.This is the recommended default — you get confirmation that Toolkit is running without any browser windows or terminal output interrupting your login flow.
Starts the Toolkit daemon in the background with no notifications and no browser windows. Toolkit simply becomes available quietly; you’ll never see a prompt or pop-up.Use this mode on machines where you want zero login-time UI disruption, or in automated/shared environments where desktop notifications aren’t appropriate.
Starts the Toolkit daemon and automatically opens the web dashboard in your default browser at http://toolkit.localhost as part of the login sequence.Use this mode if the dashboard is a core part of your daily workflow and you want it front and center the moment your session starts.

​
Enabling Autostart

1

Enable with the default mode

Run the following command to register Toolkit with your OS startup mechanism using the daemon_notify mode:
On success, you’ll see:
2

Enable in silent mode

To start the daemon at login without any notifications or browser windows, pass the --mode flag:
3

Verify the status

Confirm that autostart is registered correctly and review the active configuration:
See the Checking Status section below for a full example of the output.

​
Platform Integrations

Toolkit writes a startup entry to the appropriate OS-native location — no third-party daemon managers or elevated privileges required:
All three integrations are user-scoped — Toolkit registers under your login session only, so you never need administrator or sudo privileges to enable or disable autostart.

​
Disabling Autostart

To remove the startup entry and stop Toolkit from launching at login, run:
On success, you’ll see:
The daemon will no longer start on login. Any currently running Toolkit processes are unaffected — only future logins are changed.

​
Checking Status

Use toolkit autostart status to inspect the current autostart configuration at any time:
Example output:
The output shows:
  • Enabled — whether autostart is currently registered with the OS (YES / NO).
  • Mode — the active startup behavior (daemon_notify, daemon_silent, or browser_launch).
  • Platform — the OS detected at registration time (windows, linux, or darwin).
  • URL — the target URL the daemon will serve on startup.

​
JSON Output for Scripted Checks

Every autostart subcommand accepts a --json flag for structured output. This is useful in CI pipelines, dotfile bootstrap scripts, or any automation that needs to assert on the current state:
Example output:
You can also use --json with enable and disable to get machine-readable confirmation: