Author with AI Companion

Brainstorm a Strategy without code

AI Companion is the no-code path for brainstorming, questioning, and shaping a Strategy idea in plain language. Use it to turn a trading hypothesis into a reviewable specification before entering supported rules in Visual Composer or implementing a Python Strategy SDK plugin.

It does not directly save a Strategy, change the Strategy Library, select data, or prove that a rule is sound. You remain responsible for the final Strategy definition and validation.

AI Companion is for no-code brainstorming, alternative rules, assumptions, and a clear authoring checklist. It does not create, test, sync, or publish a Strategy.

Visual Composer is for building supported rules without code. It does not create arbitrary Python logic.

Strategy SDK is for writing and testing a local Python Strategy plugin. It is not a no-code authoring surface.

Ask for a useful specification

Give the Companion the decision you want to make and ask it to expose missing choices. For example:

Help me specify a Long-only Strategy that enters when close crosses above a
reviewed trend Signal. Ask me to resolve the input version, decision timing,
entry and exit rules, position policy, risk behavior, order assumptions, and
data requirements. Return assumptions, unresolved decisions, validation risks,
and a Visual Composer checklist. Do not claim the Strategy is saved or ready.

Do not paste credentials, account details, proprietary source code, or data you are not allowed to share with the selected model provider.

Review the idea before authoring

Before transferring a suggestion into Composer or Python, confirm:

• the exact market fields and Signal outputs it needs;
• when each input is available and how it avoids future information;
• parameter names, units, defaults, and sensible bounds;
• Long/Short entry and exit behavior;
• position, conflict, and risk handling;
• required data shape and execution assumptions; and
• tests or counterexamples that could disprove the rule.

Use the Companion to challenge your assumptions, create small scenarios, or explain a rule in plainer language. Do not accept a proposed rule simply because it sounds technical or complete.

Choose the implementation path

Use Visual Composer when the accepted rule fits the available no-code controls. Use Strategy SDK when the reviewed rule needs Python code, source control, or reusable builder logic.

In both paths, inspect the saved Strategy in Strategy Library, then validate it against the actual Dataset and time window before creating a Study. An AI answer is not a test result, a data-quality check, or a prediction of trading results.