Rehearse the Trading agent kill switch
A Trading agent kill switch you have never pressed is decoration. Rehearse it in Breakflare paper mode on a schedule so live is never the first time.
Updated
A kill switch you have never pressed is decoration. Under stress, people click the familiar buttons and invent reasons to wait. Breakflare Trading agent ships with paper mode as the default for a reason: you can rehearse halt behavior until the motion is boring, before any live key discussion. This post is only about that rehearsal. For the full pre-live number set (floors, size, stops, max hold), use the guardrails checklist.
Key Takeaways
- Press the kill switch in paper on a schedule so live is never the first time.
- Document what halts versus what continues to log before you need the control.
- Do not hide the switch two menus deep “to avoid fat-fingers” and then forget the path.
- After-action review matters: why you pressed, what flattened or paused, what you change next.
- Core research still does not trade. Agent risk controls are yours to rehearse.
Where should the kill switch live in your habit?
It should live in the same mental place as your score floors: a named control you can reach without improvisation. Bookmark the path. Write it in the same note as size caps and stops. If a teammate or future-you cannot find it in thirty seconds during a calm paper session, the design of your personal runbook failed.
Hiding the control is a common false safety. Latency under stress is the real risk. Prefer a confirmed action (are you sure?) over burial.
Pair the location note with paper mode habits: you already open the agent UI regularly to read fills. Add one kill-switch touch to that cadence.
How do you run a paper rehearsal?
- Pick a calm UTC window, not a candle emergency.
- Confirm paper mode is on.
- Note open simulated positions and pending rules.
- Press the kill switch.
- Record what stopped: new entries, working exits, alerts, etc.
- Record what still logged.
- Resume or reset per your documented procedure.
- File a five-line after-action note.
Repeat weekly while you are in active paper, and again after any UI change. The goal is muscle memory, not adrenaline practice.
Operators who only rehearse after a scare teach their nervous system that the kill switch equals failure. Scheduled drills make it a normal control, which is when people actually use it.
What should halt versus what should log?
| Layer | Typical intent during kill | Why it matters |
|---|---|---|
| New entries | Halt | Stops digging |
| Risk exits / flatten policy | Follow your written rule | Ambiguity here causes hesitation |
| Research board / scores | Usually still readable | Attention research is not trading |
| Alerts | Decide consciously | Noise vs situational awareness |
| Audit log | Keep writing | After-action needs evidence |
Your environment’s exact behavior is what you document in rehearsal. Do not assume. The scoring stack and live board can stay useful for research while the agent is halted; that split is healthy. Core research never required the agent in the first place.
How does after-action review work?
Write five lines while memory is fresh:
- Trigger (drill / drawdown / dominance spike / UI test).
- Time to find and press.
- What halted.
- What surprised you.
- One process change (runbook path, size cap, floor, dominance rule).
Link process changes back to the binder: score floors, max hold and stops, Bitcoin dominance agent rules, low-confidence skips. A kill switch without follow-up edits is theater.
When should you press outside a drill?
Examples that belong in your written policy:
- Unexpected fill behavior versus floors
- Correlation pack blowing through size caps
- Personal unavailability (travel, illness) with live still on
- Exchange or key anomalies
- Regime shocks you already mapped (dominance, risk-off)
Do not wait for a perfect narrative. The switch exists because narratives arrive late. Attention columns on the 51-200 board can stay in your research loop either way; see daily watchlist workflow.
What the kill switch is not
It is not a substitute for stops and max hold. Those fire per position. Kill switch is book-level or agent-level halt. It is not a shame event. It is not proof the strategy “failed forever.” It is a control, like raising confidence floors on a thin day.
It also does not turn Breakflare into an advisory service. Hype, momentum, Climb, Breakout Score™, and confidence remain research layers (what is hype score, confidence). You own agent risk.
Graduation from paper to live still follows paper then live and trade-only key hygiene (Binance trade-only keys).
Plus is $399/mo or $3,990/yr with a 14-day trial for live ranks and paper Trading agent. Start a Plus trial when you want that rehearsal loop on the live product surface.
How often is enough rehearsal without becoming superstition?
Weekly during active paper is a solid default. After any UI change, credit change, or key permission change, run an extra drill the same day. If you have not opened the agent in two weeks, drill before you resume, even if you “still remember.” Memory of a menu path decays faster than memory of a thesis.
Avoid drills that only toggle and untoggle in one second with no note. The learning is in the observation of halt scope and the after-action line. A thirty-second ritual that produces no artifact will not help under stress.
If you operate live later, keep a lighter cadence (for example biweekly) so the path stays fresh without constantly interrupting a stable book. The kill switch is still available every day; rehearsal frequency is about readiness, not about pressing it for sport.
What shared-runbook details prevent panic?
Write: exact navigation path, confirmation prompts, whether open orders cancel, whether flatten is automatic or manual, who is allowed to resume, and where the after-action note lives. If you are solo, still write resume criteria so fear does not keep the agent halted forever after a minor drill.
Link the runbook to size and floor docs so a kill event can trigger a control review, not only an emotional cooldown. Many useful presses reveal a missing floor or an oversized pack correlation, which is a process win when captured.
How does kill switch relate to dominance and risk-off rules?
A kill switch is manual and immediate. Dominance or risk-off rules are pre-committed modifiers that may reduce size, raise floors, or pause entries automatically. You want both. Rules reduce how often you need the switch. The switch covers failures and surprises rules did not encode.
During drills, optionally simulate a dominance spike day: tighten floors, press kill, confirm halt, resume with the tighter regime. That combined rehearsal connects dominance agent rules thinking to muscle memory. Keep the after-action note explicit about which control did which job so you do not blur them later under stress.
What does a failed drill teach you?
A failed drill is any rehearsal where you cannot find the control quickly, you are unsure what halted, or you resume without a note. Failed drills are valuable if logged. They usually reveal runbook gaps, UI unfamiliarity, or unclear flatten policy.
Schedule a repeat the same day after fixing the gap. Do not wait a week; the lesson decays. If failures cluster around “I was distracted,” reduce multitasking during agent sessions rather than blaming the UI alone. Kill-switch readiness is partly environment design: one screen, runbook open, no improvisation.
Who owns resume authority?
Write whether resume requires a second look at floors and size caps, a cooling-off timer, or both. Resume that is merely “turn it back on” recreates the conditions that forced the halt. Tie resume to a mini checklist: floors still valid, size still valid, reason for halt addressed or accepted.
Frequently asked questions
Does the kill switch flatten positions?
Document the answer in your own rehearsal. Policies differ; your after-action note should state what happened in paper.
Is kill switch Plus-only?
Trading agent features are part of Plus. Research on the board does not require the agent.
Should I tell anyone I pressed it?
If you operate with partners or a future-you handoff, yes: log it. Solo operators still benefit from the five-line note.
Can I automate kill on Bitcoin dominance?
You can encode regime rules separately (dominance rules). Still rehearse the manual switch; automation fails in novel ways.
Does pressing kill mean I should quit the product?
No. It means a control worked. Fix the runbook item that forced the press, then continue paper.
Related reading
- Guardrails before live: full five-control set.
- Paper mode first: where rehearsal belongs.
- Paper then live: graduation sequence.
- Breakflare trading agent waitlist: product framing for the agent.
Start researching today's shortlist
Pay $1 for 14 days: today's live board, whales, and alerts so you can invest from research, not FOMO. Then $399/mo. Or Core at $99/mo. Cancel anytime.