Saved scripts
Everything the copilot builds with you is kept: the script, every version of it, and the conversation that produced it. Your scripts are also the point at which the rest of the platform stops being ours and starts being yours — they run as engines on the Screener and the Live Tape.
Versions
A script is not one file, it is a stack of versions, each with a note saying what changed. Accepting a copilot edit files a new version rather than overwriting the last one, so a change that made things worse is one click from being undone. The version pills in the workbench switch what the chart and the code are showing, and the Backtest records which version produced a result.
A script remembers the chat that built it, so a fix you want can be sent back to the conversation that has the context, rather than explained again from scratch.
Across your devices
Scripts belong to your account, not to a browser. Sign in on a phone and what you built at your desk is there. If the network is down or you are signed out, the local copy stays in charge and nothing is lost — the two reconcile by version when you are back.
Scripts as engines
A saved script is selectable as an engine on the Screener and as a source on the Live Tape. The script runs across the scan universe in your own browser and keeps the names it is signalling on now — a strategy counts while it holds a position, an indicator counts if it fired within the last few bars.