Build a TradeLocker Studio bot from a strategy idea
Describe a bot's rules and generate Python/Backtrader code for TradeLocker Studio. Refine the logic in TradeScriptAI, export the source, and test the bot in Studio.
Before you begin
You need access to TradeLocker Studio and its supported testing environment. Studio bots use Python/Backtrader; a TradingView Pine script cannot be pasted in as an executable Studio bot.
An example prompt
Create a TradeLocker Studio Python strategy using backtrader. Use a configurable 20-period simple moving average. Once the indicator is ready, buy only when the close crosses above the average and there is no position or pending order. Close the position on a cross below. Use a configurable order size supported by Studio. Track pending orders and clear them on completion, cancellation, margin failure, or rejection. No short trades or external APIs.
This is an educational specification, not a tested trading system or a performance claim.
Step-by-step workflow
1. Describe the bot as a sequence of rules
Specify the instrument, bar interval, indicator, entry condition, exit condition, and order size. Include what should happen while an order is waiting to fill. For this example, use one moving average and a single long position.
2. Generate Python for Studio
Select TradeLocker in TradeScriptAI and submit the prompt below. Check that the result uses backtrader and a strategy class, with no unrelated broker API credentials or external services. Review syntax and indicator validation results.
3. Bring the source into Studio
Open TradeLocker Studio and its strategy code workspace. Create a bot and replace the starter strategy with the complete exported Python source, following Studio's current code workflow. Save and resolve any environment-specific errors before testing.
4. Configure a historical test
Select the instrument, resolution, date period, and applicable account settings in Studio. Confirm how your environment interprets order size. Review trades and pending-order behavior, not only the final balance.
5. Inspect failures and repeat
Check that canceled or rejected orders do not leave the bot permanently blocked, and that repeated bars do not create duplicate entries. Use the available demo environment before any live deployment. Keep the source and test settings together so results can be reproduced.
Check the result against your rules
- The indicator has enough history before the first decision.
- Only one entry order can be pending at a time.
- Rejected or canceled orders clear the pending-order reference.
- The configured size matches Studio's instrument and account rules.
When something does not work
For a missing indicator, verify its Backtrader name and parameters. For a bot that stops entering, inspect whether a rejected order left a pending-order flag set. Include the full Studio error, test settings, and relevant log when requesting a correction.
What validation tells you
TradeLocker checks include Python syntax parsing and resolution of referenced Backtrader indicators. These checks do not execute a live bot or prove compatibility with every Studio environment. Import and test the result in your own Studio installation.
TradeLocker Studio: code and backtest workflowBuild with TradeScriptAI
Basic costs US$19/month and includes 50 code generations per month on one selected platform. Starter costs US$49/month and includes unlimited code generation across all three supported platforms. There is no free generation tier.
