Key takeaways · 6
- Appending
| save $nameto any query stores the rule itself, not a frozen list of tickers:screen rs>90 float<40m | save $lowfloatfiles that exact filter under the handle$lowfloat, which then shows up as a chip in the terminal's SAVED row. - Recall is one word. Type
$lowfloatalone on a later night and the terminal treats the handle as shorthand for the stored query, re-runningscreen rs>90 float<40magainst that night's close instead of returning whatever it found the day you saved it. - Because the rule re-runs instead of the membership freezing, a saved screen is survivorship-free: names that lose relative strength or grow past the float ceiling drop out on their own, and new qualifiers appear, with nobody pruning the list by hand.
- The payoff compounds with repetition. Build the filter once and the nightly habit shrinks to typing one saved handle instead of retyping
rs>90 float<40mfrom memory every session, the kind of friction that decides whether a screen turns into a routine or gets forgotten by Thursday. - A saved screen is not the same tool as a pinned watchlist.
$lowfloatis a rule that recomputes every close; the terminal'swatchcommand holds a roster of specific tickers you add by hand withwatch add. Keep them for different jobs. - Every run is stamped to the close it came from and reports who currently qualifies, not what to do about it.
$lowfloattonight is a fact about tonight's tape; the trade is yours.
The two-second tax of retyping a filter
Every screen you run twice starts the same way: you sit down after the close, open the terminal, and type the same handful of predicates you typed the night before. rs>90 float<40m takes seconds to type on its own, but stack it across a hundred trading nights and it becomes the kind of small friction that decides whether a filter turns into a habit or quietly stops getting run. A screen you have to reconstruct from memory every evening is a screen you will eventually skip on a busy night, and a busy night is exactly when you can least afford to miss it.
The fix is one clause on the end of the same command. Type screen rs>90 float<40m | save $lowfloat and the terminal does two things instead of one: it runs the screen, relative strength above 90 and float under 40 million shares, against tonight's close, and the | save $lowfloat clause files that exact query away under the handle $lowfloat, which appears as a new chip in the terminal's SAVED row. The screen you just ran is now a rule you own.
Typed live: the command decoded clause by clause. | save $lowfloat stores the rule; typing $lowfloat any later night re-runs it against that close.
What actually gets stored
Here is the part people get wrong: | save does not freeze tonight's names into a list. What it writes down is the rule itself, the literal predicates rs>90 float<40m, attached to the handle $lowfloat. Nothing about tonight's actual members, not whichever tickers happen to clear the bar on this close, gets written anywhere. The terminal keeps the question, not tonight's answer to it.
That distinction is what makes a saved screen self-updating rather than stale. A frozen list of tickers is a photograph: accurate the moment you take it, wrong a little more every day after, as some names run past your filter's boundary and others slide into it. A saved rule has no such decay, because it is never evaluated until you call it, and every time you call it, it reads the current close instead of the one you saved it on.
Calling `$lowfloat` back
Any evening after you save it, typing $lowfloat on its own is the entire recall. The terminal reads the handle, substitutes the stored query, and re-runs screen rs>90 float<40m against that session's close, no retyping the filter, no digging through history for what you ran last Tuesday. You get whichever names currently clear relative strength 90 with a float under 40 million shares, as of the close you just called it against.
Call $lowfloat back on three different nights and the rule box stays identical while the membership underneath rotates: a name that ran hot and pushed RS past 90 joins, a name whose float crept over 40 million through a secondary offering drops out, a name that cooled off the leaderboard disappears without you touching anything. The saved query is tracking a definition, not a roster, so it follows wherever the definition currently points.
The saved rule, rs>90 float<40m, never changes. The membership underneath it recomputes against every close, so $lowfloat rolls forward on its own without you touching a single predicate.
One word, every morning
This is where reading about a screen turns into actually using one. A saved query saves more than keystrokes, it removes your excuse for skipping a night. Before the open, or right after the close updates, the whole routine is typing one handle and reading what comes back. $lowfloat this morning, $lowfloat tomorrow morning, the same handle carrying the entire filter with it every time.
Save more than one and the SAVED row turns into a short menu of the questions you actually ask on repeat, $lowfloat next to whatever else you have filed away, so opening the terminal feels less like starting from a blank prompt and more like checking a handful of gauges you built yourself. That is the daily use the tickerstance terminal is built for: a small set of saved rules you check every close, because checking one costs a single word instead of a full line of syntax.
What `$lowfloat` does not tell you
A saved screen is still end-of-day. $lowfloat re-runs against the most recently completed session, not the live tape, so calling it back before the open gives you last night's close, a description of the day that already happened, not a forecast of the one about to start.
It is also still just a rule, and a rule this simple does not sort quality from noise on its own. rs>90 float<40m alone does not tell you whether the dollar volume behind a name is real or thin, or whether the move is fresh or stale. Those live in separate filters, on separate screens, elsewhere in the same terminal. Saving a query files away the rule you wrote; it does not upgrade the rule for you.
And it is not a substitute for the terminal's watch list, which holds a handful of tickers you add by hand rather than a rule that recomputes them. Both ideas sit inside the same float-and-supply toolkit, thin share count and high relative strength amplifying a move, but a saved screen is the wide, self-refreshing funnel, and a watchlist is the short list you kept after looking through it. Neither tells you what to do with a name; both just tell you, honestly, which ones currently qualify.
Frequently asked questions
How do I save a screen in the tickerstance terminal?
Append | save $name to the end of any query, with your own handle after the $. screen rs>90 float<40m | save $lowfloat runs the screen against tonight's close and files the exact filter under the handle $lowfloat, which then appears as a chip in the SAVED row at the top of the terminal.
What does `| save` actually store, the query or the results?
The query. | save $lowfloat writes down the rule, rs>90 float<40m, not the specific names that cleared it the night you saved it. Every time you recall the handle, the terminal re-evaluates that rule against the current close, so the answer changes as the market does, even though the handle and the rule behind it stay fixed.
How do I recall a saved screen later?
Type the handle on its own. On any later night, typing $lowfloat by itself tells the terminal to substitute the stored query and re-run screen rs>90 float<40m against that session's close. The same recall works for any handle you have saved, not just this one.
Does a saved screen update automatically, or do I have to re-save it?
It updates automatically every time you call it. You never re-save $lowfloat unless you want to change the underlying filter itself; the query re-runs fresh against whatever closed most recently, so membership rotates on its own as names clear the RS-90, float-under-40-million bar or fall out of it.
What is the difference between a saved screen and the terminal's `watch` list?
A saved screen like $lowfloat is a rule with no fixed members, it recomputes the whole answer every close. The watch command is the opposite: a roster of specific tickers you added by hand with watch add, that stays exactly as you left it until you change it yourself. One tracks a definition; the other tracks names you already picked.
Can I use any name after the `$`, or does it have to be `$lowfloat`?
Any handle you choose. $lowfloat is just a label; the $ prefix is the saved-query namespace, and the word after it is whatever you pick when you save. Save a different float screen under $coil or $rotation and it recalls the same way, type the handle, get that query's current answer.