deepseek

Re-logging into DeepSeek via VNC every week got old. I transferred the whole session into Camofox instead: cookies, token, keepalive.

TL;DR: DeepSeek sessions in Camofox died because logging in means two layers: HttpOnly cookies and a localStorage userToken for Bearer API calls. Importing cookies alone patched half the state, so the login page persisted. Three scripts merge cookies into Playwright's storage-state.json, inject the wrapped token, and poll every five minutes to confirm the session.

The text visibly entered the textarea, yet React never saw a change. Why plain assignment fails on controlled components and how the native prototype setter fixes it.

TL;DR: Automating React apps like DeepSeek fails when you set textarea.value directly, because React replaces the setter on each element instance and swallows non-user input events. The fix: grab the native setter from HTMLTextAreaElement.prototype, call it with your text, then dispatch a bubbling input event. Since the icon-only send button has no label, press Enter instead.

OpenCode's usage board is led by cheap open models, not benchmark kings. How I read usage, retention, and price before switching models.

TL;DR: Benchmark leaders like GPT-5.6 top SWE-Bench, yet deepseek-v4-flash leads OpenCode's real-world usage, suggesting cost, speed, and context length matter more than peak scores. The author recommends checking usage volume, momentum, and weekly retention as satisfaction signals. Treat official model lists as a starting point, then validate against usage data and a small trial in your own repo before committing.