Start from your level of knowledge
Discuss your goals and recurring difficulties. Ask for explanations at your pace and a follow-up question that helps you check your own understanding.
Ask your chart. Understand the answer.
Discuss market structures and strategies with your AI coach. Get connections explained and important areas marked on the chart.
A conversation that starts with your analysis.
Your question does not have to start from scratch. The coach can use available chart context and selected visible content from your current view. Discuss observations where you are already examining them.
Open the context
Choose an instrument, data source and timeframe. For chart questions, open chart analysis and then the bot. For questions about metrics, select the relevant results view. Check that the content you need has loaded.
Ask a specific question
Describe your observation and what you want to understand. Identify the relevant zone, metric or rule and ask for counterarguments.
Check the tool action
For supported chart actions, inspect the actual change. Describing an intention does not mean an action was successfully completed.
Investigate the next assumption
Compare the explanation with the data. Record missing conditions, refine your question and test rules in the appropriate tool.
A chart annotation becomes useful when you understand its reasoning.
Ask the coach to distinguish observation, missing confirmation and invalidation. A marked zone should help you examine a hypothesis.
What can you observe?
In this example, prices react several times at a lower zone. The observation describes behaviour that has already occurred.
What is still missing?
A rise towards resistance is not a confirmed breakout. Ask about the required closing price and additional conditions.
What would contradict it?
A break of the lower zone could challenge the hypothesis. Define in advance which observation would change your assessment.
Three questions that help you discover more.
Open an example to see how to formulate a question you can check. These texts illustrate a possible learning direction; no AI request is sent.
Make a chart idea visible
Your question
Mark a relevant support zone on the loaded chart. Explain its basis, missing confirmation and what contradicts my breakout idea.
What to look for in the answer
A useful explanation identifies the observed price points and separates them from interpretation. After a supported drawing action, check the actual anchors and visible zone. Missing data must not be replaced by invented precision.
Understand a backtest better
Your question
Explain the visible metrics of this backtest. How do drawdown, closed trade count and results relate? What information do I need for a comparison?
What to look for in the answer
The coach can interpret the visible page context provided to it. Compare period, source, sample and cost assumptions. Start a new test or optimisation yourself in the backtest tool; an explanation alone does not calculate a new result.
Challenge your own conviction
Your question
I find this setup convincing. Formulate a plausible alternative hypothesis, identify missing conditions and help me describe my risk rule clearly.
What to look for in the answer
Look for specific reasons against the idea and an observation that distinguishes the scenarios. Entry, stop, target and position size belong together. A plausible explanation replaces neither verified numbers nor your decision.
What you can investigate with the coach.
Availability follows your current workspace, data rights and supported tools. Check the outcome after every action.
Chart view and instrument
Supported actions can change the instrument, timeframe or chart presentation. A switch does not add missing data or extend permissions.
Drawings and price areas
Discuss supported lines, zones, labels and Fibonacci tools. Check price and time anchors. Changes apply to the drawings actually addressed.
Indicators in context
Supported indicators can be added, changed or removed. Ask which inputs and parameters determine the interpretation and whether the indicator fits your question.
Explain visible results
Selected visible metrics and tables from Seasonality, screener, backtest or journal can provide page context. This does not give the coach full access to hidden records, private rules or draft form fields.
Turn an idea into clear rules
Ask for explanations of conditions, alternatives and useful checks. Develop and validate executable strategies in the builder using its available components; it has its own copilot.
Discuss risk and invalidation
Describe entry, stop and target with their assumptions. Ask about contradictions or missing information. Supported chart objects are analytical aids; the coach does not place broker orders.
Turn an answer into your next learning step.
Choose a manageable idea and focus on one question. Write down the rule before testing, instead of searching afterwards only for an explanation of an attractive result.
Explain it in your own words
Summarise what supports the hypothesis, what is missing and what would invalidate it. Ask again if a term is unclear.
Make it a testable rule
Transfer supported conditions to the strategy builder. Define entry, exit and risk, then validate the saved version.
Investigate it historically
Start a suitable backtest yourself. Compare assumptions and losing periods. Then discuss the visible results with the coach.
Your learning journey can be personal.
If you enable personal memory, the coach can consider the goals, experience, preferred markets and risk rules you share. You decide which memories to keep.
Separate statements from assumptions
Your own information and the coach’s tentative hypotheses are not the same. Review memories, correct misunderstandings and update goals that have changed.
Manage your own memories
You can turn memory off and review, correct, export or delete saved memories. Personal context is not global model training.
Write or speak.
Depending on your browser and enabled availability, you can use text, a microphone or a WAV recording and have answers read aloud. Check microphone permission, available audio features and the cost budget before use.
Keep track of your usage and balance.
AI usage requires an active account, sufficient credits and the relevant feature and data rights. Measured usage is deducted from your prepaid balance; cost approvals and your account balance remain authoritative.
Explore plans and access100 free credits for new registrations are planned. Their allocation has not yet been confirmed. Rely on the balance actually shown in your account.
Enter only information you wish to share for your question. The chart and page context provided is limited; it does not imply access to your entire account.
Discover four coaching stylesHow to recognise a useful answer.
Evidence rather than simple agreement
The answer should distinguish observation, interpretation and assumption. Ask explicitly for counterarguments, missing conditions and uncertainty.
An actual result for an actual action
Check whether the chart has really changed. A failed or unsupported action must not count as completed. Start screener scans, backtests and optimisations in their own tools.
Suitable data for your question
Source, period and timeframe determine what you can infer. Tick volume is not traded volume; offered broker liquidity is not an executed trade. Missing context limits the explanation.
Your judgement remains essential
AI can make mistakes and miss important circumstances. Historical patterns are not reliable predictions. Use the coach to understand and investigate, without treating its explanation as a promise of profit.
Frequently asked questions
Can the assistant be wrong?
Yes. An explanation can be incomplete or mistaken, especially when the data or question is ambiguous. Ask for the basis, inspect the actual chart and check whether a claimed tool action produced a real result.
Do the four styles have different data rights?
No. Choosing Lumo, Scalpo, Sapiens or Strategos changes the coaching style. It does not add market data, unlock a plan feature or replace your existing credit balance.
What is a good first question?
Try: which conditions support this interpretation, which are missing and where would it become invalid? Refer to a specific instrument and timeframe, then compare the explanation with the information actually available in the workspace.