> ## Documentation Index
> Fetch the complete documentation index at: https://docs.stratalerts.com/llms.txt
> Use this file to discover all available pages before exploring further.
# AI Search Queries
> AI Search lets you type plain English Strat queries directly into StratAlerts, which translates them into structured filters instantly.
AI Search is the natural language query engine built into the StratAlerts setups table. Instead of manually configuring column filters, you type what you're looking for in plain English — using the same Strat terminology you already think in — and the system translates it into structured filters that update the table immediately. It's designed to let you move fast: a two-second query replaces several clicks of filter configuration.
## Accessing AI Search
You can open AI Search from multiple places:
* **Wand button** — click the wand icon (✦) next to the gear menu in the Setups Table toolbar. This is the fastest mouse-driven way to open AI Search while you're already working with the table.
* **Keyboard shortcut** — press **Q** from anywhere in the app to open the search input immediately.
* **Mission Control** — use the AI Search bar on the main overview page.
Type your query and press **Enter** — the table filters update in real time.
AI Search is part of the StratAlerts app and does not require a separate AI Tools subscription. It runs inside the app and works against the live setups table.
## How it works
When you submit a query, StratAlerts parses your natural language input and maps it to structured filter conditions on the setups table. The mapping preserves Strat-specific terminology, so you don't need to translate it yourself.
Use Strat terminology naturally — candle types, timeframe names, setup conditions. The parser understands both shorthand (`2U`, `2D`) and expanded forms (`two up`, `inside day`, `in force`).
Your query is converted to specific filter conditions: candle type (CC, C1, C2), timeframe, TFC state, in-force status, and similar fields. The translation is shown so you can verify what was applied.
The table refreshes to show only the symbols that match your query. From there, you can sort, click into individual symbols, or add additional manual filters.
## Example queries
These examples show the query you type and the filter conditions it maps to:
**Query:** `all inside days`
**Translates to:** CC = `1` on the daily timeframe
Returns every symbol currently forming an inside day — a candle contained entirely within the prior candle's range. Useful for identifying coiled setups before a potential directional break.
**Query:** `2U weeks in force`
**Translates to:** CC = `2U` on Weekly timeframe, In-Force = `true`
Returns all symbols where the weekly candle is a 2U that has gone in-force — meaning price has broken above the prior weekly high.
**Query:** `1-2U setups on the daily`
**Translates to:** C2 = `1`, C1 = `2U` on Daily timeframe
Returns symbols showing the classic 1-2U setup pattern: an inside day followed by an up-candle, with the current candle potentially resolving the setup.
**Query:** `green C1 on the month`
**Translates to:** C1 Color = `green` on Monthly timeframe
Returns symbols where the trigger candle closed green. You can also target the target candle with `red C2` or use natural phrases like `green trigger candle` and `red target candle`. When you add a color to a two-part setup sequence like `1-2d green`, the color defaults to C1 unless you explicitly say `C2` or `target candle`.
**Query:** `day and week are 2U`
**Translates to:** Daily CC = `2U` AND Weekly step CC = `2U`
Returns symbols aligned as 2U on both the daily and weekly timeframe — a stronger continuation signal than a single-timeframe 2U. AI Search preserves both timeframe-state filters, so queries like `week and month that are 2u` keep the weekly base filter and the monthly step instead of collapsing to a single timeframe.
**Query:** `day in force and week in force`
**Translates to:** Daily In-Force = `true` AND Weekly step In-Force = `true`
Returns symbols that are in force on both the daily and weekly timeframes simultaneously. AI Search preserves the `in_force` flag inside each multi-timeframe step, so both conditions carry through to the table filters.
## Strat terminology the parser understands
AI Search recognizes the core vocabulary of The Strat methodology. You can use these terms directly in your queries:
| Term | Meaning |
| ------------------------------- | --------------------------------------------------------------- |
| `inside`, `inside day`, `1` | Candle 1 — inside candle contained within prior range |
| `2U`, `two up`, `up candle` | Candle 2U — up-candle, high above prior high |
| `2D`, `two down`, `down candle` | Candle 2D — down-candle, low below prior low |
| `outside`, `3`, `broadening` | Candle 3 — outside candle, both high and low exceed prior range |
| `failed 2U` | 2U candle that reversed below its own open |
| `failed 2D` | 2D candle that reversed above its own open |
The parser accepts full names and shorthand:
| Accepted terms | Timeframe |
| ------------------------------- | --------- |
| `15m`, `15 minute`, `15-minute` | 15-minute |
| `30m`, `30 minute` | 30-minute |
| `60m`, `60 minute`, `hourly` | 60-minute |
| `4H`, `4 hour` | 4-hour |
| `daily`, `day`, `D` | Daily |
| `weekly`, `week`, `W` | Weekly |
| `monthly`, `month`, `M` | Monthly |
| `quarterly`, `quarter`, `Q` | Quarterly |
| `yearly`, `year`, `annual`, `Y` | Yearly |
AI Search understands two-part and three-part Strat setup sequences using the standard C2-C1 or C2-C1-CC notation:
| Term | Filter applied |
| ----------------------------- | ----------------------------------------------------------- |
| `1-2U`, `1-2d` | C2 = `1`, C1 = `2U` or `2D` |
| `3-2U`, `2D-3` | Directional two-part sequences |
| `1-2-2`, `1-2U-2D` | Three-part sequences mapped to C2-C1-CC |
| `all 1-2 setups on the month` | Expanded to C2 = `1`, C1 = `2` (both directions) on Monthly |
Bare `2` in a sequence is automatically expanded to cover both `2U` and `2D`. Explicit directional sequences like `1-2d` are mapped correctly as setup-sequence filters, not misread as current-candle state.
| Term | Filter applied |
| ---------------------------------- | -------------------------------------------- |
| `green C1`, `green trigger candle` | C1 Color = `green` |
| `red C2`, `red target candle` | C2 Color = `red` |
| `1-2d green` | Setup = `1-2D`, C1 Color = `green` (default) |
| `green C2 on the week` | C2 Color = `green` on Weekly |
When a color is attached to a setup sequence without specifying which candle, it defaults to C1. To target C2 instead, explicitly name it.
| Term | Condition |
| ----------------------------------- | --------------------------------------------- |
| `in force`, `in-force`, `triggered` | InForce = true |
| `continuation` | Continuation = true |
| `P3`, `potential 3` | P3 flag = true |
| `PMG`, `potential major gap` | PMG flag = true |
| `green TFC`, `bullish TFC` | TFC state = green for the specified timeframe |
| `red TFC`, `bearish TFC` | TFC state = red for the specified timeframe |
## Tips for effective queries
Be specific about the timeframe. "2U setups" is valid, but "2U setups on the daily" returns a more focused result. If you omit the timeframe, AI Search defaults to the timeframe currently selected in the table.
Combine conditions naturally. Phrases like "2U daily with green weekly TFC" or "inside days on the 60 that are in force" work as you'd expect — the parser handles compound conditions.
AI Search is designed for standard Strat terminology. Very custom or proprietary terms outside the standard Strat vocabulary may not translate correctly. If a query produces unexpected results, check the filter summary shown below the search bar to see exactly what was applied.
## Related
Feed live Strat bundles into GPT, Claude, Gemini, and other LLMs for deeper AI-powered analysis.
Detailed field reference for the NDJSON bundle format used with external LLMs.