frame devs: what do you prefer about the frames.js frame debugger over the warpcast debugger?

Building @warpcast and @farcaster / dad / like to read, cook, ski, code

warpcast debugger:
- is wonky
- loses all my input on reload (unlike Warpcast mobile)
- it doesn't debug anything, just launches a frame
- throws errors on SDK interactions (add frame) instead of helping me debug them (success/failure)
- it's necessary evil since it's the only way to simulate FC connection

what I'd like as a developer:
- support debugging SDK interactions
- save my input to local storage, so I don't have to re-type it each time
- output extra Warpcast-specific stuff to console: auth, connection, interactions, etc
- output some basic stats (time to auth, etc)

oh, and above all: fix timeout when trying to fetch frame embedding

✳︎ design engineer → @ponder 
✳︎ explorer of humanism • petrolhead/gearhead
✳︎ React/SwiftUI
✳︎ bento.me/matthew

even better, allow SDK to simulate connection in dev for a given FID and we can do away with this whole tunneling thing altogether, as it's a big obstacle