Authentic execution demo

Coupang browser execution

WinClaw ingredient reorder demo

When the owner says an ingredient is running out, the WinClaw local daemon opens an existing browser window, searches for the product, compares candidates, stops at the point right before ordering, and leaves a procedure + screenshots behind.

We're out of tofu. Find something that can arrive by tomorrow morning and prepare it up to the point right before ordering.

This use case does not confirm a real purchase. Login, CAPTCHA, and OTP are handled by the owner. WinClaw never clicks the final pay or order-confirm button.

Coupang browser execution
https://www.coupang.com/search?q=업소용+두부
Recommended Jjigae-grade tofu (bulk)

Arrives tomorrow morning; cart is prepared

human approval required

Halted at the order-review screen. Never clicks the final pay or order-confirm button.

Procedure recorder

From shortage to stop-before-order

  1. 01Understand the shortage

    WinClaw extracts the ingredient, the desired delivery window, and the stop-before-order condition from the owner's request.

  2. 02Open the browser

    The local daemon opens an existing PC browser and verifies the Coupang login state.

  3. 03Delegate login barriers

    Login, CAPTCHA, and OTP are handled by the owner. WinClaw does not bypass them.

  4. 04Product search

    Searches Coupang for restaurant-grade tofu, jjigae-grade tofu, and tomorrow-morning delivery.

  5. 05Compare candidates

    Compares price, quantity, delivery ETA, and review credibility; organizes the candidates.

  6. 06Stop before order

    Goes only as far as cart / order-sheet prep and halts at the human-approval point.

  7. 07Record evidence

    Saves procedure.md, evidence.json, screenshots, and a replayable reorder-tofu.play draft.

Candidate comparison

Candidates WinClaw compared

Recommended

Jjigae-grade tofu (bulk)

Arrives tomorrow morning, stable unit price, sufficient stock

Alternate

Pan-fry / jjigae tofu

Smaller quantity but immediate delivery available

On hold

Restaurant-grade pan tofu

Lower unit price but slower delivery

Recorded artifacts

Procedure + screenshots stay behind

When execution finishes, WinClaw leaves a procedure record, screenshots, evidence.json, and a replay draft for the owner and partners to review.

screenshots/

  • 01-login-handoff.png
  • 02-search-results.png
  • 03-product-detail.png
  • 04-cart-before-payment.png
  • 05-approval-stop.png

report files

  • procedure.md - records clicks, inputs, waits, and approval points in order
  • evidence.json - timestamp, action, target, result, screenshot_path, redaction_applied
  • reorder-tofu.play - a ScreenPlay draft to replay the same task
  • Address, phone number, and payment method are masked before storage

Real processing attempt

Real attempt result

We tried the real login URL from .env.coupang, but Coupang returned 403 Access Denied before the login form. COUPANG_ID and COUPANG_PW were not entered. The outcome demonstrates WinClaw's safe behavior — recording the site-protection barrier rather than bypassing it.

  • procedure.md - record of stopping at the 403 barrier
  • evidence.json - blocked_before_login_form, http_status_observed: 403
  • screenshots/01-login-page-access-denied.png
Real attempt screenshot showing 403 Access Denied on the Coupang login page
Site-protection barrier recorded during the real browser attempt

What a successful run looks like

Real evidence preview (2026-05-24 headed success)

Below are the six screenshots from a run with a demo-only Coupang account. The same flow produces a new evidence folder every time "Run real WinClaw API demo" is pressed (result.kind = safe_stop, label = payment_confirm). On click, an approval request (✅/❌) is sent to an admin Telegram at the wait_for_user point; on non-approval / timeout, the run finishes safely with a safe_stop manifest. If WINCLAW_TELEGRAM_TOKEN / WINCLAW_TELEGRAM_CHAT_ID are unset on the server, the endpoint refuses with 503.

  1. login attempt01 login-attempt
  2. post submit barrier02 post-submit-barrier
  3. post login03 post-login (coupang home)
  4. compare04 compare (찌개용 두부 검색)
  5. cart skipped05 cart-skipped (graceful recover)
  6. stop before payment confirm06 stop-before-payment_confirm

Real API execution · Telegram 승인 게이트

이 버튼이 실제 WinClaw demo API를 호출합니다

Ingredient reorder handoff run Ready · POST /api/demo/ingredient-reorder/runs
  1. 01AuthBarrier detected

    403/site protection barrier를 기록합니다.

  2. 02ManualHandoff

    사용자가 사용자 소유 브라우저에서 로그인/CAPTCHA/OTP를 완료합니다.

  3. 03Resume same session

    WinClaw가 같은 세션에서 쿠팡 검색 흐름을 재개합니다.

  4. 04Compare candidates

    찌개용 두부 대용량, 대체 후보, 보류 후보를 비교합니다.

  5. 05ApprovalStop

    payment_confirm 전 정지하고 사장님 승인을 기다립니다.

  6. 06Evidence recorded

    procedure.md, screenshots, evidence.json을 생성합니다.

Safety boundary

Purchase is prepared but never confirmed

The point of this demo is to show WinClaw's local browser execution and evidence recording. Actual purchase confirmation only happens after owner approval.

  1. Drives the existing browser window — no API
  2. Login, CAPTCHA, and OTP are handled by the owner
  3. Never clicks the final pay or order-confirm button
  4. Does not complete external purchases without human approval
  5. Address, phone number, and payment method are masked