Tech Stock Watch
The scanner requests a new strategy iteration when a new candle appears on the selected timeframe.
Manual click · New candle · SL/TP watcher · Stop loss, Take profit
Published strategy and runtime controls
This page presents the platform agent configuration as a read-only public view. No visitor can save, deploy, pause, delete or manually run this agent.
You can inspect the same instruments, files, sources, prompts, risk controls and runtime options available in Agent Studio. The published values cannot be edited, saved or applied from this public page.
Build the agent from inputs to execution
Files and market context flow into the strategy prompts. Force over prompt controls then define the boundaries the model cannot override.
Choose instruments and sources. The matching input files are connected automatically.
General engine selection and market scope. This is the first decision layer before prompts and risk.
What the user sees and how the private workspace is named.
Choose the model, instruments and data sources before writing prompts.
GPT-5.4 miniselect
D1 currentselect
Estimate for one completed agent iteration across all selected instruments. Input tokens have two layers: fixed platform prompt/schema and variable public control + market data packet. Model preview includes 30% Art Argentum margin. Wallet ledger rounds positive usage cost up to cents; there is no fixed run floor.
Create, edit, activate and pause are free. manual iteration only queues a request; the engine bills the calculated token cost after completion.
Connected files
Every source uses one file board. Trading instruments are connected automatically; optional context files are selected directly from the same board.
Chart filesCandle and price-action files available to the strategy.5 automatic
Macro filesMacro, fundamentals and company context files.5 automatic
Insights filesNarrative, media and insight files available to the strategy.5 matched · source OFF
Source switches are binding. These lists only narrow attention inside enabled sources.
Optional short focus lists for enabled data sources. Disabled sources are saved as null and ignored by the prompt.
This focus list is active and will be included only inside the enabled source layer.
This focus list is active and will be included only inside the enabled source layer.
Disabled because the matching data source is OFF. Turn the source ON to edit this focus list. It will be saved as null while disabled.
The central instruction layer: tell the model how to analyze, decide, manage positions and reason about risk.
Separated prompt blocks are easier to scan and safer to edit than one large instruction section.
Prompt text guides the LLM. Switches and numeric controls in Force over prompt remain binding and cannot be overridden here.
How the agent should read evidence before deciding.
When the agent should open, avoid or hold a trade.
How the agent should manage an already open position.
How the agent should reason about risk inside static limits.
Hard behavior and execution controls applied after the strategy prompts.
The agent cannot enable, disable or exceed the switches, numeric limits and execution rules defined in this section.
Use simple sliders instead of long prompt edits to control frequency, fast-TP behavior and recovery risk.
Sliders are static behavior controls. They guide the model inside hard source, SL/TP, volume and scheduling limits.
Position sizing, exit permissions, mechanical SL/TP watcher, SL/TP ranges and advanced risk tools are grouped here.
All SL/TP permissions and mechanical candle-exit settings live in one risk category.
SL/TP distances are intentionally not editable here. Use Scalping aggression: LOW = tighter SL / farther TP, HIGH = wider SL / nearer TP.
Take profit firstselect
Optional tools are hidden until explicitly enabled.
Choose exactly one execution model. The LLM may decide when to use it, but runtime owns direction constraints, volume math and limits.
Increase next trade after lossselect
Choose when a new model decision is requested and how much historical context is supplied.
LLM decision timing uses compact switch controls instead of exclusive cards.
More than one trigger can be active. iteration_mode is derived only for legacy scanner compatibility; iteration_triggers keeps the full contract.
These fields control how much state the model receives and what the workspace stores.




