← Back to KillSwitch

THE HUMAN OVERRIDE / INTERACTIVE TOUR

Your command.
Their full stop.

Watch the control model in action. Introduce an incident, detonate the kill switch, and see how a human decision becomes a coordinated shutdown.

BROWSER SIMULATION · NO LIVE CONNECTIONS

Illustrative sequence. Animation timing is not a product benchmark.

01 / CHOOSE YOUR SCENARIO
KILLSWITCH / HUMAN CONTROL PLANEDEMO ENVIRONMENTRUNNING
CONNECTED SYSTEM

agent-workflow-01

Execution path Human authority
A human controls the kill switch independently of the AI agentAn agent and two child workloads have access to tools, credentials, and a network. The human can stop execution and revoke access through a separate control plane. AGENT EXECUTION BOUNDARY AUTHORITY TO STOP Human operatorTHE FINAL SAY KillSwitch control planeOUTSIDE AGENT AUTHORITY ✳Primary agentRUNNING Research agentRUNNING Execution agentRUNNING Tools & integrationsCONNECTED API credentialsVALID Network egressOPEN CONTAINED / HUMAN HOLD
HUMAN OPERATOR FINAL SAY
KillSwitch control planeOutside the agent’s authority
AGENT EXECUTION BOUNDARY
Primary agentRUNNING
Research agentRUNNING
Execution agentRUNNING
TOOLSCONNECTED
API KEYSVALID
NETWORKOPEN
CONTAINED / HUMAN HOLD
EXECUTION NODES3 running
ACCESS PATHS3 connected
RESTART AUTHORITYHuman only
03 / THE SHUTDOWN SEQUENCEAWAITING HUMAN COMMAND
  1. 01
    Accept overrideA human makes the call
  2. 02
    Stop executionRoot & child workloads
  3. 03
    Block accessTools & network paths
  4. 04
    Revoke credentialsNo authority to act
  5. 05
    Hold & verifyEvidence. Human review.
ILLUSTRATIVE EVENT LOGSESSION READY
    HUMAN AUTHORITY REMAINS AVAILABLESIMULATION ONLY / NO LIVE AGENTS

    04 / BEHIND THE SWITCH

    One decision.
    A coordinated response.

    The product direction, made visible.
    Each enforcement path needs a real integration.

    CONTROL

    A separate authority.

    The stop command originates outside the agent’s own permissions. Human control remains available after agent execution is halted.

    CONTAIN + REVOKE

    Cut the ability to act.

    Stop connected workloads, block their tools and network paths, and revoke credentials at the issuer. Verify each path independently.

    RECOVER

    A deliberate restart.

    Keep incident evidence, review the cause, and require human approval before restoring a workload’s execution or access.

    A real kill switch only covers integrated systems under your authority. Unconnected agents, independent copies, and completed actions need separate response procedures.

    TURN THE CONCEPT INTO A PLAN

    Map your own off switch.

    KILLSWITCH / SHUTDOWN PLANNER

    YOUR FIRST CONTINGENCY PLAN

    Before you deploy,
    define the stop.

    Create a practical starting brief for your team. Everything stays in your browser.

    What can your agents access?

    A planning worksheet, not an active security control.

    KILLSWITCH / SITE PRIVACY

    Your plan stays yours.

    The shutdown planner runs in your browser. Your answers are not submitted to KillSwitch Security or stored by the site. Downloading a brief creates a text file on your device.

    The demo is a local simulation. We do not add advertising or analytics trackers. Cloudflare processes requests and security checks to operate this website.

    If you use the contact form, your name, email, and message are sent to KillSwitch so we can reply. Cloudflare helps deliver messages and block spam.

    Your light or dark theme choice is saved in this browser so it follows you between pages. The setting is not sent to KillSwitch.

    KILLSWITCH / HUMAN-AUTHORIZED RECOVERY

    04 / RECOVERY STAYS HUMAN

    Stopped means stopped.
    Until you decide.

    In this demo, a restart stays locked until you complete the review below. These acknowledgements reset the simulation only.

    ✓ Simulated execution nodes stopped
    ✓ Tool, credential, and network access cut
    ✓ Illustrative incident record preserved

    No real workloads, credentials, or infrastructure will be changed.