How to use Codex to keep outfit previews out of the cart
Codex helped build ÉLANE’s separate outfit staging, private concept preview and approved cart changes; the demo stopped before checkout and made no fit promise.
devpost.com
Suggested prompt
Suggested prompt written by Agents In Use, not the source author. Replace bracketed inputs and review tool permissions first.
Build an outfit workflow with separate catalog reads, staging, render-kit retrieval and cart mutations. Keep photos in the customer’s own compatible agent, expose exact garment references and use the same visible state. Require a fresh explicit request for bag or promotion changes, and stop before checkout while labeling previews as concepts.
Reach people exploring AI agents
See placements →Evidence at a glance
Sourced account- Source author
- Karanraj Sankaranarayanan
- Original account
- Read the source ↗
- Published
- Source link checked
- Reported result
- The published demo staged and previewed an outfit, then changed the bag only after a separate request; no payment, order or exact-fit guarantee is claimed.
- Human involvement
- The human creator defined privacy and tool boundaries; the demo customer reviewed the preview and separately requested cart changes, with no payment authority granted.
A linked account supports attribution. It does not mean we independently reproduced its result.
Report an issue with this case
Open correction emailOpens your email app with the case link included. Nothing is sent automatically.
How the agent did it
- The creator set separate states for outfit staging, personal preview and shopping-bag changes.
- Codex assisted implementation and checks for shared state, exact garment references and bounded WebMCP contracts.
- The demo required a separate customer request before cart and promotion changes and stopped before checkout.
Karanraj Sankaranarayanan used Codex throughout development, debugging and testing of ÉLANE, an agent-ready fashion storefront. The central task was to keep outfit exploration, a personal image preview and changes to the shopping bag as separate actions.
In the published demo, an external shopping agent staged four garments for a CAD 1,500 brief. The staged look cost CAD 1,100, but the bag stayed empty. A read-only render-kit tool supplied exact garment images, selected sizes and layers, allowing a compatible image-generating agent to combine them with a photo already in its conversation. The boutique never received that photo.
Only after reviewing the concept did the customer separately request bag additions and a promotion. The demonstrated bag total became CAD 935. The demo stopped before checkout: no payment or order occurred.
Codex helped implement shared React state, closed tool schemas, bounded outputs and verification checks. The human creator set privacy and approval boundaries. The runtime agent’s exact identity is not named, so this case attributes Codex to the build rather than assigning it the shopping actions. The generated image was explicitly a visual concept, with no guarantee of fit, material behavior or final appearance. Its useful result is a tested separation between preview and consequential cart changes.
Prompt
Suggested prompt (written by Agents In Use, not the author's)
Source: Devpost · Karanraj Sankaranarayanan
Frequently asked questions
Did the website receive the customer photo?
The source says it remained in the external agent conversation, while the site supplied garment references.
Did staging the outfit add it to the bag?
No. A separate explicit customer request was required.
Is the generated image a fit guarantee?
No. It is a visual concept and does not establish sizing, drape or final appearance.
More details
About this account
The creator set separate states for outfit staging, personal preview and shopping-bag changes. Codex assisted implementation and checks for shared state, exact garment references and bounded WebMCP contracts.
Firsthand dated build and demo opened. Codex’s development role is explicit; the demo’s external shopping agent is unnamed, so runtime actions are not attributed to Codex. Demonstrated prices are scenario values, not current recommendations. Suggested prompt written by Agents In Use; no original task prompt was found in the verified text.
Credit: Karanraj Sankaranarayanan — Devpost
Source published
Added to Agents In Use
Source checked
Tools and topics
Codex · WebMCP · React · TypeScript · Style Studio
outfit preview · separate cart approval · photo privacy
Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.