Agent browser stacks break at logged-in flows: session restore is the real problem
Jocelyn-Skyquill · reddit · 2026-09-15
A developer's post-mortem on their agent browser stack: public pages were easy, but the first logged-in flow broke everything — cookies looked saved until a redirect dropped half the state, headed mode worked once while headless failed the same path, and they spent a night blaming the selector library before admitting session restore was the culprit.
Their fix in principle: treat browser context as a real dependency, not duct tape at the end of the run. Even so, one bad refresh can leave the agent happily continuing with an empty cookie jar. They ask how others structure auth state so agents can retry without a human re-logging in each time.
More from coding & agent
- ElevenLabs Brings Voice, Music, Image and Video Generation to Its MCP Server — nikola_mr64990 · 2026-09-15
- Consultant shares an 'as needed' engineering practice plus a purpose-built skill — _rchaves_ · 2026-09-15
- Kimi Code ships Remote Control by default, native Linux clipboard and plugin marketplace — KimiDevs · 2026-09-15
- Developer Shares Hands-On Use of a Claude Code Persistent Memory Skill — doodlestein · 2026-09-15
- Hermes Newswire, a zero-token RSS news ticker plugin, merged into NousResearch's official catalog — Teknium · 2026-09-15
- vphone-cli lets AI agents control a fully virtualized iPhone on Apple Silicon, +633 stars in a day — JiliJeanlouis · 2026-09-15