Code gets caught inside the reasoning stream: a security rule fires, the model rewrites in place, and secure-and-working runs rise from under 15% to 72.8%–98.1%
Reasoning models draft code early inside their chain of thought, and SecReason scans the streaming tokens before delivery and inserts a warning so the model repairs the draft within the same reasoning trace, raising the share of runs that are both secure and functionally correct from below 15% to 72.8%–98.1%.