Conway Cloud: Sandbox disappears after creation + wallet connector broken

[nikoamoretti]

Environment

• Automaton v0.2.1
• macOS (local mode, sandboxId: "")
• MetaMask wallet
• Browser: Chrome

Issues

1. Sandbox disappears after creation

Created a new sandbox via the Conway Cloud dashboard (app.conway.tech → + New Sandbox). The sandbox appeared briefly, then disappeared from the dashboard on refresh. The Sandboxes section shows "No sandboxes yet" / "0 total".

2. Wallet connector broken — getChainId error

When attempting to buy credits via the dashboard Buy Credits buttons, MetaMask prompts never appear. Instead, the following error is returned:

Payment failed: r.connector.getChainId is not a function

This happens on every credit purchase attempt. The workaround was to send USDC directly from Coinbase to the wallet address on Base, which worked — the Wallet USDC balance updated correctly. But converting USDC → Conway credits via the dashboard UI fails every time.

3. Minor: No network guidance during setup

The setup wizard asks for funding but doesn't emphasize that USDC must be sent on Base network specifically. Easy to accidentally send on Ethereum mainnet (which I did — $20 stuck on wrong chain). A note in the funding step would save new users money.

Workaround

• Funded by sending USDC on Base directly from Coinbase to the Conway wallet address
• Transferred credits to automaton via the Transfer Credits section (this worked)
• Running in local mode since sandbox creation fails

Expected

• Sandboxes should persist after creation
• Buy Credits buttons should trigger MetaMask transaction signing
• Setup wizard should warn about Base network requirement

[nikoamoretti]

Update: Charged for sandbox, sandbox vanished — same as #97, #162, #231

What happened

1. Topped up $5 on Conway dashboard
2. Created a Small sandbox via dashboard UI
3. Sandbox appeared briefly, then disappeared on page refresh
4. Transaction history shows the $5 charge went through

API evidence

GET /v1/sandboxes
→ {"sandboxes":[],"count":0,"source":"workers_fallback_blocked"}

POST /v1/sandboxes (attempt to create new)
→ {"error":"Insufficient credits","current_balance_cents":433}

The workers_fallback_blocked source confirms the worker backend can't reach/list sandboxes — same root cause as #162 where "source": "supabase" showed the row was deleted.

Credits were deducted ($5) but the sandbox no longer exists. Current balance is $4.33, meaning the charge went through but the sandbox was never properly persisted.

Impact

• Automaton (Nicodus) is running locally, has built services, but cannot serve x402 traffic without a sandbox
• Blocked from revenue generation entirely
• $5 lost to a phantom sandbox

Request

1. Credit adjustment for the lost sandbox ($5)
2. Any ETA on sandbox stability? This is the same pattern reported in CRITICAL BUG: Charged for VM creation, but sandbox is missing/inaccessible (refund or restore requested) #97, Sandbox cannot be found - I’ve had this sandbox for a week and it is now missing. #162, Charged for Small VM but no sandbox provisioned (credits deducted) #231 — sandboxes created and charged but lost from the control plane DB.

Automaton wallet: 0x91827356dE28A3bb8f22E58dA5426977062bFfeE

[nikoamoretti]

Additional: Dashboard balance doesn't match MetaMask wallet balance

The Conway dashboard shows a different balance than what MetaMask shows for the same wallet address (0xe8096b6be430e7f9bdaf79020423615ea752ac1e).

This compounds the wallet connector issue already reported (r.connector.getChainId is not a function) — even when the dashboard does load, the balance displayed is wrong/out of sync.

Between the broken wallet connector, phantom sandbox charges, and mismatched balances, the entire billing flow is unreliable right now.