FAQ

Connect your TradingView username in ChartMystic under Settings, Connected Accounts. Once access is granted, open TradingView, go to Indicators, and look under Invite-Only Scripts.

Access usually appears within a few minutes after you save your TradingView username. Brand-new TradingView accounts can take longer because TradingView may need time to index the username.

Open TradingView, click your profile avatar, and look for your account username. Use the username, not your email address or display name.

Atlas Pro works on TradingView's free plan. Footprint Precision Mode requires a TradingView Premium account because TradingView controls access to footprint data.

No. ChartMystic only needs your TradingView username. Never send your TradingView password to support.

ChartMystic Access is available as Weekly at $49 per week or Annual at $1,499 per year.

It includes ChartMystic TradingView indicators, the AI Pine Script assistant, real-time alerts, and priority support.

Use the in-app billing portal, contact support through in-app chat, or email support@chartmystic.com.

New subscriptions include a 30-day money-back guarantee. Contact support from the email address associated with your account.

You can contact support via live chat by clicking here.

Because it is live. The Live Bias Marker updates with the current candle as price moves — that is the design. Confirmed Signals are the closed-bar output and stay anchored to their signal bar.

Atlas Pro separates live and confirmed behavior. The Live Bias Marker can update during the current candle. Confirmed Signals are evaluated only after bar close, stay anchored to their signal bar, and historical backfill uses the same closed-bar release logic — what you see in history is what would have printed live.

Start with Balanced. It is the default and the intended baseline. Move to Aggressive only when you want more cadence and accept more noise; move to Conservative only when you want fewer, more selective Confirmed Signals.

Aggressive prints roughly 1.3× as often as Balanced. Conservative prints roughly 0.75×. The signals themselves are the same engine output — the mode controls how strict the confirmation gate is.

Use Atlas Pro Confirmed Signal for both sides. Use Atlas Pro Bullish Signal or Atlas Pro Bearish Signal if you only want one side.

Set TradingView's trigger frequency to Once Per Bar Close for any Atlas Pro confirmed signal alert. This matches the engine's closed-bar logic and prevents intrabar duplicate fires.

Atlas Pro is designed for crypto, equities, forex, and futures on any TradingView timeframe you trade.

Atlas Pro works on every TradingView timeframe, from sub-minute intervals up to weekly and monthly candles. Pick the timeframe that matches your trading horizon and test it on the symbols you actually trade.

Favorite Atlas Pro, open TradingView Pine Screener, select Atlas Pro as the study, and review the Atlas Pro Bias and Atlas Pro Setup Ready columns across your watchlist. Use it to find symbols worth opening — then confirm on the full chart.

Open Atlas Pro settings. Turn off Show Dashboard to hide it, or use Dashboard Position to move it to any corner (Top Right, Top Left, Bottom Right, Bottom Left).

Use timeframes that match your workflow. A common default ladder is 15m, 1h, 4h, and 1d, but the Multi-Timeframe Dashboard is built around your trading horizon, not a fixed ladder.

Signal History controls how many historical Confirmed Signal markers are visible on the chart: All, Current Session, or Off. It does not change which signals print — only which ones remain visible.

Scribe Studio is ChartMystic's AI Pine Script workspace. Describe an indicator or strategy in plain English — entry rules, visuals, alerts, anything — and Scribe Studio returns a working Pine Script you can paste straight into TradingView. It can also debug compiler errors, modernize old code, explain existing scripts, and approximate indicators from a screenshot.

No. Scribe Studio is designed for traders who can describe what they want but cannot or do not want to write Pine themselves. You describe the behavior; Scribe writes the code. Knowing some Pine helps you ask sharper follow-up questions, but it is not a prerequisite.

Click the copy button on Scribe's code block, open TradingView's Pine Editor (the panel at the bottom of any chart), paste the script, save it with a clear name, and click Add to chart. If TradingView shows a compile error, paste the exact error back into the same Scribe chat and ask for a fix.

Yes. Ask Scribe for a strategy() script with entry rules, exit rules, stop loss, take profit, and position sizing. Once you paste it into Pine Editor and add it to a chart, TradingView's Strategy Tester populates automatically with simulated P&L, drawdown, win rate, and a full trade list.

The entry rules may be too strict, the date range may not include qualifying setups, position sizing may be invalid, or a session/timeframe filter may be blocking entries. Ask Scribe to add diagnostic plots that visualize when each entry condition is true — that almost always reveals the cause.

Yes. Paste the indicator code and tell Scribe which condition should open a long, which should open a short, what closes the trade, and what stop, target, and position sizing to use. Scribe rewrites the script as a strategy() so TradingView's Strategy Tester can evaluate it.

Yes. Paste a script written for an older Pine version and ask for a clean, modern rewrite. Scribe updates deprecated calls, fixes namespace changes, and returns a script that compiles on the current Pine version.

Ask Scribe to add explicit alertcondition() calls for each signal you want — bullish, bearish, exit, or any custom event. Specify the alert names and the message format (including webhook JSON if needed) and Scribe returns the full updated script with those alerts wired in.