7 sessions on websocket with a coding agent: the agent failed at least once in 3, and 4 finished without a human stepping in.
Takeaway: Next time I'd ask for the migration to be done component-by-component with a build check after each one, instead of generating the whole 25-component app in one shot and debugging the pile of runtime errors afterward.
Takeaway: Next time I'd start by asking directly for the two known root causes at once: the frontend title priority order and the 64KB session-summary read truncation on large image messages, since both turned out to matter.
Takeaway: I'd start by pointing the agent straight at useBridgeClient.ts and ws-rpc-adapter.ts instead of letting it discover the RPC layer through several rounds of grepping from the Vue component outward.
Takeaway: Next time I'd start by asking directly for a headless mode in /web instead of first exploring RPC/SDK paths that turned out to be dead ends — that exploration cost a lot of turns before we landed on the right approach.
Takeaway: I'd start by just asking for a one-line summary plus the key entry points instead of letting the agent read every single file, since most of the answer came from README.md and a handful of core files.
Takeaway: I'd start by naming the exact env vars and lifecycle hook I suspect (session_start firing per-subagent) so the agent goes straight to gateway/update/self-update extensions instead of spending a dozen turns on lsof and pstree.