Daily loss limit doesn't persist across a restart

Agreed on severity — a limit that resets is worse than no limit because you believe you're protected. The daily total needs to persist against the trading day rather than the process lifetime. Treating this as a priority fix.

I would absolutely have been caught by this and never known why.

Update: fixed, going out in the next build. The daily total is now read back from your saved trade history when auto-trading starts, so a mid-session restart carries the loss you have already taken instead of handing you a fresh allowance. If that read fails for any reason the app says so on screen rather than silently starting from zero — a limit that quietly resets is worse than no limit, which was your original point.

Good catch, and two follow-ups on the fix: 1. Which clock defines "daily"? If it's local machine time and I'm travelling, the boundary moves with me and the read-back could pull in trades from what my broker calls the previous session. 2. Does the history read count realised P/L only, or open positions marked to market? Those give very different numbers on a day where I'm still holding. 3. Your last sentence got cut off, "if that read fails for any reason the ap..." — what does it do? I'd rather it refuse to arm than arm with a zero total.

On the clock: Eastern, not the machine's. A fixed ET calendar day, so travelling does not move the boundary and a 24-hour crypto session does not turn "daily" into "since start". On what counts: realised P/L for that ET day plus unrealised on open positions, against your equity base. Open positions are in there deliberately. The position you have not closed is the one the limit is for.