Commands and browser controls
A practical command list, including what update and publish actually do.
On this page
CraftOS commands
| Command | Behavior |
|---|---|
| lantern | Browser, or server tools for a hosting-tools profile |
| lantern hub://help/ | Open a Hub site |
| lantern ln://my-site/ | Open a modem site |
| lantern edit [name] | Create or manage a local site |
| lantern host [name] [--headless] | Server tools, or serve a named local site |
| lantern publish <name> | Upload a Hub draft; publish separately on the website |
| lantern hub https://host.example | Set an HTTPS Hub origin; not a browsing command |
| lantern seed <file> | Import a unique seed and remove its source file |
| lantern doctor | Show runtime, terminal, modem and installation diagnostics |
| lantern trust reset <alias> | Remove a saved identity pin after typing the alias |
| lantern update [installer-path] | Check and install the latest signed release; an optional path runs a trusted local installer |
| lantern repair [installer-path] | Run a trusted installer already present on disk |
| lantern uninstall | Remove program after confirmation; preserve user data |
Install the latest preview
Lantern 0.2.0 and later automatically check for and install newer signed releases when you launch the browser, hosting tools or editor. Choose Check for updates in the browser menu, or run lantern update, to check manually. Older installations need the command above once to gain this updater.
Updates preserve your installation profile, sites, settings, security state and startup entries. If HTTP is blocked, the service is unavailable or verification fails, the installed version continues to run. A small signed announcement is checked first; application files download only for a newer release. Interrupted activation rolls back on restart. The repair command still runs a trusted local installer.
wget run https://lantern.thultz.dev/downloads/lantern.luaOffline installation and backups
If HTTP is blocked, transfer a trusted offline install-lantern.lua bundle to the computer and run it there. Do not transfer someone else’s initialized security state.
Back up site sources and data before experimenting. Uninstall preserves /lantern-data. Private identity files and upload keys need confidential backups; public website packages must never contain them.
Found a mismatch? Include the exact error, runtime version and a small example with secrets removed.