Appearance
Signal parsing & AI recognition
Configure Trading Profiles → Signal parsing to help TTMT read your source's text, symbols, and follow-up commands. A parsed signal must still pass the account's trading rules and broker checks.
Start with the current parser
Current parser uses existing parsing rules and your configured phrases. In Command phrases, add the source's wording for Move SL to entry, Close position, Cancel pending order, and Add an entry. These phrases identify supported actions on the referenced TTMT-managed trade; adding a phrase does not create a new kind of trading action.
Text replacements runs literal replacements in order before parsing. Enter Find text and Replace with. Leave the replacement empty to remove a phrase; completely empty rows are ignored when saving or previewing. Preview representative messages after each change so a broad replacement does not change other signals unexpectedly.
Configure symbol mapping separately to resolve source instruments to broker names.
Choose an AI mode
| Signal recognition mode | Behavior |
|---|---|
| Current parser | Uses existing rules and configured phrases. |
| Try AI | Lets you inspect AI results without executing AI-derived signals. The existing parser still runs first. |
| Parser + AI | Uses AI when the current parser cannot read a message. |
Try AI is not a workspace-wide trading pause: messages understood by the existing parser may still follow the normal execution path. Use channel monitor-only routing if you intend to observe signals without sending trading commands.
AI recognition and AI-derived execution have separate server controls. Parser + AI can recognize a message while AI-derived execution remains disabled. A saved key or AI recognition enabled on server does not establish permission to trade AI-derived results. Ambiguous messages require review, and image parsing is not supported.
AI recognition is intended to read unfamiliar signal text, reply commands, and edits. Availability depends on server enablement and provider configuration. It does not guarantee that every message can be interpreted or that an inferred action will be accepted.
Configure a provider
The current interface supports workspace API keys for OpenAI, Gemini, DeepSeek, and Claude. Compatible endpoint is not currently selectable for workspace API keys.
- Select the provider in AI signal recognition.
- In Your workspace API key, check whether AI recognition enabled on server is shown.
- Enter the provider's API key and select the model offered by the interface.
- Select Save API key or Replace API key.
- Preview representative signals, inspect results, then save and apply the intended profile version.
The key is encrypted on the backend, scoped to the workspace, and is not returned to the browser. Provider usage is billed to your provider account. Provider credentials are workspace settings; saving the key is separate from saving or applying a profile.
API key saved does not mean the provider connection has been tested. Removing the workspace key makes AI parsing through that credential unavailable. Check the displayed server/provider status rather than assuming that selecting an AI mode alone enables it.
Troubleshoot recognition
If a message is not read, first inspect replacements, command phrases, source wording, and selected mode. If AI is unavailable, check server enablement, saved provider/model settings, and provider account access. If the message is read but no trade occurs, inspect routing, the applied profile, filters, and broker execution results instead.
Preview can use unsaved editor changes; channel execution uses the account's confirmed saved configuration. Save and apply the exact version you intend to use before comparing those outcomes.