CLOUDPips Kumo Setup Guide

This guide goes through Kumo's Inputs tab, group by group. Just starting? Load Default.set and change only RiskPercent: every default is the setting we backtested.

Start Kumo in 3 steps

  1. Attach Kumo to an XAUUSD chart set to D1. The chart's timeframe only affects how the chart loads: Kumo reads the timeframes it needs by itself
  2. Rented on cloudpips.io: paste your License Key (it starts with CPK-) into License_Key, the first row of the Inputs tab. It's in My licenses (bought on MQL5? skip this)
  3. Load Default.set with Load in the Inputs tab (choose and download a preset)

Every signal the bot skips is printed in the Experts tab with the reason.

Every setting in the Inputs tab

In the same order as MT5's Inputs tab. Every default is the setting we backtested. If you change a strategy setting, run your own backtest first.

Setting Default What it does
License_Key empty Your License Key from cloudpips.io, pasted with no spaces before or after (rented version only; the MQL5 version doesn't have it)
TradeDirection BOTH Which side may trade: both, buy only, or sell only
Level_Timeframe H4 Timeframe of the high and low that price must break. Kumo draws these levels on the chart. A bigger timeframe = fewer trades, held longer
Enable_Level2 false Also trade breakouts of a second timeframe = more trades
Level_Timeframe2 H1 The second timeframe (when Enable_Level2 is on)
Skip_Against_Structure true Skip breakouts against that timeframe's market structure = trade only with the main direction
Trend_Filter_Timeframe off Trade only in the direction of the chosen timeframe's structure
Entry_Timeframe M5 A candle on this timeframe must close beyond the level before Kumo enters, so a wick alone doesn't count
Other settings in Breakout Levels – Confirm the swings
SL_Mode ATR How each trade's first stop loss is placed, such as from market volatility or beyond a swing. A wider stop = a smaller lot at the same risk
Other settings in Stop Loss – The stop distance for each method
Trail_Mode Supertrend How the stop follows the profit. There's no fixed take profit: a trade runs until the trailing stop is hit, so winners can go far
ST_Exit_On_Flip true Close the trade as soon as the trend turns, without waiting for the stop
Other settings in Exit: Trailing Stop – The distance for each method
Enable_Kaze_Filter true Wind filter: trade only when the market is active enough, skipping signals in a quiet market. The current Kaze level is on the panel
Kaze_Min 1.0 Minimum activity: 1.0 = as active as usual for that time of day. Higher = fewer trades
Kaze_Require_Rising true The activity must also be rising
RiskPercent 1.0 The main one to change. Risk per trade as a % of balance: roughly what a stop loss costs. Default.set uses 1, Aggressive.set 2. If the balance is so small that the lot falls below your broker's minimum, Kumo uses the minimum lot, so the real risk is higher (use a Cent account for small balances)
Fixed_Lot 0.0 A fixed lot size instead of RiskPercent (0 = use RiskPercent)
Max_Lot 0.0 The largest lot per trade (0 = no limit)
Use_SL_TP true Leave it at true: every trade has its own stop loss, as in every preset. false = an experimental basket mode: trades open without a stop loss and close only all together
Basket_TP_Pct 0.0 Basket mode only: close all trades when their open profit reaches this % of balance
Basket_SL_Pct 0.0 Basket mode only: close all trades when their open loss reaches this % of balance (0 = off)
Max_Open_Positions 0 Basket mode only: the most trades open at once (0 = no limit)
Enable_EquityTP false Close all positions at once when combined open profit reaches a target, then keep trading. It watches the whole account, so other bots' trades count too
Internal_EquityTP_Pct 0 The open-profit target as a % of balance
Enable_TargetProfit false Stop trading when profit reaches a target: Kumo closes all its trades and stops until you restart it from the panel
TargetProfitPct 0.0 The profit target as a %, from the balance at the start of the cycle
Enable_DrawdownCut false Emergency drawdown cut: close all trades and stop the bot. A last safety net; if you turn it on, set it at a level you can genuinely live with
MaxDrawdownPct 0.0 The open loss, as a % of balance, that triggers the cut
Enable_DailySLLimit false Stop for the rest of the day after a number of stop losses (days follow your broker's server time)
Max_Daily_SL_Hits 0 Most losing trades per day
Enable_DailyTPLimit false Stop for the rest of the day after a number of winners
Max_Daily_TP_Hits 0 Most winning trades per day
Enable_DistanceFilter false Don't open a new trade too close to an existing one
Min_Distance_Points 1000 Minimum distance from an open position (points)
Structure_Timeframes M5,M15,H1,H4,D1 Timeframes whose market structure the panel shows (display only, no effect on trading)
Draw_Levels_On_Chart true Draw the breakout levels on the chart
Enable_WithdrawSim true Show the withdrawal simulator box on the chart
Withdraw_Profit_Pct 50.0 % of each profitable day's profit to simulate withdrawing
Magic_Number 778811 Kumo's ID for its own trades, to tell them apart from others. Change it and the panel's figures start from zero

Changing settings while running

  1. Double-click the EA's name in the top-right corner of the chart (or press F7)
  2. Edit the values in the Inputs tab and press OK

Open trades stay open with their stop loss. On MQL5 Virtual Hosting, Migrate again after changing settings.

Capital and VPS

  • Minimum balance: 1,000 USD on a Standard account, or 10,000 USC on a Cent account ($100). See How much capital do I need?
  • VPS: recommended, so the bot looks after its trades 24/5. See Set Up a VPS
  • Running Kumo with another CLOUDPips bot: use a Hedging account and set RiskPercent to 0.5 on each. Don't pair it with Hoshi, which already has Kumo's main breakout entry. See Can I run two bots on the same account?

Next step

Choose the preset that suits your account: Kumo Presets Compared (Default, Aggressive)

More help

Updated 7 November 2026

Still stuck? Email us at support@cloudpips.io or message LINE @cloudpipsfx and we'll help you sort it out.