How to use Codex to verify cash-flow plans before payday
Codex challenged Safe to Spend’s cash-flow proof and chat gates; independent checks and a failed forecast promotion gate limited claims before the release.
devpost.com
Suggested prompt
Suggested prompt written by Agents In Use, not the source author. Replace bracketed inputs and review tool permissions first.
Independently review this payday cash-flow solver. Check integer-cent arithmetic, dated action feasibility, chat gates and every optimality claim against a separate brute-force oracle. Test fallback labeling and forecast underprediction on held-out accounts; reject a complex model if it misses the predeclared gate, and never present a projection as guaranteed solvency.
Reach people exploring AI agents
See placements →What happened
The creators report a deployed cash-flow tool with independent plan checks and a rejected neural forecast; no actual savings, guaranteed balance or live banking outcome is claimed.
Reported by nrstough Stough and bussiw hrushi — DevpostHow the agent did it
- Codex independently reviewed the collaboratively built solver and found gate, lock and unsupported-proof defects.
- The team added independent plan verification and cross-language parity against a brute-force oracle.
- Human promotion criteria rejected an inadequately transferring neural forecast in favor of a simpler measured rule.
Where a person stepped in
The creators set model-promotion gates, accepted the simpler forecast and constrained financial wording; no agent moved funds or established guaranteed solvency.
The Safe to Spend creators used Codex to challenge a cash-flow planning application built alongside Claude Code. The product calculates dated spending changes intended to keep a projected balance above zero until payday; its evidence includes sandbox, CSV and demo inputs rather than connected production bank accounts.
Codex’s adversarial review found a bypassable chat gate, a conversation lock and a claim of minimality that was not actually proved. The team rewrote verification so a chosen plan was checked independently. A separate TypeScript brute-force implementation acted as an oracle for the Python CP-SAT solver and also supplied a disclosed offline fallback. Money remained integer cents.
The team also rejected its more elaborate neural forecast. A promotion gate required improvement without unacceptable underprediction; corpus gains failed to transfer to a real-account evaluation. The shipped forecast instead used a weekday-based percentile of recent spending. The source does not assign every forecasting experiment exclusively to Codex, so this case keeps its concrete attribution on independent review and implementation collaboration.
Humans set acceptance and wording boundaries. The reported result is a deployed planning tool with corrected proof claims and an acted-on negative model result, not guaranteed solvency, verified personal savings or authority to move money. Broader live account connectivity remained future work.
Prompt
Suggested prompt (written by Agents In Use, not the author's)
Source: Devpost · nrstough Stough and bussiw hrushi
Frequently asked questions
What did Codex’s review actually catch?
The source names a bypassable chat gate, a conversation lock and an unproved minimality claim.
Did the neural forecast ship?
No. The team rejected it after the promotion gate failed to transfer to a real-account evaluation.
Can its outputs guarantee the user stays solvent?
No. The source limits wording to the displayed schedule and uses sandbox, CSV or demo inputs.
More details
About this account
Codex independently reviewed the collaboratively built solver and found gate, lock and unsupported-proof defects. The team added independent plan verification and cross-language parity against a brute-force oracle.
Firsthand dated build/review account opened. Codex review and Claude Code collaboration explicit; forecasting experiments are team-reported rather than attributed solely to one agent. This is a software evaluation, not financial advice or an executed money transfer. Suggested prompt written by Agents In Use; no original task prompt was found in the verified text.
Credit: nrstough Stough and bussiw hrushi — Devpost
Source published 20 Sept 2026
Source checked 14 Oct 2026
Tools and topics
Codex · Claude Code · OR-Tools CP-SAT · TypeScript oracle · Nessie sandbox
cash-flow evaluation · independent verification · negative model result
Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.