Prebuilt strategies can take you far, but sometimes your edge lives in logic that does not fit neatly into preset indicator stacks. Gimmer’s Script strategy gives you a TypeScript-based way to express that logic, test it, and operate it inside the same strategy workspace.
Why Use the Script Strategy?
Not every trading idea is a basic crossover or a fixed checklist of indicators. Some approaches depend on how the portfolio is positioned, how one asset behaves relative to the rest of the basket, or how several conditions combine before a trade should happen.
That is where Gimmer’s Script strategy becomes useful. Instead of wiring together predefined rules only, you can write a TypeScript handler that decides whether the current market state should produce a buy, sell, or neutral signal.
What the Editor Exposes
The current Gimmer strategy flow includes a dedicated code editor for Script strategies. Inside that editor, the typed context object gives your logic access to the pieces that matter most when evaluating a decision:
- Bot context for the strategy that is running
- Strategy settings such as timeframe and order sizing
- Portfolio data including quote balance and tracked assets
- OHLCV market data for the current pair
In practice, that means you can write rules that are aware of both market structure and portfolio state instead of reacting to a single indicator in isolation.
TypeScript Instead of Guesswork
Gimmer uses a Monaco-based editor for this workflow, which makes the Script strategy feel closer to a real development surface than a plain text box. The editor is set up for TypeScript and includes ready-to-use typing for the strategy context, so you can see what data is available while you write.
That matters because faster iteration is not just about writing code quickly. It is about writing logic with fewer assumptions, fewer hidden inputs, and fewer surprises when the strategy runs.
How the Workflow Fits Together
The Script strategy is not isolated from the rest of the product. It sits inside the same builder flow as other strategies, which keeps the process operational instead of experimental-only.
- Config: define the exchange, timeframe, quote currency, base assets, and the script itself
- Backtest: run the strategy against historical data and review performance, drawdown, and position history
- Activity: monitor how a saved strategy behaves once it is active
- Publish: prepare seller profile details, strategy metadata, and pricing plans if you want to package a strategy for marketplace distribution
This is the part many traders underestimate. A scripting surface is useful, but a scripting surface tied directly to backtesting and operational review is what makes it practical.
Who This Is Best For
The TypeScript Code Editor is a strong fit if you want to:
- Turn a discretionary trading idea into explicit rules
- Use portfolio-aware logic instead of single-indicator triggers
- Experiment with custom signal generation before going live
- Keep custom strategy logic inside the same product workflow as configuration, backtesting, and distribution
It is not a shortcut to better performance by itself. You still need clear logic, sensible risk controls, and disciplined validation. But if your edge depends on something more specific than preset blocks, the Script strategy gives you a structured way to express it.
Final Thoughts
There is a big difference between having an idea and being able to operate that idea consistently. Gimmer’s TypeScript Code Editor closes that gap by letting you move from concept to coded signal inside a workflow that already includes configuration, backtesting, monitoring, and marketplace preparation.
Want more control over how your trading logic is defined? Download Gimmer and explore what you can build with the Script strategy.
— The Gimmer Team
