Skip to main content

Helix improves your playbook

Ask Helix to tighten the plan you are already on, and it proposes a discipline rule you can add with one tap.

Tighten the plan you are on

When Helix spots a pattern in your trading that a guardrail would help, it does not build you a whole new plan. It offers to improve the one you are already committed to. You might ask "how do I stop revenge trading?" or "help me tighten my plan", and if the data backs it up, Helix suggests a rule to add, like a cap on new entries right after a loss, or a lower daily trade count.


Open Helix from the sidebar, or press the Ask Helix button at the top of the nav, and ask about a habit you want to fix.


Helix improves your playbook, screenshot 1


What the card shows

The suggestion arrives as a card tagged Suggested action, labelled Improve playbook. It names the playbook you are on and lists what it would add under an Adding heading, each proposed rule marked with a +. This is a preview of the addition on top of your current rules. Nothing changes on your plan while the card sits there.


If the plan you are on already holds you as tight or tighter, Helix says so in the chat and offers a stricter version or leaves it alone. It surfaces the idea, it never loosens what you already have.


Helix improves your playbook, screenshot 2


Apply merges it in

Choose Apply to add the rule, or Dismiss to pass. Applying merges the new rule into your active playbook, it never overwrites what is there. Everything you already had stays, the new rule joins it, and the card confirms with Added to your playbook. Your grading starts counting the new rule from your next trade on.


On a prop-firm or template playbook, the rules you layer on show up in their own Your added rules area, kept separate from the challenge's own locked rules. Those stay exactly as the firm set them. Each rule you added carries a Remove control, so taking one off your next trade is one tap, and the play's own rules stay locked either way.


Helix improves your playbook, screenshot 3


Did this answer your question?