debug-store

Debug Store Infrastructure (developer-only)

This is the inside-out view of vibe-seller stores: how to inspect and drive the runtime — the database, the browser-use wrapper, the CDP proxy, the per-store Ziniao session — without going through the task system, the web UI, or the JWT-cookie auth wall.

This is for the platform builder, not for end-user agents running tasks. For end-user/agent flows (running campaigns, etc.), see amazon-ads and new-product-launch.

What you can do without a task

The vibe-seller per-store wrapper is just a shell script that talks to a long-running CDP-mux proxy. The wrapper auto-starts the proxy and the browser via an internal API call (with a baked-in ai_bot JWT, so you don't need user creds). All you need is:

1. A fresh VIBE_TASK_ID env var (lowercase UUID; first 8 chars must be hex).
2. The store slug (look it up in ~/.vibe-seller/data/vibe_seller.db — stores.name, then slugify; or just list ~/.vibe-seller/bin/ for the directories that actually exist).

Then ~/.vibe-seller/bin/<slug>/browser-use open <url> works.

DB cheatsheet

DB=~/.vibe-seller/data/vibe_seller.db
sqlite3 "$DB" .tables
sqlite3 "$DB" "SELECT id, name, browser_backend, platforms, countries FROM stores;"
sqlite3 "$DB" ".schema stores"
sqlite3 "$DB" "SELECT id, username, email, role FROM users;"
sqlite3 "$DB" "SELECT store_id, status, current_platform, current_country,
                      active_tab_count, cdp_port, chrome_pid
               FROM browser_sessions;"
sqlite3 "$DB" "SELECT id, status, substr(result,1,120), substr(error,1,120)
               FROM tasks WHERE created_at > datetime('now','-1 hour')
               ORDER BY created_at DESC LIMIT 10;"

The stores table has no slug column — the wrapper directory (~/.vibe-seller/bin/<slug>/) is where the actual usable name lives. name in DB is the user-facing label and may differ from the slug when names contain spaces / non-ascii. Match by ID when scripting.