nuke

NAME

nuke — completely reset the SLICC environment

SYNOPSIS

nuke <launch-code>

DESCRIPTION

Performs a total, irreversible reset of the SLICC environment. Deletes all local data — the virtual filesystem, chat history, scoops database, scheduled tasks, and all other persisted state — then unregisters the service worker and reloads the page from a clean slate.

This command exists as a last resort. It is the equivalent of a factory reset.

LAUNCH CODE

As a safety mechanism, nuke requires a secret launch code to execute. Running nuke without the correct code prints a warning and exits with a non-zero status. The launch code prevents accidental invocation — you must already know the code to use it.

If you run nuke without the code (or with the wrong one):

⚠️  WARNING: this will reset the entire environment, file system, chats, and scoops.
Run nuke again with the secret launch code to proceed.

WHAT IT DESTROYS

• VFS — all files in the virtual filesystem (/workspace, /scoops, /shared)
• Chat history — every conversation, gone
• Scoops — all sub-agent records and their workspaces
• Cron tasks — all scheduled recurring jobs
• Webhooks — all registered webhook endpoints
• Mounts — all filesystem mount configurations
• Sprinkles — all persistent UI panels
• Service worker — unregistered and cleared
• IndexedDB — every database SLICC has created

In short: everything stored locally in the browser is deleted.

WHAT SURVIVES

• Provider configuration — API keys and LLM provider settings (stored in localStorage, preserved by design)
• Secrets — any credentials stored externally
• Layout preferences — basic UI settings in localStorage

WHEN TO USE

• Corrupted state — when the environment is broken and no other fix works
• Fresh start — when you want a clean slate without residual data
• Testing — to reset between test runs during development

WARNING

This operation is irreversible. There is no undo, no confirmation prompt beyond the launch code, and no recovery mechanism. Once executed, all local data is permanently destroyed.

If you have files or configuration worth preserving, back them up first using mount to sync to an external source before running nuke.

SEE ALSO

mount — attach external filesystems (use to back up data before nuking)