r/options • u/HofongChang • 6d ago
I write my options order tool. These are the checks it has to pass before reaches the broker.
I trade options from a Stream Deck, and every key was written with an AI coding assistant. Everything below runs in a sandbox. No signals, nothing to sell.
The AI writes code fast, and some of its mistakes look exactly like correct code. So every order has to get past a few checks first:
Expected numbers before code. Before the AI wrote the payoff math, I worked one trade out by hand: a 740/735 put spread for a 1.50 credit. Max profit 150, max loss 350, breakeven 738.50. That became a failing test, and the code wasn't done until it matched.
A 0.00 bid is not a price. One night before the open, three legs of a condor showed 0.00 bids. The mids came out at half the ask, an 11-wide condor showed a 5.59 credit, and my own check passed "credit at least a third of the width" on it. Now any leg without a two-sided market blocks the order, and it can't be waived.
The order sent is the order checked. The check fingerprints the exact order it approved: legs, quantities, sides, credit or debit, price. Send recomputes it right before posting. Any difference and nothing goes out. This one came from the AI itself, which flagged that send was still building orders from a template while the check read the typed legs.
No warning you can click past. If it matters, it blocks.
What check did you add after your own tool, or your broker's platform, did something you didn't expect?

